Page History

...

Beginning with SQLsafe 6.5, %timestamp% expands to the local time of the backup. As a result, SQLsafe may write new backups to files already created by an earlier version of SQLsafe immediately after upgrading. By default, SQLsafe appends to backup files and this issue does not occur as the new backup appends to the existing file. This situation resolves itself after the time difference between UTC and local time passes. For example, this issue is resolved after five hours in the Central Standard Time zone (US).

Note that if you specify to overwrite, SQLsafe overwrites the existing files instead of appending the new information. If you upgrade from a release earlier than SQLsafe 6.4, appends fail and display an error message.

Setup program removes previous version when upgrade fails

If the upgrade fails while you are upgrading from a previous version of SQLsafe, the setup program removes the previous version from the SQL Server computer on which you attempted the upgrade.

XSP installation fails on clustered SQL Server instances

When you use the Agent Only install to manually deploy the SQLsafe Backup Agent to a clustered SQL Server instance, the corresponding SQLsafe XSP installation will fail. After the Backup Agent install completes, you can manually install the SQLsafe XSP.

For more information, see the Using the SQLsafe XSP Technical Solution located in the Documentation folder (by default, C:\Program Files\Idera\SQLsafe\Documentation).

Remote Backup Agent install fails when SQL Server is not installed

In order to install the SQLsafe Backup Agent remotely, the computer from which you install SQLsafe must have a version of SQL Server already installed. For more information, see the software requirements.  

Table Restore wizard is no longer available in SQLsafe version 6.0 or later

...