Page History

...

• When a backup operation in SQLsafe is performed at the same time as the native SQL Server, the successful backup job on SQLsafe may not always show the correct timestamp in the filename file name of the repository
• When upgrading from an older version, the user may experience Log Shipping policies with an "out of date" message in the console. Clicking the "out of date" link will fix this issue.   
• Instead of being assigned the default location set in Preferences, users may find that location paths of stripped files are the same as that of the mirror paths when changing from single to stripped location type.
• Users may find that pressing the "Enter" key  in the Backup, Restore and Log Shipping wizards may lead them to the consecutive pages instead of inserting new lines in fields as it is done in the Backup Policy Wizard.
• When setting up a log shipping wizard with a cluster instance, users may find that secondary database file location does not display the same path as the one configured in the respective wizard but it displays the location from the primary database.
• Users may get a Last operation status of "Backups did not start as scheduled" in policies that are configured to run full and differential backups at specific times and where backups are done with no compression and no encryption.
• When running Instant Restore, users may experience problems if they have the same drive mounted as a drive letter and as a folder and they are using both paths for the Instant Restore procedure: the backup file accessed via the drive letter and the data files accessed via the folder path.
• Users may experience timeouts with the Instant Restore processes over a SQL Server 2012 SP1 with cumulative updates. 

• Users may find that when the InstantRestore process is running in a clustered SQL Server and a failover occurs during the Hydration process, the Management  Console displays the InstantRestore and Hydration processes as halted. The operation will not complete until the cluster is failed back to the original node where the operation was started.

• Users that select the SQLsafe Backup Agent to create policies on servers where the timezone has been changed may need to restart the SQLsafe Backup Agent service to update the timezone and ensure policies run on the correct schedules.

...

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    the software requirements .

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

To restore objects and data from your backup files, use the new Idera SQL virtual database tool. For more information, see see Recover objects using SQLvdb .

...

In a FIPS-compliant environment, SQLsafe uses only FIPS-compliant algorithms to encrypt your backup files. These encryption methods do not require any additional software. For more information, see see   Ensure FIPS compliance .

Upgrade any Backup Agents that perform TSM backups

...

A failure results when you attempt to restore a database file by right-clicking a file backup in the Backup/Restore Operation Status list and select Restore Database . To avoid this issue when restoring a file backup, click  Restore > Database Files  from the menu and complete the available restore wizard. You can also access the wizard from the Servers tree by right-clicking the appropriate SQL Server instance and selecting Restore Database(s) Files   .  

...

Enabling the SE_MANAGE_VOLUME_NAME privilege for your SQL Server account improves general SQL Server file I/O performance as well as SQLsafe InstantRestore. If this privilege is not enabled for the SQL Server Service, InstantRestore performance could be negatively impacted, just as with SQL Server itself. The degree of impact varies depending on environmental conditions.  For more information about SQL Server Instant File Initialization, see the Microsoft Knowledgebase Knowledge Base article located at