Versions Compared

Key

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

SQL Safe is ONLY compatible with IDERA Dashboard version 4.6 and with limited support.

9.1 New Features

Azure

  • New Authentication Methods are available: Key and SAS (Shared Access Signature Service URL).

Backup in Desktop Console

  • Users can now run Pre/Post-Backup Commands.

Upgrade

  • A new wizard to upgrade SQL Safe Agents is available.

9.1 Fixed Issues

Amazon S3 Cloud

  • Status
    colourGreen
    titleSQLSAFE-14622
    Restores of backup files with FILESTREAM files are working properly now.
  • Status
    colourGreen
    titleSQLSAFE-14842
    Users can now rename the bucket properly.

Availability Group

  • Status
    colourGreen
    titleSQLSAFE-14341
    Full and Differential backups are working properly on Availability Groups.

Azure Cloud

  • Status
    colourGreen
    titleSQLSAFE-14619
    Backup operations to the Azure Storage account are running faster than before.

Installation

  • Status
    colourGreen
    titleSQLSAFE-13999
    Users can now install remotely the SQL Safe Backup Agent where the Microsoft Visual C++ 2015 redistributable or greater is previously installed.

Object Level Recovery

  • Status
    colourGreen
    titleSQLSAFE-14554
    Object Level Recovery operations on remote instances using CLI or XSP are working properly now.

Policies

  • Status
    colourGreen
    titleSQLSAFE-14393
    Users can now perform log shipping policies properly using CLI with and without encryption.
  • Status
    colourGreen
    titleSQLSAFE-14572
    The SQL Server Agent is working properly when performing backup policies.

Virtual Database

  • Status
    colourGreen
    titleSQLSAFE-14733
    The Virtual Database is mounting the original database.

9.0 New Features

User Interface

  • New User Interface features include UI Scaling (support for 4K monitors and scaled fonts) and a new dark mode theme.

8.7.2 New Features

Amazon S3 Cloud

  • The StorageClass parameter is now available when backing up to Amazon S3 Cloud (AWS S3).

SQL Safe Repository

  • Users can now record the cluster details in the SQL Safe Repository.

8.7.2 Fixed Issues

Azure Cloud

  • Status
    colourGreen
    titleSQLSAFE-14448
    Backup and Restore operations are allowed on Azure File storage and Azure Blob storage.

Backup / Restore

  • Status
    colourGreen
    titleSQLSAFE-13991
    Backup and Restore operations of a database from an Untrusted Domain server are successful.
  • Status
    colourGreen
    titleSQLSAFE-14381
    Backup and Restore operations are allowed from Untrusted Domains.
  • Status
    colourGreen
    titleSQLSAFE-14559
    Backup and Restore operations are working properly on the Amazon S3 cloud.

CLI Command

  • Status
    colourGreen
    titleSQLSAFE-14296
    Restore Policies are working properly through CLI commands for backups in the Amazon S3 cloud.

Instant Restore

  • Status
    colourGreen
    titleSQLSAFE-13868
    Restore Hydration operations can be canceled on the Management Console.

Management Service

  • Status
    colourGreen
    titleSQLSAFE-14268
    The Management Service is working properly.

Object Level Recovery

  • Status
    colourGreen
    titleSQLSAFE-14425
    Reference objects are included in Object Level Recovery operations.

Policies

  • Status
    colourGreen
    titleSQLSAFE-14196
    Backup and Restore policies are working properly for the Azure cloud.
  • Status
    colourGreen
    titleSQLSAFE-14255
    SQL Safe detects when a policy is out of sync.

Restore

  • Status
    colourGreen
    titleSQLSAFE-14265
    The Restore Again option is assigning properly the new path location.

SQL Safe Agent

  • Status
    colourGreen
    titleSQLSAFE-14130
    In untrusted domains, Windows Authentication is blocked and the SQL Safe Agent authenticates using SQL Server Authentication.

