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 

Newtab2
aliasSupportsupport
urlhttps://www.idera.com/support/supportplans
.

Known Issues for 8.7

Object Level Recovery

  • When performing an Object Level Recovery, the operation may fail if an object is selected to be restored but the associated schema is not.

Known Issues for 8.6.1

Management Service

  • The Management Service may leave open SQL Server connections in an a 'sleeping' state , until the SQL Server or SQL Safe Management is restarted. In extreme cases, the number of open connections may cause the number of concurrent connections to reach the maximum allowed by SQL Server. Please contact Support
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
     for further assistance.

Policies

  • Email notifications are not sent for Restore policy failures. Please contact Support for
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
    for further assistance.
  • When creating a restore policy from a cloud backup, specifying the Temporary Download Location path may produce an error if the SQL Server is a named instance. Please contact Support for contact 
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
    for further assistance.

Restore

...

  • 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 skipped status or an error in the Policy Status view. Please contact Support
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
     for further assistance.

Cluster Environment

...

  • Statuses for deleted databases are not removed from the Last Operation Status section of the Policy Status view. Please contact Support
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
     for further assistance.
  • When performing a restore policy from Amazon S3 location for a large database with the "Download File from Cloud" option unchecked, the SQL Safe Backup product will download the file from the cloud and choose the SQL Server data folder default destination.

...

  • SQL Safe Backup can be installed without the IDERA Dashboard on an Operating System 2003.

    Running the combined installer will display the following message: "The current Operating System is not supported by this product".

  • The remote installation of SQL Safe Backup agent fails in scenarios where the Microsoft Visual C++ 2017 Redistributable or greater is previously installed in the machine.
    To install SQL Safe Backup agent properly, log onto a machine directly, and install the Agent\Management components.

...

  • Statuses for deleted databases are not removed from the Last Operation Status section of the Policy Status view. Please contact Support
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
     for further assistance.

Upgrades

  • After upgrading from SQL Safe Backup 8.5.1 to 8.5.2, the Web Console may need to be re-registered. Go to the product registration in the Web Console, delete the SQL Safe Backup 8.5.1 product, and register the SQL Safe Backup 8.5.2 product.
  • Email notifications for SQL Safe Backup operations are not generated after upgrading to SQL Safe Backup 8.5.2. Please contact 
    Newtab2
    aliasSupportsupport
    urlhttps://www.idera.com/support/supportplans
     for further assistance.
  • The upgrade to SQL Safe Backup 8.5.2 may fail if your SQL Safe Backup installation uses a repository with a non-default name. Please contact 
    Newtab2
    aliasSupportsupport
    urlhttps://www.idera.com/support/supportplans
     for assistance in completing the upgrade.
  • The upgrade to SQL Safe Backup 8.5.2 may fail for customers who have previously backed up the system database TempDB using SQL Safe Backup. Please contact 
    Newtab2
    aliasSupportsupport
    urlhttps://www.idera.com/support/supportplans
     for assistance in completing the upgrade.

...

  • Statuses for deleted databases are not removed from the Last Operation Status section of the Policy Status view. Please contact Support
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
     for further assistance.

Upgrades

...

  • SQL Safe Backup Policies only supports support availability groups where the Backup preferences are configured for the Primary Replica. If configured with any other option, Full Backup operations will result in an error when running against any Secondary Replica.

...

  • Statuses for deleted databases are not removed from the Last Operation Status section of the Policy Status view. Please contact Support
    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
     for further assistance.

SQL Safe Backup Agent

...

  • When installing or upgrading SQL Safe Backup, 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 is removed.

Object Level Recovery

...

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

...

  • 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

    Newtab2
    aliassupport
    urlhttps://www.idera.com/support/supportplans
     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.

...

The new granular alert notifications available in version 6.6 provide more detailed feedback about policy compliance and status. Because policy jobs created with SQL Safe 6.4 or earlier do not support this feature, the Management Console policy views will not display compliance status related to previous backup or restore operations. Instead, the policy views will track the policy status from the time you upgraded. To see the status of previous backup and restore operations, use the backup/restore operation status pane on the instance and database status views.

...