Versions Compared

Key

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

...

Note

SQL Safe is ONLY compatible with IDERA Dashboard version 4.6 and with limited support.

Known Issues for 9.2.1

Backup

  • Backup operations are skipped for databases set on an always-on setting in a secondary server.

Virtual Database

  • SQL Virtual Databases cannot be renamed or changed from their default location.
  • You cannot unmount Virtual Databases through the CLI commands.

Known Issues for 9.2

SQL Safe Agent

  • A communications delay when working with SQL Server instances in a clustered configuration has been identified. A patch is available for this issue, please contact
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
    .
  • After upgrading the management components to 9.2 and using older SQL Safe agent components, backups may be failing. A patch is available for this issue, please contact
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
    .

Known Issues for 9.1

SQL Safe Repository

  • The installation of the SQL Safe repository fails when it is installed on a SQL Server version lower than SQL Server 2019.

Known Issues for 9.0

Installation

  • The remote installation of the SQL Safe Backup agent fails in scenarios where the Microsoft Visual C++ 2015 redistributable or greater is previously installed in the machine. To install the SQL Safe Backup agent properly, log onto a machine directly and install the Agent\Management components.
  • During the installation of SQL Safe, the installer may identify that the VC++2015 redistributable or greater is not installed and suggests that you install it. The installer uses a registry key to detect whether the correct version of the VC++ redistributable is installed. There is a Microsoft bug with some versions of VC++ that cause causes that registry key to be deleted which triggers this problem. However, during your SQL Safe installation, you are prompted with dialog boxes to complete the installation of the required VC++ version.

...

  • The remote installation of the SQL Safe Backup agent fails in scenarios where the Microsoft Visual C++ 2015 redistributable or greater is previously installed in the machine. To install the SQL Safe Backup agent properly, log onto a machine directly and install the Agent\Management components.
  • During the installation of SQL Safe, the installer may identify that the VC++2015 redistributable or greater is not installed and suggests that you install it. The installer uses a registry key to detect whether the correct version of the VC++ redistributable is installed. There is a Microsoft bug with some versions of VC++ that cause causes that registry key to be deleted which triggers this problem. However, during your SQL Safe installation, you are prompted with dialog boxes to complete the installation of the required VC++ version.

...

  • When saving native format SQL Server backups and storing to Azure cloud storage, customers need to confirm that their Azure accounts are of the type "General Purpose". This is not a SQL Safe Backup limitation but a Microsoft mandate, please refer to the 
    Newtablink
    aliasMicrosoft Support document
    urlhttps://support.microsoft.com/en-in/help/3177997/backup-to-url-fails-with-nonrecoverable-i-o-error-3271-in-sql-server
    .
  • On SQL 2012 instances, databases may be skipped from jobs without displaying its their skipped status or an error in the Policy Status view.   Please contact 
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
     for further assistance.

...

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

...

  • When submitting an ad-hoc native backup operation against SQL Safe Agents prior to the 8.4 version, the operation will not perform any work. Native backup operations are only supported for SQL Safe Backup Agents 8.4 version and later.

...

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

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

  • IDERA Dashboard does not support Microsoft Windows 2003.

...

  • The SQL Safe Management Service and SQL Safe Backup Agent must be must be upgraded to the 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.

...

  • 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 as the Primary location in the 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 the web and desktop console are still displaying under Dashboard Managed Instances.

...

  • 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 as the Primary location in the Log Shipping Policy wizard fails with an error even though the Service account has full permissions to the shared path.  

...

IDERA Dashboard

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

...

  • SQL Server Agent service account authentication for the Network path provided as the Primary location in the 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.

TSM

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

...

  • 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 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 the location paths of stripped files are the same as that those of the mirror paths when changing from single to stripped location type.

  • Users may find that pressing the "Enter" key in the Backup, Restore, and Log Shipping wizards may 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 the 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 fails back to the original node where the operation was started.

  • Users that who 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.

...

When some users upgrade to SQL Safe 6.5 or later, the backup file names using the %timestamp% macro may change. This issue affects users who have SQL Safe to groom their backup files at backup time, using either the the -delete command line option or the Remove files older than an option in the Backup Policy wizard. Previous versions expand %timestamp% to the UTC time of the backup.

...

Note that if you specify to overwrite, SQL Safe overwrites the existing files instead of appending the new information. If you upgrade from a release earlier than SQL Safe 6.4, appends fail and display an error message.

Setup The setup program removes the previous version when the upgrade fails

If the upgrade fails while you are upgrading from a previous version of SQL Safe, the setup program removes the previous version from the SQL Server computer on which you attempted the upgrade.

...

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

...

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 the SQL Server itself. The degree of impact varies depending on environmental conditions.  For For more information about SQL Server Instant File Initialization, see the Microsoft Knowledge Base article located at Database Instant File Initialization.

...

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

...

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

...