39 weeks agoS3 Backup beta 15 rev.1255

S3 Backup beta 15 rev.1255

Sorry for taking a bit longer with this release. The reason for that was that I spent some time working on new code. The process of building an executable was completely overhauled and while it brings no immediately obvious changes for the user it’s an important step for some of the things we have planned and to be announced at their own time.

(Also, another beta extension for S3 Webmaster was issued. I expect that it will get some care rather soon and get an actually updated release at last.)

  • Almost immediately after rev.1221 a rev.1224 was issued with a fix to Reaction bug in lock management. I apologize for having that one in the first place, but I also have to note that the bug was of a kind that would go unnoticed if Reaction wasn’t written with thought given to such things — it did a very good job detecting that something was wrong.
  • The issue with Windows 7 scheduling that appeared in the last revision was resolved. We always try to test the app in a couple of different environments before releasing a new version, but as far as permissions on task scheduling operations go, systems seem to vary wildly. So if you have any messages pop up when configuring the scheduling of the backup job, let us know so we could look into it. Note however that this does not apply to the running on schedule part — that functionality is solid. It’s the configuration part that proved to be quirky.
  • When the client computer time is skewed, Amazon denies access for security reasons (to fight against so called “replay attacks”). This condition was not properly reported in a few recent revisions, but this is fixed now. If your computer clock or timezone settings are way off you will get a message telling you what time Amazon expects the client machine to have.
  • The app is linked against newest Microsoft CRT libraries now.
  • I will not detail the multiple changes to the application building process and internal changes, as this time that is something that is quite hard to explain without getting into details on internal architecture. So I’ll just mention that there were quite a few more.

Now we are back to migrating the codebase and releasing new revisions every couple of days. We were made aware of a couple temporary issues caused by mismatch in some parts of the app between the old and the new codebase, but those will be resolved shortly.

Still, please do report whenever you see any odd behavior.

Also, let me mention again that while S3 Backup is in beta you can order a license at discount.