Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

8.3 New Features

  • When performing backup and restore operations, users are now able to specify Microsoft Azure Blob Storage as the location for their backup and restore files.
  • Copying policies is now available from the Policy tab. Users can now copy preexisting policies and modifying their settings before copying them. 
  • The installer has been improved to allow the installation of all SQL Safe components and the Idera Dashboard in one single wizard. 
  • Users can now perform striped backups to tape devices using Tivoli Storage Manager.
  • SQL Safe is now integrated with IDERA Dashboard 3.0.  

8.3 Fixed Issues

  • Users do not experience error messages anymore when performing the bulk "Backup Again" operation in the Operation History tab.
  • Users can now sort the databases list of the backup wizard according to Database Name, Last Backup, or Space Used. 
  • The Restore Wizard now updates the point-in-time date accurately after clicking the Apply option. 
  • "Restore again" and "Restore with different options" are now available for Instant Restore operations in the Operation History tab. 
  • Links from "Databases with failed backups" and "Databases with failed restores" in the "My Environment" section of the Home tab now direct to the correct information in the Operation History tab.
  • Users can now access a tool tip that provides the complete name of SQL Server instances and databases displayed in the bar graphs of the Home tab.
  • SQL Safe now supports TSM (Tivoli Storage Manager) 7.1.1.1.
  • Users can now use wildcards such as %, _, [ ],[^] to find their information more quickly through the filters.
  • Users can now perform the "Restore again" operation as a bulk operation in the Operation History tab without experiencing error messages. 
  • When upgrading to a new version, users can now select previous SQL Safe display names or create a new one.

8.2 New Features

SQL Safe 8.2 includes the following features in its web console:

...

SQL Safe now supports SQL Server Availability Groups and allows you to perform backup and recovery strategies on your primary and secondary replicas.

7.4 Fixed issues

You no longer need to restart the InstantRestore service when adding a new drive to a server.

7.2.1 New features

Improved backup performance

...

SQL Safe 7.1 is SQL Server 2012 RC0 compatible. This version of SQL Safe is not certified against newer builds of SQL Server and should not be used with these builds in a production environment. IDERA provides experimental support while you use your installation in a testing environment to ensure the features you rely on most are working as or better than expected.

7.4 Fixed issues

You no longer need to restart the InstantRestore service when adding a new drive to a server.

7.1 Fixed issues

  • Users who have a case-sensitive SQL Server user name no longer finds SQL Safe failing to create a job. This issue was the result of SQL Safe adding the characters in an all lowercase format.
  • SQL Safe now prompts for a user name and password if a user runs the SQL SafeCmd DELETE command when they do not have access to the remote file system.
  • This release fixes an issue that caused some users attempting to upgrade to SQL Safe 7.0 to receive a message stating that a previous version already exists.
  • An issue preventing the backup service from starting after some users upgraded to SQL Safe 7.0 is resolved.
  • Restore policies no longer become out of sync with the database for users who have multiple data files.
  • An issue occurring during an upgrade that prevented backups from starting is resolved. In the job history, this issue logged an error stating, "The process could not be created for step 1 of job X (reason: The system cannot find the file specified). The step failed."
  • A data format issue that caused some users to see a number of their policies as "Not Loaded" is fixed. All policies should successfully appear after any SQL Safe version upgrade.
  • SQL Safe now prompts the user to sync policies after changing SQL authentication details for a SQL Server.

...