SupportS3 Backup 1.0.3 — Unattended backups and other updates
We’ve just released S3 Backup 1.0.3. The autoretry logic and the configuration system were improved in this version.
The most noticeable change is that the application password now does not prevent the unattended backups. If you have checked the “protect application” checkbox in the settings, when you start the application manually, you are asked for the password, but when the app runs on schedule it does that without requiring any interaction.
Previously, setting the password encrypted the entire configuration file with it, so without the password the application just could not get to the S3 credentials and other settings. This release changes this and while the sensitive parts of the configuration are still encrypted, it is done in such a way that the app can run unattended. As part of this update the configuration file format changed from XML to JSON.
Another part of the app that was updated is the autoretry logic. S3 Backup is very resilient in the face of various errors that could happen, such as network problems, transient S3 errors and other conditions. When any of those happen, the event is logged, but the job continues to run, retrying the operation until it succeeds. We had this system in place for a very long time, but for this release we’ve updated it in various ways to make sure it can wait out even the more prolonged network outages and is more clear about what eventually causes it to give up.
We’ve also added support for automatically retrying interrupted downloads.
Bugfixes
- For users who were using Blowfish encryption in pre-1.0.2 releases and had a very long encryption password, the last release broke the downloading of those older files. This is now fixed.
- When a network error is reported, a message from the operating system is logged. This is done for information purposes only and does not prevent the app from trying that operation again. However, if the system locale causes the errors to be reported in non-ASCII encoding, this logging operation failed and caused a more severe error that stopped the entire operation. This is now fixed and those error messages are converted to Unicode using the system-specified encoding.
Other updates
- wxPython toolkit was upgraded to the 2.9 branch