SQL Backup - 7.0
Upgrading from SQL Backup 4, 5 or 6
Upgrading from SQL Backup version 5 or 6
If you are upgrading from SQL Backup version 5 or 6, you do not need to import SQL Servers that you previously registered. Your servers will be added automatically to the SQL Backup 7 Registered SQL Servers pane.
If you have not yet installed the SQL Backup 7 server components on a registered SQL Server, is displayed to the right of the SQL Server name in the Registered SQL Servers pane. You can click the icon to upgrade the components, as described in Installing or upgrading on a SQL Server instance.
If you have already upgraded the SQL Backup GUI, the same icon may be shown in various locations when you are working with a SQL Server instance that still has version 5 or 6 server components installed. This indicates that certain features are unavailable until you upgrade the server components to version 7.
Once you have upgraded, you must activate the SQL Server. If you have purchased a support contract, you can use the same license key as you used in version 5 or 6 (SQL Backup will remember this for you). Otherwise, you can use a trial version of SQL Backup 7 for 14 days, but then you must purchase a license.
The scripts and jobs you created using version 5 or 6 are supported in version 7, and will work in the same way.
Upgrading the activity cache
The activity cache speeds up the display of backup and restore history in SQL Backup by storing a copy of the backup and restore history for your registered SQL Servers.
The cache data is located on the same computer as the SQL Backup graphical user interface, in C:\Documents and Settings\<user name>\Local Settings\Application Data\Red Gate\SQL Backup\Server Data by default.
When you start the graphical user interface for the first time, you may be prompted to upgrade the activity cache. This will only happen if an activity cache from SQL Backup version 5 or 6 is found on your computer.
This may take several minutes, but happens only once.
Backup file format - SQL Backup version 5 only
Version 6 of SQL Backup introduced changes to the backup file format, and these have been maintained in version 7. When you upgrade the SQL Backup server components from version 5 to version 7, SQL Backup creates new backup files in the new format. The backup file extension is unchanged (.sqb).
- SQL Backup 7 is fully compatible with files created by earlier SQL Backup versions. You can work with any SQL Backup backup file version using SQL Backup 7.
- SQL Backup 5 (version 5.4 and earlier) cannot be used to restore a version 7 (or 6) backup file. To restore a version 7 (or 6) backup file to a server that has not been upgraded, you must first convert the backup file.
Upgrading from SQL Backup version 4
If you are upgrading SQL Backup from version 4, you can import all your registered SQL Servers into SQL Backup 7; you do not have to register them all again. For details, see Adding SQL Server instances.
When you register a SQL Server, if you have not yet installed the SQL Backup 7 server components on it, is displayed to the right of the SQL Server name in the Registered SQL Servers pane. You can click the icon to upgrade the components, as described in Installing or upgrading the server components using the GUI.
You must then activate the SQL Server. If you have purchased a support contract, you can use the same license key as you used in version 4 (SQL Backup will remember this for you). Otherwise, you can use a trial version of SQL Backup 7 for 14 days, but then you must purchase a license.
If you do not upgrade the server components, SQL Backup retrieves the details of activities and jobs on these SQL Servers when you first start SQL Backup. The information is displayed in the Time Line, the Activity History, and the Jobs tab. However, this information cannot be refreshed while SQL Backup is running.
Any options you set in version 4 are imported into version 7. However, note that backup alerts are no longer available; instead you can now use the Time Line or create a report of backup activity to see overdue backups. For more information about the options available, see File management options.
The scripts and jobs you created using version 4 are supported in version 7, and will work in the same way.
If you saved any backup settings in version 4, you can use them in version 7. However, in version 7 they are called templates.
Some features are restricted for activities and jobs from a previous version of SQL Backup. For example, you cannot display the properties of a backup performed by SQL Backup version 4.
Was this article helpful?
Thanks for your feedback!
- Backups stop working when the SQL account passwords are changed
- Backups and restores taking longer each time they run
- Improving performance by leveraging multi-processor hardware
- Checking the status of a backup or restore
- SQL Backup Agent doesn't start on named instance
- No backup files are erased when the verify option is also used
- Log shipping initialisation failing with error 3176
- Installing SQL Backup unattended
- Issues faced when upgrading an MSCS cluster server
- Cannot schedule log shipping on case-sensitive servers
- Activation fails because response does not match registration properties
- SQL error -1 on backup with 64-bit
- Could not find procedure 'master...sqbutility'
- 'Does not exist' error manually creating a generic service resource
- Backing up log shipping standby databases
- Stopping a backup or restore whilst in progress
- Backing up full-text catalogs using SQL Backup
- Cannot resolve collation conflict
- Microsoft cluster installation (version 4)
- Informing the SQL Agent of job failures
- Database log files may continue to grow even though transaction logs are backed up
- Cannot load xp_sqlbackup.dll
- Minimum Windows Rights Required for SQL Backup Agent
- Bringing a log shipping standby database online
- Console does not support editing the command you selected
- Malformed database disk image error
- Cannot use a local account to run SQL Backup Agent on cluster
- Preparing SQL Servers for remote installation
- SQL error 18210 and VDI error 1010
- Log shipping jobs not deleting old .sqb files
- Scheduled backups may not include new databases
- VDI error 1010 due to an abort request
- Cannot save or see backup templates
- Not all databases appear in the log shipping wizard
- No mapping between account names and security IDs was done
- SQL error 3101 (database is in use) during log shipping
- Insufficient quota to complete the requested service
- Configuring SQL Server procedure memory
- Backing up and restoring on SQL Server Express Edition
- Cannot run two database backups at the same time
- Restoring database backups across a local network
- In some situations the last compressed data block fails to be written to disk
- Configuring permissions for the SQL Backup Agent service
- Restoring backups from one server to a second server using the user interface
- Using SQL Backup tags to automate backup file naming
- VDI 1010 Error
- SQL Backup 5 cannot connect to servers running SQL Backup 4.0
- Files are created when NOWRITE or NOCOMPRESSWRITE is used in conjunction with multiple threads
- Cannot backup a database when full-text catalogs are not online
- Moving a full-text catalog on RESTORE
- Preventing backups over the network from timing out
- Deleting backup history manually
- SQL Backup installation from SQL Toolbelt installer only installs the console
- Console taking a long time to start up
- Reporting across multiple servers, login fails for user NT AUTHORITY\ANONYMOUS LOGON
- SQL Backup Agent cannot start due to account lookup error
- IO Error on backup or restore restart-checkpoint file
- Unable to edit SQL Backup Scheduled Jobs via the Jobs Tab in the SQL Backup GUI (version 5)
- VDI error 1000 caused by improperly installed VDI interface
- VDI Error 1000 caused by account lookup failure
- VDI error 1000 caused by insufficient permissions
- Error 193: %1 is not a valid Win32 application.
- Installing SQL Backup on a cluster
- Restoring the SQL Server MASTER database
- VDI Error 1010: Failed to get the configuration from the server because the timeout interval has elapsed
- Changing the default data location used by SQL Backup
- Index was outside the bounds of the array error during registration
- Repairing the SQL Backup server-side data store
- Troubleshooting slow backup and restore tasks
- Completed backup jobs showing "in progress" status (version 5)
- Restore wizard: files incorrectly labeled 'Missing' when browsing for a backup file to restore.
- When creating a backup job using the wizards some of the user databases may not be listed
- How to restore a filegroup
- System error 1453 while backing up (Insufficient quota to complete the requested service)
- SQL Backup VDI 1030: Failed to create VirtualServiceSet component
- Backups fail on named instances on custom ports
- SQL error 3101 (database is in use) during full database restore
- Error acquiring mutex occurring during use
- Transaction log continually growing on disaster recovery database
- Reseeding a disaster recovery database
- SMTP mail options not being saved
- SQL Backup Activation NullReferenceException Error
- Scheduling SQL Backup restore jobs
- SQL Backup Error 880: permission denied in database
- Deleting remote backup files after a specified time period (version 5)
- SQL Backup Unable to Login to Perform Backup or Restore
- Restore operation errors with exitcode 680
- "Failed to initialize local data store" error
- Trouble browsing network shares when backing up or restoring
- System error 32 (The process cannot access the file because it is being used by another process)
- Log backup failing because there is no current database backup
- Error locating server or instance of SQL Server
- How to set up log shipping between machines on different domains
- SQL Backup and CPU affinity
- SQL Backup mirrored backups
- Error trying to run backup job
- "Access to the database file is not allowed" error
- The server principal NT AUTHORITY\SYSTEM is not able to access the database
- Browsing while using SQL Server authentication is disabled on the selected server
- Cannot generate SSPI context message
- Log ship to multiple servers
- File browser does not work for remote servers
- Configuring Log Shipping to two Target Databases
- Previous backups not deleted according to ERASEFILES setting
- SQL Backup Reporting fails after upgrading to Version 6 from Version 5 for Multiple
- VDI error 1010 error on log backup when no backup is available
- SQL Backup failed with exit code: 1010 SQL error code: 3101 [SQLSTATE 42000] (Error 50000). The step failed.
- Log backup for a database failing to get copied to the log shipping share
- Mirrorfile backup jobs producing corrupt files
- Activity monitor showing sqlbackup status as wait type MSQL_XP
- Backup and restore processes using high percentage of CPU resources
- Warning 485: File does not exist encountered during a restore (but the process completes successfully)
- Log Shipping error 130 when moving restored file
- SQL Backup "Warning 110" generated
- Attempting to restore data into a SQL Express database that exceeds limit
- SQL error 3241 when restoring database
- A nonrecoverable I/O error encountered on Backup or restore operation
- SQL error 15404
- General log-in problem: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- Warning: System error 1450 when Backing up
- Problems with "Auto-Close" option set when backing up
- Warning: System error 64 (The specified network name is no longer available) on backing up across a network
- SQL error 4208 encountered on backing up
- Warning 170: "Log files are not in sequence" - on log shipping (restore) operation
- Warning: System error 121 (The semaphore timeout period has expired)
- Changing your participation in the quality improvement program
- Installing SQL Backup server components unattended
- Changing your participation in the quality improvement program
- Verifying backups of the master database
- Log files
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
- Getting help offline
- Using SQL Backup to back up to a network share
- Manually installing SQL Backup server components on clusters (Windows Server 2003)
- Manually installing SQL Backup server components on clusters (Windows Server 2008)
- Using SQL Backup log shipping to maintain a standby server
- SQL Backup release notes - version 6.xx
- SQL Backup release notes - version 7.xx
- Working with the new features in SQL Backup 6
- Using flexible licensing with SQL Backup Pro and SQL HyperBac
- Using SQL Backup Pro and SQL HyperBac together on the same server
all SQL products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs