Page History
SQL Safe Backup provides the following new features and fixed issues.
9.
...
4 New Features
Installation
Repository
- OIDC Authentication Method for connecting to the Older agents need to be upgraded to
- SQL Safe Backup 9
- Repository. 3 version.
Instances
- When registering an instance, set the "Untrusted Domain" option to identify whether a server is trusted or not.
Upgrades
- New communication protocols.
- Backup agent upgrades:
Warning Before upgrading your Backup Agents, ensure the service account is set correctly. By default, it runs under the LocalSystem user, which may lack the necessary permissions for backup operations. Confirm the appropriate account is configured to prevent issues during the upgrade.
9.3 Fixed Issues
9.4 Fixed Issues
CLI CommandBackup
Status colour Green title SQLSAFE- 15242 Notification emails are generated properly for backup operations.
The xp_ss_restoreheaderonly stored procedure is working properly now.15300
Instance
Status colour Green title SQLSAFE- 15240 Set the destination path for your striped backups.
The SQL Server friendly name assigned to an instance remains consistent across all SQL Safe operations and wizards.15132
LicenseCluster Environment
Status colour Green title SQLSAFE- 15167 Perform backups properly on the secondary node of a non-Avaialbility Group database.
Remove servers from the License Key Manager.1614
PolicyInstances
Status colour Green title SQLSAFE- 14741 SQL Server instances using IPSEC are running normally on SQL Safe.
Policies
15368 Status colour Green title SQLSAFE- 15213 Run jobs through Extended Stored Procedures.
Policies with a large number of databases are executed correctly.15382
UpgradeRestore
Status colour Green title SQLSAFE- 15198 When restoring from Azure Blob, SQL Safe displays all files.
...
After upgrading SQL Safe to version 9.4, the Extended Store Procedure is working properly.15373 Status colour Green title SQLSAFE- 15220
After upgrading SQL Safe to version 9.4, the SQL Safe Management service starts automatically15394 Mount Virtual Databases properly using the CLI commands- .