Upgrade

  • Status
    colourGreen
    titleSQLSAFE-13889
    Upgrade the repository when the temporary database has been previously backed up. Please contact support for further assistance.
  • Status
    colourGreen
    titleSQLSAFE-14129
    After upgrading SQL Safe Backup, the registration of the Web Console is successful.

Virtual Database

  • Status
    colourGreen
    titleSQLSAFE-14626
    Virtual Database operations are working properly for both local and remote instances.

8.7.1 New Features

Cloud Support

  • Extended support is now available for cloud backups and restores from Azure and Amazon S3.

Desktop Console

  • The user experience has been improved in the Desktop Console.

Object Level Recovery / Virtual Database

  • The Object Level Recovery and Virtual Database functionalities are now refined and reinforced.

8.7.1 Fixed Issues

Backup

  • Status
    colourGreen
    titleSQLSAFE-14526
    Backup files are now deleted from the temporary download location while performing a
    backup.

Cloud Storage

  • Status
    colourGreen
    titleSQLSAFE-14460
    Amazon S3 and Azure cloud storage performance has been improved to load large backup
    files.
  • Status
    colourGreen
    titleSQLSAFE-14264
     
    Status
    colourGreen
    titleSQLSAFE-14513
    Restore operations from Amazon and Azure cloud storage through T-SQL
    and CLI commands are now working properly.

Notifications

  • Status
    colourGreen
    titleSQLSAFE-14132
    Email notifications are sent properly now after the product upgrade.

Operation Status

  • Status
    colourGreen
    titleSQLSAFE-14544
    Queued operations are now displayed correctly in the Operation Status window.

Policies

  • Status
    colourGreen
    titleSQLSAFE-14166
     
    Status
    colourGreen
    titleSQLSAFE-14259
    Status
    colourGreen
    titleSQLSAFE-14280
     
    Status
    colourGreen
    titleSQLSAFE-14500
     
    Status
    colourGreen
    titleSQLSAFE-14562
    Policies performance has
    been improved.

Virtual Database and Object Level Recovery

  • Status
    colourGreen
    titleSQLSAFE-14232
    Virtual Database and Object Level Recovery operations are now supported in a cluster
    environment after a failover.
    Make sure you set up manually the VDBMetadata directory structure before a Virtual Database operation is
    attempted on an availability group environment.

8.7 New Features

Object Level Recovery

  • The Object Level Recovery functionality is now available in the Desktop Console.

Policies

  • Users can now copy policies in the Desktop Console.

Virtual Database

  • The Virtual Database functionality is now available in the Desktop Console.

8.6.1 New Features

Backup and Restore operations

  • SQL Safe Backup now supports backup compression for TDE-enabled databases with native SQL Server (.bak) format.
  • SQL Safe Backup now supports backup and restore for Change Data Capture (CDC) enabled databases preserving the CDC metadata and capture \ cleanup jobs.

Support for Microsoft SQL Server 2019

  • IDERA SQL Safe Backup 8.6.1 version now supports Microsoft SQL Server 2019 for all operations.

8.6.1 Fixed Issues

CLI and T-SQL Commands

  • Status
    colourGreen
    titleSQLSAFE-14275
     
    Status
    colourGreen
    titleSQLSAFE-14269
     CLI and T-SQL commands are now working properly for all SQL Safe Backup operations.

Policies

  • Status
    colourGreen
    titleSQLSAFE-14247
     Backup operation statuses are now displayed properly in the Policy Status tab for SQL Server versions older than 2012.

Restore

  • Status
    colourGreen
    titleSQLSAFE-14267
     Performing a Point-In-Time restore no longer leaves the database in a "recovering" state.

8.6 New Features

Azure / Amazon S3 Cloud

  • SQL Safe Backup 8.6 version now supports Azure and Amazon S3 subfolders.

Cloud Environment

  • Redesigned cloud backup and restore operations for Azure and Amazon S3 storage.

