What's new in EMS SQL Backup 3.1.1.10364
Jan 12, 2022
- Don't miss 35%OFF for components till 27 January. Coupon code inside!
New in EMS SQL Backup 3.0.0.10110 (May 18, 2018)
- The conditions in maintenance tasks have been implemented.
- Improved maintenance tasks editor.
- Support for converting maintenance plans SSIS 2012-2017.
- The error on selecting databases and objects has been fixed.
- Some errors in the installer have been fixed.
- Improved displaying of active tasks.
- Many other minor fixes and improvements.
New in EMS SQL Backup 2.2.1.9824 (Nov 7, 2017)
- If tasks were executed simultaneously the status was displayed incorrectly sometimes. Fixed now.
- Maintenance Cleanup. Removing of backup files from Google Drive was incorrect when folder contained more than 100 files. Fixed now.
- Restore. Not all the files were displayed when browsing on Google Drive. Fixed now.
- Sometimes the 'The conversion could not be completed because the supplied DateTime did not have the Kind property set correctly' error occurred when getting logs from server. Fixed now.
New in EMS SQL Backup 2.2.0.9785 (Apr 3, 2017)
- Added support of files/filegroups backup.
- Possibility to restore separate files and filegroups from backup (partial restore).
- Bulk Restore: restoring several databases from specified backup folder with optional scheduling.
- Added support of native backups split into multiple files.
- Now it is possible to reduce policy e-mail notification text to execution status only.
- Added the option to delete backup history on dropping the database.
- Now it is possible to automatically delete backup files downloaded from remote storages/clouds after restoring.
- Extended logging added on testing connection to SMTP-server.
- Backup of files and filegroups.
- Bulk Restore: emergency restore of multiple databases.
- Scheduled check-up of multiple database backups.
- Regular database infrastructure deployment from single backup to several servers at a time.
- Lots of other improvements and bugfixes.
New in EMS SQL Backup 1.7.0.8731 (Mar 2, 2015)
- The number of maintainable databases per SQL Server instance is restricted to two databases.
- Added the possibility to copy backup files from SQL Server to the machine where SQL Backup Administration Console is running ('Get Backup To Console' wizard).
- Added the possibility to upload backups to Microsoft Azure storage.
- The ability to overwrite existing backup files in network folders (SMB/CIFS) is implemented.
- Now it is possible to move/rename folder for backups specifying new path in service settings. Moved backups are handled automatically.
- There was a restriction which prevented adding some databases in the 'Database Shipping' wizard. Fixed now.
- Lots of other improvements and fixes.
New in EMS SQL Backup 1.6.0.8587 (Dec 11, 2014)
- Added the possibility to change the time zone in the EMS SQL Backup Administration Console.
- Daylight saving time using is improved in planning policies time execution.
- Added the possibility to set HTTP proxy for uploading backup files using FTP.
- License Activation and License Deactivaion wizards are improved.
- Other improvements and bug-fixes.
New in EMS SQL Backup 1.5 (Dec 11, 2014)
- The Built-In Scheduler is implemented to execute policies on servers without SQL Server Agent, for example, SQL Server Express. The ability to use SQL Server Agent remains.
- The remote and local installation of Server-side components is improved and simplified:
- Possibility to save the settings used for remote setup.
- Numerous hints, messages and validations when setting parameters.
- Remote install through custom network share in case of absence of ADMIN$.
- Possibility to specify the port for server instance.
- Database Shipping:
- The possibility to ship full database backup from one SQL Server instance to another by schedule.
- More detailed log for Tasks and Steps. Now the log contains the source data.
- Improved support of SQL Server 2014.
- Trial period counter worked incorrectly in some cases. Fixed now.
- The decompression file errors for some configurations were fixed.
- At times the shrinking of log files of EMS SQL Backup failed. Fixed now.
- Lots of other improvements and bug-fixes.
New in EMS SQL Backup 1.4 (Dec 11, 2014)
- The product is renamed into EMS SQL Backup.
- License Manager is a very useful license key management.
- Server-side components updater: multiple update of server-side components.
- To start Administration Console you do not need Administrator privileges.
- Task scheduler errors are fixed.
- Dates localization errors are fixed.
- Memory leaks are fixed.
- Other small improvements and bug-fixes.
New in EMS SQL Backup 1.3.0.7027 (Nov 12, 2013)
- Support of remote storages to upload and store backups.
- Network folders, network-attached storages (NAS).
- Upload using FTP (ImplicitSSL / ExplicitSSL), SFTP (SSH) protocols.
- Support of cloud storage Amazon S3.
- Possibility to add unlimited number of remote and local storages for each backup.
- Support of 'Check orphaned users' option to restore backups.
- New macros for backup folders: {backup_root_folder}, {server}
- Log efficiency and representation are improved.
- Improved design.
New in EMS SQL Backup 1.2.0.6351 (Jun 14, 2013)
- Added the possibility to verify the integrity of the resulted files after the backup process (RESTORE VERIFYONLY & CHECKSUM).
- Displaying progress for long-running processes.
- Monitoring the log size increase (log size limit by date and size).
- Displaying the database size.
- Improved the main form design.
- Other improvements and bugfixes.
New in EMS SQL Backup 1.1.0.6205 (Apr 3, 2013)
- Added support of simultaneous backups on the same server.
- Added support of copy-only backups which do not affect the normal sequence of backups.
- Software update notifications.
- Improved the process of converting a policy to a template.
- Added new features for managing templates.
- Many interface improvements.
- Now server-side components have no memory leaks.
- More stable connections to the server-side and Console.
- The log management in the server side is improved.
- The server connection failure caused a configuration record error. Fixed now.
- Other improvements and bugfixes.