SQL Safe provides the following new features and fixed issues.
8.4 New Features
Virtual Database
- Virtual Database (VDB) is integrated to SQL Safe 8.4.
Native Backups
- SQL Safe supports SQL Server native backup format for backups along with the ability to restore from native backups.
8.4 Fixed Issues
Virtual Database
- The servers that have SQL Safe Agents installed (Version 8.0.0.423) are no longer reporting “SQLvdb Filter Service version 8.0.0.423: License has expired”.
Backup policy schedule
- 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.
License
- The IDERA Dashboard now displays the SQL Safe License Key information.
SQL Safe Backup Service
- The installation or the upgrade of the remote SQL Safe Backup Agent service is no longer displaying errors.
SQL Safe product migration
- SQL Safe product migration on CWF is no longer an issue.
Operation History
- Selecting the “Backup with different options” option in the Operation History tab no longer generates exceptions.
Restore database
- In the Restore Database wizard, the browse button, located in the Databases option under File System tab, is now enabled.
SafeToSQL Utility
- SafeToSQL Utility can convert .safe backups into .bak backups and it is no longer having .NET versions conflicts.
Restore database
- In the SQL Safe Restore Wizard, selecting a file path using the Browse feature correctly populates the file path that was chosen.
Encrypted Backup
- Users are no longer prevented from completing the SQL Safe Backup Wizard when selecting the "Backup with different options" setting on a backup operation that was previously completed which resulted in an encrypted backup file.
Cloud instances
- All Azure restore operations are recorded and displayed in the Operation History tab.
Backup policy
- Users can select databases when adding all instances in the Backup Policy Wizard.
Add instances
- When adding an instance to SQL Safe, users can now validate the entered credentials by running Test Credentials button.