Page History

...

• The licenses users add should be valid for the Centralized Licensing model. When Centralized Licensing is enabled, all licensing information is managed using the SQL Safe Management Service and each of the individual SQL Safe Backup Agent licenses are removed.

Policies

• Users should take into account that time fields for the Policies, Operation History, and Databases tabs in the SQL Safe Web Console are currently expressed in the GMT time zone.
• In the web console Policies tab, options to start jobs and disable policy are not available.  
• SQL Server Agent service account authentication for the Network path provided as Primary location in Log Shipping Policy wizard fails with an error even though the Service account has full permissions to the shared path.  

...

• Low-level file selection is not working properly with TSM backup/restore.

VDB

• Users who plan to install Safe 8.0 on the same system as VDB should obtain the VDB 2.1 buddy drop which addresses compatibility issues between the two products. Please contact IDERA Support for more information. 
• After installing SQL Safe, existing virtual databases may not be accessible. IDERA recommends to first upgrade with the VDB 2.1 buddy drop, unmount virtual databases, install SQL Safe, and then recreate the respective VDBs. Contact IDERA Support for more information.
• When uninstalling SQL Safe, users may need to reboot their computers to remove the SQLvdb Filter Service.

Other issues

• After registration, SQL Safe Web Console will list all available instances in your repository. Users have to use the options to Bulk Edit credentials to change credentials for those instances they are not able to monitor.

• The SQL Safe Web Console is not currently sending e-mail notifications for Restore Operations  

• Agent deployment service account changes made in the desktop console are not replicating in the web console

...

• Low level file selection is not working properly with TSM backup/restore.

Policies

• SQL Server Agent service account authentication for the Network path provided as Primary location in Log Shipping Policy wizard fails with an error even though the Service account has full permissions to the shared path.
• Users may find the option for wildcards is not available when defining databases to backup in the respective policy wizard. 

• In the web console Policies tab, options to start jobs and disable policy are not available.

IDERA Dashboard

• Instances removed from web and desktop console are still displaying under Dashboard Managed Instances.

VDB

• Users who plan to install Safe 8.0 on the same system as VDB should obtain the VDB 2.1 buddy drop which addresses compatibility issues between the two products. Please contact  IDERA Support  for more information. 
• After installing SQL Safe, existing virtual databases may not be accessible. IDERA recommends to first upgrade with the VDB 2.1 buddy drop, unmount virtual databases, install SQL Safe, and then recreate the respective VDBs. Contact  IDERA Support  for more information.

Other issues

• After registration, SQL Safe Web Console will list all available instances in your repository. Users have to use the options to  Bulk Edit credentials  to change credentials for those instances they are not able to monitor
• Users should take into account that time fields for the Policies, Operation History, and Databases tabs in the SQL Safe Web Console are currently expressed in the GMT time zone.
• When uninstalling SQL Safe, users may need to reboot their computers to remove the SQLvdb Filter Service. 
• The SQL Safe Web Console is not currently sending e-mail notifications for Restore Operations
• Agent deployment service account changes made in the desktop console are not replicating in the web console.

...

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

Table Restore wizard is no longer available in SQL Safe 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 Recover objects using SQL virtual database.

FIPS-compliant encryption no longer requires additional software when installing SQL Safe version 6.0 or later

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

Upgrade any Backup Agents that perform TSM backups

Due to the extensive TSM enhancements included in SQL Safe 6.4 and later, older Backup Agents are not compatible with 6.4. To ensure you can continue backing up your SQL Server data to TSM, upgrade any Backup Agent that is used to perform TSM backups in your environment.

64-bit users need additional steps to install reports

Users with 64-bit installations must follow different steps to install reports. For more information, see IDERA solution 3891, "Where do I find the SQL Safe reports," in the knowledge base on Support (www.IDERA.com/support).

SQL Safe 4.0 users who upgrade to SQL Safe 7.1 or newer cannot use existing backup policies as part of new restore policies

SQL Safe 4.0 users who upgrade to SQL Safe 7.1 or newer receive error messages if they attempt to create and then run a restore policy that includes a backup policy created on the earlier version of SQL Safe.

SQL Safe Management Service logging multiple grooming events per day

Some users may notice the SQL Safe Management Service logging multiple grooming events in the Windows Application log each day. SQL Safe should be logging only one such event per day.

Attempting to restore a database from the list of backups on the SQL Server details page fails

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.

InstantRestore performance is affected by whether the SE_MANAGE_VOLUME_NAME privilege is on your SQL Server

Enabling the SE_MANAGE_VOLUME_NAME privilege for your SQL Server account improves general SQL Server file I/O performance as well as SQL Safe 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 Knowledge Base article located at Database Instant File Initialization.

InstantRestore appears to stall when restoring databases that contain read-only file groups

SQL Safe 7.0 Beta hydration appears to stall at 99% complete when restoring databases that contain read-only file groups. SQL Server triggers InstantRestore hydration when it performs read/write I/O on the database files. Because SQL Server does not perform read/write I/O on the read-only files, hydration does not begin. Eventually, hydration begins when SQL Server performs read I/O on the files. You can delete the database if you experience this issue.

Adding a new drive requires you to restart the InstantRestore Service

When you add a new drive to a server, you must restart the SQL Safe Filter Service to make sure that the SQL Safe Filter driver is attached to the new drive. When the SQL Safe Filter Service starts, it attaches the SQL Safe Filter driver to all the fixed drives on the server. If you add a new drive after the service starts, the driver is not attached and any files created on this drive during InstantRestore do not function correctly. To avoid this issue, simply restart the SQL Safe Filter Service after adding any new drive.

...