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

Installation

• The installation of SQL Safe Backup fails in scenarios where an existing SQL Safe database already exists.To avoid a failure, make sure that the specified name of the SQL Safe repository database matches the existing database.

SQL Safe Backup Agent

• When deploying the SQL Safe Backup Agent components from the SQL Safe Management Console, an error message appears indicating an installation failure. Refreshing the SQL Server instance will detect if the SQL Safe Backup version or the deployment was successful. Deployments of the SQL Safe Backup Agent components from the SQL Safe Web Console does not present this issue.

Policies

• The SQL Safe Management Console can become unresponsive when editing a policy that contains a server where the SQL Safe Backup Agent is unreachable.

Known Issues for 8.4.2

Installation

• The SQL Safe Filter Service and SQL Safe OLR Service can be installed on Windows version 10 and later once you disabled the Secure boot (in the VM properties for a VM or the BIOS settings for a physical machine).

...

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

...

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

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. 

...

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

...

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

...

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

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. 

...