Support for Microsoft Windows 2019

  • IDERA SQL Safe Backup 8.6 version now supports Microsoft Windows 2019.

8.6 Fixed Issues

Availability Group

  • Status
    colourGreen
    titleSQLSAFE-14063
     Users can now host their SQL Safe Backup repository databases in an availability group environment. The SQL Server instances are registered using the listener name. For both cases, the license is tied to the listener name instead of each node. Keep in mind that if the availability group listener is registered and licensed instead of the node, then non-availability group databases would not be visible in SQL Safe Backup.

Backup

  • Status
    colourGreen
    titleSQLSAFE-14206
     Users can now perform backup operations to an Azure location specifying the container name as "Page blob". 

Backup / Restore

  • Status
    colourGreen
    titleSQLSAFE-11856
     
    Status
    colourGreen
    titleSQLSAFE-13585
     
    Status
    colourGreen
    titleSQLSAFE-13890
     
    Status
    colourGreen
    titleSQLSAFE-13924
     
    Status
    colourGreen
    titleSQLSAFE-14009
     
    Status
    colourGreen
    titleSQLSAFE-14161
     Users can now backup and restore large databases to/from Azure and Amazon S3 locations.
  • Status
    colourGreen
    titleSQLSAFE-13539
     
    Status
    colourGreen
    titleSQLSAFE-14083
     Users can now backup and restore to/from Azure and Amazon S3 cloud base storage using subfolders.
  • Status
    colourGreen
    titleSQLSAFE-14193
     
    Status
    colourGreen
    titleSQLSAFE-14194
     Users can now perform AdHoc backup and AdHoc restore operations to Amazon S3 and Azure cloud storage using subfolders. They need to make sure to select the Force Restore (replace) option when performing restore operations.
  • Status
    colourGreen
    titleSQLSAFE-14087
     
    Status
    colourGreen
    titleSQLSAFE-14091
     Backup and restore operations are now working properly for TSM and Amazon S3 locations.

Cluster Environment

  • Status
    colourGreen
    titleSQLSAFE-13853
     Users can now perform Object Level Recovery and Virtual Database operations to an agent in a clustered environment.

FIPS Compliance

  • Status
    colourGreen
    titleSQLSAFE-13847
     Users can now perform backup and restore operations when enabling FIPS compliance. They can save Azure Pub Account details in the Web and Desktop Console.

Policies

  • Status
    colourGreen
    titleSQLSAFE-13546
     Users cannot run backup policies to a snapshot database.
  • Status
    colourGreen
    titleSQLSAFE-14192
     Users can now perform backup policies using subfolders from azure locations.

Restore

  • Status
    colourGreen
    titleSQLSAFE-13952
     The Restore wizard is now working properly when restoring backed up databases to Amazon S3 locations in a remote instance.
  • Status
    colourGreen
    titleSQLSAFE-14053
     Instant Restore operations to large databases are now working properly when it is restored to a new database or to an existing database using the "Force Restore" option.

Upgrades

  • Status
    colourGreen
    titleSQLSAFE-14049
     After upgrading from SQL Safe Backup 8.5.2 to 8.6, the registration of the Web Console is now successful.
  • Status
    colourGreen
    titleSQLSAFE-14123
     Users can now upgrade the SQL Safe Agent Components from an old SQL Safe Backup product version to the 8.6 version properly.


8.5.2 New Features

Backup

  • The SQL Safe Management Console has been improved to allow users to perform backups in native (.bak) format.

...

  • Status
    colourGreen
    titleSQLSAFE-12892
     The verify bakcup backup option is now working properly when performing backups to TSM.
  • Status
    colourGreen
    titleSQLSAFE-13438
     Users can now backup large databases to Amazon S3.
  • Status
    colourGreen
    titleSQLSAFE-13521
     Scheduled backup jobs are now working properly in a failover cluster environment.
  • Status
    colourGreen
    titleSQLSAFE-13938
     Users can now perform backups with a remote instance using a non-default port number.
  • Status
    colourGreen
    titleSQLSAFE-13908
     Improved user experience with T-Log backup operations.

