Date: Fri, 29 Mar 2024 12:41:24 +0000 (UTC)
Message-ID: <1024011634.70003.1711716084183@ip-10-0-1-26.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_70002_2030065410.1711716084179"
------=_Part_70002_2030065410.1711716084179
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
New features and fixed issues
New features and fixed issues
=
SQL Safe Backup provides the following new features and fixed issues.
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 Ser=
ver 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
- SQLSAFE-14=
275 CLI and T-SQ=
L commands are now working properly for all SQL Safe Backup operations.
Policies
- SQLSAFE-14=
247 Backup operation statuses are now displayed properly in the=
Policy Status tab for SQL Server versions older than 2012.
Restore
- SQLSAFE-14=
267 Performing a Point-In-Ti=
me restore no longer leaves the database in "recovering" state.
8.6 New Features
Azure / Amazon S3 Cloud
- SQL Safe Backup 8.6 version now supp=
orts 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 no=
w supports Microsoft Windows 2019.
8.6 Fixed Issues
Availability Group
- SQLSAFE-14=
063 SQL Safe Backup operations are now working properly in avai=
lability groups.
Backup
- SQLSAFE-14=
206 Users can now perform ba=
ckup operations to an Azure location specifying the container name as "Page=
blob".
Backup / Restore
- SQLSAFE-11=
856 SQLSAFE-13890 SQLSAFE-13924 SQLSAFE-14009&nbs=
p;SQLSAFE-1416=
1 Users can now backup and r=
estore large databases to/from Azure and Amazon S3 locations.
- SQLSAFE-13=
539 Users can no=
w backup and restore to/from Azure and Amazon S3 cloud base storage using s=
ubfolders.
- SQLSAFE-14=
193 Users can no=
w 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.
- SQLSAFE-14=
087 Backup and r=
estore operations are now working properly for TSM and Amazon S3 locations.=
Cluster Environment
- SQLSAFE-13=
853 Users can now perform Ob=
ject Level Recovery and Virtual Database operations to an agent in a cluste=
red environment.
FIPS Compliance
- SQLSAFE-13=
847 Users can now perform ba=
ckup and restore operations when enabling FIPS compliance. They can save Az=
ure Pub Account details in the Web and Desktop Console.
Policies
- SQLSAFE-13=
546 Users cannot run backup =
policies to a snapshot database.
- SQLSAFE-14=
192 Users can now perform ba=
ckup policies using subfolders from azure locations.
Restore
- SQLSAFE-13=
952 The Restore wizard is no=
w working properly when restoring backed up databases to Amazon S3 location=
s in a remote instance.
- SQLSAFE-14=
053 Instant Restore operatio=
ns 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
- SQLSAFE-14=
049 After upgrading from SQL=
Safe Backup 8.5.2 to 8.6, the registration of the Web Console is now succe=
ssful.
- SQLSAFE-14=
123 Users can now upgrade th=
e SQL Safe Agent Components from an old SQL Safe Backup product version to =
8.6 version properly.
------=_Part_70002_2030065410.1711716084179--