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.

...

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

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.

...

• 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

IDERA Dashboard

• Instances removed from web and desktop console are still displaying under Dashboard Managed InstancesLow 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

TSM

• Low level file selection is not working properly with TSM backup/restoreInstances 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.

...