...

  • Status
    colourGreen
    titleSQLSAFE-13766
     The Last Operation Status section is now updating properly the list of backups that succeeded and failed.

Grooming

...

  • Status
    colourGreen
    titleSQLSAFE-13652
     The license key is now working properly when adding instances in the Web Console.

...

  • Status
    colourGreen
    titleSQLSAFE-13346
     SQL Safe Backup policies automatically performs perform a full backup operation when a differential backup operation fails due to a lack of a full backup.

  • Status
    colourGreen
    titleSQLSAFE-12893
    The  The storage options of the Backup again with different options to Tivoli Storage Manager (TSM) are working properly now in the SQL Safe Management Console.
  • Status
    colourGreen
    titleSQLSAFE-12894
     The High Level and Low Level text boxes of the Backup with different options to Tivoli Storage Manager (TSM) are recognizing the data properly in the SQL Safe Web Console.
  • Status
    colourGreen
    titleSQLSAFE-9555
     SQL Safe Backup displays now properly the progress of a backup operations that are being performed without compression.
  • Status
    colourGreen
    titleSQLSAFE-13892
     Backup and restore operations performed in native file format can have timeout values modified through a registry key update.
  • Status
    colourGreen
    titleSQLSAFE-13225
     Percentage values are no longer included in the Result Text of backup and restore operations.

...

  • Status
    colourGreen
    titleSQLSAFE-13350
     The preferences set on either the SQL Safe Web Console or SQL Safe Management Console are kept the same when performing operations.
  • Status
    colourGreen
    titleSQLSAFE-13891
     Users can now set long passwords for the deployed Backup Agents Agent service account in the Agent Deployment option.
  • Status
    colourGreen
    titleSQLSAFE-13842
     The SQL Safe Management Console is no longer reporting a false failure when deploying the SQL Safe Backup Agent to a remote server.

...

  • The groom settings for SQL Safe Backup have been improved to allow users to granularly control the amount of operational history that is to be maintained by SQL Safe Backup. This improvement will provide users with more control on over maintaining the size of the SQL Safe repository database.

...

  • Status
    colourGreen
    titleSQLSAFE-13366
     Users can now add a database to an existing backup policy.
  • Status
    colourGreen
    titleSQLSAFE-13304
     In the SQL Safe Web Console, the filename is now auto-generated when enabling the option to delete backup files in the backup policy wizard.
  • Status
    colourGreen
    titleSQLSAFE-13194
     In the SQL Safe Web Console, the "Access Files As" option is now able to switch to the default state after providing different credentials in the Restore policy.
  • Status
    colourGreen
    titleSQLSAFE-13191
     When creating or editing a policy in the SQL Safe Web Console, the credentials specified for accessing the file system is now properly applied. 
  • Status
    colourGreen
    titleSQLSAFE-13159
     In the SQL Safe Web Console, users can run now a policy manually.
  • Status
    colourGreen
    titleSQLSAFE-12673
     In the SQL Safe Web Console, restore policies are working properly when configured to connect to the SQL instance using SQL Server Authentication.
  • Status
    colourGreen
    titleSQLSAFE-13513
     Users can now supply a UNC path when creating or modifying a policy in the SQL Safe Web Console.

...

  • Status
    colourGreen
    titleSQLSAFE-13448
     In the SQL Safe Web Console, users can now perform the verify operation using the restore wizard.
  • Status
    colourGreen
    titleSQLSAFE-13372
     In the SQL Safe Web Console, the point in time selection is working properly now in the restore wizard.
  • Status
    colourGreen
    titleSQLSAFE-13173
     In the SQL Safe Web Console, users are now able to select multiple files for restore through the File System and Target Server options.
  • Status
    colourGreen
    titleSQLSAFE-12860
     The restore wizard now correctly selects the SQL Server instance based on the user selection on the Databases tab when the Repository option is selected.
  • Status
    colourGreen
    titleSQLSAFE-12049
     The restore wizard now displays the list of instances in a sorted order on the Databases tab when the Repository option is selected.

