Page History

IDERA strives to ensure our products provide quality solutions for your SQL Server needs. The following known issues are described in this section. If you need further assistance with any issue, please contact Support (www.IDERA.com/support).

Known Issues for 8.4

IDERA Dashboard

• Safe does not currently support IDERA Dashboard’s tag management.

• Instances removed from web and desktop console are still displaying under Dashboard Managed Instances.
• IDERA Dashboard does not support Microsoft Windows 2003.

Installation

• When installing or upgrading SQL Safe, the installer is not able to parse SQL Server instance names with a space within the entered name. For example, use "SERVER,1433" instead of "SERVER, 1433".

Virtual Database

• SQL Virtual Database does not support compressed native backup from SQL Server 2014 and SQL Server 2016 instances. Attempting to mount these kinds of backups results in the following error: "The header for the backup archive cannot be read. The file may not be a valid backup archive".

• When using an appended SQL Safe Backup file, mounting a virtual database automatically selects the first backup set within the backup file.

Licensing

• 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.  

Cloud support

• When backups fail while using Windows Azure, partial files will remain unless the user deletes it manually.

TSM

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

Object Level Recovery

• The SQL Safe Management Service and SQL Safe Backup Agent must be upgraded to 8.4 version in order to run Object Level Recovery successfully.
• Object Level Recovery operations can fail when the SQLsafe repository database is hosted on a SQL Server 2014 or SQL Server 2016 instance with the following error: "Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)". The recommended workaround is to use the InstantRestore or Virtual Database feature to recover the database in an expedited fashion.

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.

Known Issues for 8.3

IDERA Dashboard

• Safe does not currently support IDERA Dashboard’s tag management.

• Product registration at the IDERA Dashboard is currently not supported in this release.
• Instances removed from web and desktop console are still displaying under Dashboard Managed Instances.

Installation

• When installing or upgrading SQL Safe, the installer is not able to parse SQL Server instance names with a space within the entered name. For example, use "SERVER,1433" instead of "SERVER, 1433".

Licensing

• 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.  

Cloud support

• When backups fail while using Windows Azure, partial files will remain unless the user deletes it manually.

TSM

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

...

• 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.

Known Issues for 8.2

TSM

• 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.

...

• 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.

...

• When a backup operation in SQL Safe is performed at the same time as the native SQL Server, the successful backup job on SQL Safe may not always show the correct timestamp in the 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 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 SQL Safe Backup Agent to create policies on servers where the timezone has been changed may need to restart the SQL Safe Backup Agent service to update the timezone and ensure policies run on the correct schedules.

...