Page History
...
- When submitting an ad-hoc native backup operation against SQL Safe Agents prior to 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.
Known Issues for 8.4
Cloud support
- When backups fail while using Windows Azure, partial files will remain unless the user deletes them manually.
IDERA Dashboard
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.
...
- 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
Licensing
- The licenses users add should be valid for the Centralized 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
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.
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. When backups fail while using Windows Azure, partial files will remain unless the user deletes them manually.
TSM
- Low-level file selection is not working properly with TSM backup/restore.
Object Level Recovery
- .
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
- 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 the 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
Cloud support
- When backups fail while using Windows Azure, partial files will remain unless the user deletes it manually.
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.
...
- 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.
...