Page History

...

• The Retry reading backup files after network errors check box on the Backup Sets tab of the SQL Safe Database Restore wizard is renamed Enable network resiliency. The functionality remains the same while the name of the field was changed to improve usability.

• The Verify (checks integrity, no data restored) option moved from the Recovery State tab to the Target tab in the SQL Safe Database Restore wizard.

• SQL Safe now properly displays the selection in the Select backup sets manually box when the user switches from one database to another using the Restore wizard. This issue affected users attempting to restore multiple databases.

• New rolling logs improve troubleshooting by avoiding issues that result when a single log file continues to store information and grows without a limit. This file can cause performance issues and be hard to search for clues to find the issue you are trying to resolve. This feature is recommended for use only when instructed by IDERA support.

• SQL Safe Reporting no longer displays an error message when a user attempts to run the Last Backup report.

• Dependent SQL Safe operations in a series are now associated so that when one of the operations fails, all of the following operations are canceled.

• The Restore wizard now properly handles the LSN chain when there is an intermediate Full backup.

• Performance updates improve the speed of the SQL Safe installation.

• Enhancements to SQL Safe memory usage decrease the chance of memory leaks or fragmentation.

• Users can now backup a database using only one thread as specified in the Thread Count field on the SQL Safe Backup Policy wizard Options tab.

• SQL Safe alerting now properly handles log shipping restore schedule start times when set to a non-default value.

• SQL Safe network retry updates fixed an issue that resulted when the SQLAgent job hung during a backup and the network retry function is disabled.

• SQL Safe no longer causes an extreme load on the tempdb while backing up a database.

• SQL Safe now properly handles FQDN names when connecting to the Backup Service.

• SQL Safe no longer truncates text within the Result Text field.

• Users can now sort the list of databases in the SQL Safe Backup wizard by clicking the appropriate column name.

• SafeToSQL users who submit an encryption password that fails verification now receive the correct error message.

• The Backup Policy wizard no longer re-runs the file access check after a user edits the policy unless the change was made to the Location tab.

• SQL Safe now allows encryption passwords of more than 24 characters. This update allows users to implement pass phrases as a more effective method of security.

• Users no longer experience an issue causing the default SQL Server instance file path to change when re-running a failed or skipped backup.

• SQL Safe now features Cancel buttons in a number of areas available when the user runs a task. You can cancel a task when performing log shipping re-initialization, deleting a policy, enabling or disabling a policy, running a job, re-synching a policy, or updating a license.

• SQL Safe now prompts the user immediately after a user account credential check fails.

• Improved Command-line Interface (CLI) documentation regarding SQL Safe and TSM server is located in the SQL Safe Help topic, Back up to the TSM Server.

• Accessing sample Command-line Interface (CLI) and Extended Stored Procedure (XSP) script sample access is now documented in the Product components and architecture

• Users who submit a script that contains unnecessary backslash characters in the file path no longer receive an error message stating, "Value cannot be null." SQL Safe now omits the unnecessary backslash characters and continues the operation.

• Users can now create and run log shipping or restore policies on a database that contains multiple files on different drives.

• The SQL Safe Management Console now contains the proper certificate so the user no longer receives a request for credentials each time they launch the Console. This issue affected Windows 2008 users replying on user account control functionality.

• The default Connection Settings detail on the SQL Safe Backup wizard Locations tab no longer retains any changes made during previous use.

• Users can now quickly find an instance in the SQL Safe Database Restore wizard Databases tab by typing the name directly into the instance field and selecting the appropriate instance when it appears.

• Users can now successfully change the IP address on the server hosting the SQL Safe Management Service without causing IP address resolution issues with the Backup Agent.

• Users attempting to restore an older, inactive backup file stored on a TSM server no longer receive an error message.

• SQL Safe XSP now correctly handles wide-character Unicode file names.

• Updated file access permissions fixed a performance issue caused when SQL Safe ran the Backup Policy File Access Check on every database within a SQL Server instance.

• SQL Safe performance is improved when a user attempts to create or run a policy or load the policy status pages.

• Users with large SQL Safe repositories no longer encounter a timeout when accessing the Backup Sets page in the Management Console during a restore.

• If a backup policy specifies both a FULL as well as DIFF or LOG backups to be performed, the FULL backup is automatically run for new databases that have no previously-performed FULL backup existing at the time the FULL, DILL, or LOG backup is scheduled, whichever occurs first.

• The SQL Safe Management Console no longer prevents users from deleting some policies. These policies failed when loading from the Repository before the user attempted to delete the policy.

• PDF files of the SQL Safe Help and SQL Safe Release Notes now include hot links to access related information within the document.