Versions Compared

Old Version 4

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 5

changes.mady.by.user Nadja Pollard

Saved on

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  NewtablinkaliasSupporturlhttp://Support (www.idera.com/support/faq).

Known issues for 7.4

  • When a backup operation in SQLsafe is performed at the same time as the native SQL Server, the successful backup job on SQLsafe 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 location paths of stripped files are the same as that 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 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 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 back to the original node where the operation was started.

  • Users that select the SQLsafe Backup Agent to create policies on servers where the timezone has been changed may need to restart the SQLsafe Backup Agent service to update the timezone and ensure policies run on the correct schedules.

...

In order to install the SQLsafe Backup Agent remotely, the computer from which you install SQLsafe must have a version of SQL Server already installed. For more information, see the software requirements.  

Table Restore wizard is no longer available in SQLsafe version 6.0 or later

To restore objects and data from your backup files, use the new Idera SQL virtual database tool. For more information, see Recover objects using SQLvdbSQL virtual database.

FIPS-compliant encryption no longer requires additional software when installing SQLsafe version 6.0 or later

...