...

  • Updated licensing files that will affect expiring subscription keys (license keys that have an expiration date). If applying for a new subscription license key, you must upgrade prior to applying the new key. Perpetual license keys (non-expiring license keys) are not impacted.

...

  • Users can mount a virtual database from backup file(s) located on a UNC share, as long as the SQL Safe Backup Service and SQL Safe OLR Service has permissions to the UNC share.
  • Mount Operations through the SQLvdb CLI Commands now recognizes the default location settings in the Graphical User Interface (GUI) and do does not require the -Move parameter for the database file.

...

  • Virtual Database (VDB) is integrated to into SQL Safe 8.4.

8.4 Fixed Issues

...

  • When adding an instance to SQL Safe Backup, users can now validate the entered credentials by running the Test Credentials button.

Backup Policy

...

  • SQL Safe Backup policies configured with the "Monitor + Automatically create backup jobs using the SQLsafe Backup Agent" action , are now running all operations as scheduled.

...

  • In the Restore Database wizard, the browse button, located in the Databases option under the File System tab, is now enabled.
  • In the SQL Safe Restore Wizard, selecting a file path using the Browse feature correctly populates the file path that was chosen.

...

  • The installer has been improved to allow the installation of all SQL Safe components and the Idera Dashboard in one single wizard.

Policies

  • Copying policies is now policies is now available from the Policy tab. Users can now copy preexisting policies and modifying modify their settings before copying them.

...

  • Users do not experience error messages anymore when performing the bulk "Backup Again" operation in the Operation History tab.

  • Users can now sort the databases list of the backup wizard according to Database Name, Last Backup, or Space Used. 

  • The Restore Wizard now updates the point-in-time date accurately after clicking the Apply option. 

  • "Restore again" and "Restore with different options" are now available for Instant Restore operations in the Operation History tab. 

  • Links from "Databases with failed backups" and "Databases with failed restores" in the "My Environment" section of the Home tab now direct to the correct information in the Operation History tab.

  • Users can now access a tool tip tooltip that provides the complete name of SQL Server instances and databases displayed in the bar graphs of the Home tab.

  • SQL Safe now supports TSM (Tivoli Storage Manager) 7.1.1.1.

  • Users can now use wildcards such as %, _, [ ], [^] to find their information more quickly through the filters.

  • Users can now perform the "Restore again" operation as a bulk operation in the Operation History tab without experiencing error messages.

  • When upgrading to a new version, users can now select previous SQL Safe display names or create a new one.

...

  • SQL Safe currently shows backup operations progress even when the compression option is not selected.   

  • If a policy with a differential backup has a database with no previous full backup, SQL Safe takes first a full backup before executing the policy.  

  • SQL Safe no longer restores logins when the option  Include database logins in the backup file is are selected for backup operations. 

  • SQL Safe accurately sends warning notifications for the  Verify step of Backup + Verify Policies. 

  • SQL Safe has now improved the logic for calculating policy schedules and sending email notifications. 

  • SQL Safe currently considers the creation date of a new database before sending notifications for missed operations schedules.

...

  • Home tab - with a general status of the environment through alerts, summary information of SQL Safe operations, managed instances, and other important data. 

  • Policies tab - with information about all SQL Safe policies existing in the users environment. 

  • Operations History tab - with of all SQL Safe operations performed in the users environment the users environment and their current status.  

  • Instances tab - with a general view of all SQL Server instances registered in the users environment. 

  • Databases tab - with general information of the databases that belong to the SQL Server instances registered in the users environment. 

  • SQL Safe Agents tab - provides information of all computers that host registered SQL Server instances and the details of related Safe Agents. 

...