Release notes - version 7.xx

SQL Backup 7.2 is a minor release and includes the following enhancements and bug fixes:

Enhancements

Default names for scheduled backup jobs now include information about the databases in the job.
Log Shipping wizard steps re-ordered and validation introduced to prevent network share and MOVETO folder being the same.
It is now possible to double-click anywhere on a reminder to launch the Schedule Restore Jobs wizard.
On step 2 of the Schedule Restore Jobs wizard, 'Create new database' is always selected and populated by default.

Bug fixes

SB-4546, SB-4689 and SB-5289 - STOPATMARK and STOPBEFOREMARK are supported when restoring using LATEST_ALL.
SB-4767 and SB-5056 - Changes to default names for scheduled backup jobs (see New Features above).
SB-5024, SB-5113 and SB-5287 - Issues with keyboard shortcuts and navigation in the Restore, Schedule Backup Jobs and Schedule Restore Jobs wizards have been resolved.
SB-5190 - Reminders are not displayed if SQL Backup cannot connect to the SQL Server.
SB-5196 - Backup jobs that use the FULLIFREQUIRED keyword are now removed from the In Progress tab once the backup has completed.
SB-5202 - When upgrading from one major version to another (for example, from SQL Backup 6 to 7), SQL Backup is installed in a folder labelled with the new major version number by default. The folder containing the previous version is removed.
SB-5245 - In the Restore wizard, the option to check for orphaned users is selected by default when the user changes from a filegroup backup to a full backup.
SB-5270 - An error is raised when invalid database file paths or file names are entered on step 2 of the Restore wizard.
SB-5286 - When the Restore or Log Shipping wizard is launched from the context menu, the 'Database' control is populated with the selected database.

SQL Backup 7.1 is a minor release and includes the following enhancements and bug fixes:

Enhancements

The Jobs tab contains an additional 'Database' column to show which databases are included in each job. For multiple databases in a job, click the information icon.
The height of rows in the Activity History has been reduced.
In differential or transaction log backup jobs for multiple databases, you can specify WITH FULLIFREQUIRED to take a full backup of any databases which require one before a differential or transaction log backup can be taken. This option is not available from the backup wizards. See The BACKUP Command for more information.

Bug fixes

SB-4579 and SB-4714 - Enhancement requests relating to WITH FULLIFREQUIRED. See above.
SB-4717 - Consistent warnings and errors are returned in all cases where a backup file name is generated from the or tags and the database name includes an invalid character.
SB-4968 and SB-5183 - The character limit for extended stored procedure commands has been increased to 1048378 characters.
SB-5122 - When creation of a scheduled backup job fails, the Jobs tab is opened.
SB-5169 - File and folder browsers include SQL authentication warning message.
SB-5173 and SB-5184 - Error 821 is returned when DBCC CHECKDB fails after restoring log backups.
SB-5191 - RESTORE SQBHEADERONLY can be performed while the backup file is in use.
SB-5193 - When creating differential backups of all or system databases, SQL Backup no longer reports that a differential backup of the master database has been created.
SB-5214 - Error 515 is returned if the tag does not include or when backing up multiple databases.
SB-5224 - Error 480 displays the invalid path entered by the user when the tag is used.
SB-5225 - Using the .NET 4 client profile no longer causes a crash.
SB-5248 - Email notifications now support encrypted SMTP passwords.
SB-5181 When creating a scheduled backup job using the 'Exclude these' option to select databases, reminders are created for the databases currently included in the job.

SQL Backup 7.0 is a major upgrade from SQL Backup 6.5 and includes the following new features:

Schedule a recurring restore from a full backup or set of backups that does not exist yet by specifying a folder and file name pattern to identify the latest backup each time the job runs.
Schedule a recurring restore from specific backup files which form a full backup or set of backups.
Run a database integrity check as part of a scheduled restore job.
Drop a database after a scheduled restore job has completed, or only if the restore and integrity check (if applicable) were successful.
Take a copy-only backup using the Back Up or Schedule Backup Jobs wizards.
Include CHECKSUM in the backup process using the Back Up or Schedule Backup Jobs wizards.
Create a reminder to set up backup verification using the Schedule Backup Jobs wizard.
Launch the Schedule Restore Jobs wizard from the Reminders tab, populated with details from the scheduled backup job, to set up backup verification.
View results of CHECKSUM and DBCC CHECKDB in the Activity History.
Various bug fixes.

Was this article helpful?

Search support