Versions Compared

Key

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

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

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.

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

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.

...