Versions Compared

Old Version 35

changes.mady.by.user Alejandra Rivera

Saved on

compared with

New Version 36

changes.mady.by.user Alejandra Rivera

Saved on

Key

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

SQL Safe Backup provides the following new features and fixed issues.

8.5.2 New Features

Backup

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

IDERA Dashboard

  • SQL Safe Backup is now integrated with IDERA Dashboard 4.6.0.9.

SQL Safe Web Console

  • The SQL Safe Web Console includes an additional tab named Advanced for editing properties of a registered instance.

8.5.2 Fixed Issues

Availability Groups

  • Status
    colourGreen
    titleSQLSAFE-13888
     Users can now perform Full/Differential backups on the secondary replica and Full/Differential policies on the primary replica.

Backup

  • Status
    colourGreen
    titleSQLSAFE-12892
     The verify bakcup 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.

Cluster Environment

  • Status
    colourGreen
    titleSQLSAFE-13875
     Users can now deploy the Backup Agent onto a Cluster Environment from the SQL Safe Management Console.

Desktop Console

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

Grooming

  • Status
    colourGreen
    titleSQLSAFE-12842
     The repository grooming is now set to 365 days.
  • Status
    colourGreen
    titleSQLSAFE-13854
     The grooming bitesize option is now set to 1000.

Installation

  • Status
    colourGreen
    titleSQLSAFE-13984
     The recovery model and page verify settings are now set properly when installing SQL Safe Backup.

License

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

Management Service

  • Status
    colourGreen
    titleSQLSAFE-12850
     Log entries are now working properly.

Policies

  • Status
    colourGreen
    titleSQLSAFE-9560
     Restore policies are now working properly when changing the target database name of a restore performed from one server to another.
  • Status
    colourGreen
    titleSQLSAFE-9702
     Backup policies are now scheduled as expected.
  • Status
    colourGreen
    titleSQLSAFE-13406
     The Copy Policy feature is now scheduling policies properly.
  • Status
    colourGreen
    titleSQLSAFE-14060
     When performing a backup policy, the location type is now set properly.

Restore

  • Status
    colourGreen
    titleSQLSAFE-13903
     Users can now restore backup files that are moved manually to Amazon S3. Once the file is moved to Amazon S3, rename the file, and perform the restore.
  • Status
    colourGreen
    titleSQLSAFE-13938
     Users can now perform restores with a remote instance using a non-default port number.

T-Log Backup

  • Status
    colourGreen
    titleSQLSAFE-13908
     Improved user experience with T-Log backup operations.

Upgrade

  • Status
    colourGreen
    titleSQLSAFE-13976
     Users can now upgrade manually SQL Safe Backup from 8.4.2 to 8.5.1 using the agent. 

8.5.1 New Features

Amazon

  • SQL Safe Backup now supports the Amazon AWS GovCloud S3 in the SQL Safe Management Console and SQL Safe Web Console.

...