SQL Backup - 7.2
Overview - SQL Backup
SQL Backup comprises two main parts:
- The SQL Backup graphical user interface (GUI) for setting up and monitoring your backup and restore jobs.
The GUI is not licensed and can be installed on as many computers as you wish. You can install only one version of the SQL Backup GUI on each computer. To check which version of the graphical user interface is installed, from the Help menu select About SQL Backup.
- The SQL Backup server components installed on each SQL Server instance (or on each node of a clustered instance).
This is the licensed part of SQL Backup and contains the SQL Backup extended stored procedures and the SQL Backup Agent Service. You can install only one version of the SQL Backup server components on each SQL Server instance. To check which version of the server components is installed, in the SQL Backup GUI select the server, then from the Edit menu select Properties.
Note that the version numbers of the SQL Backup GUI and and server components may differ. The latest version numbers are posted on the SQL Backup forum.
Before you start installing or upgrading, check the Technical requirements to confirm that your systems are compatible with SQL Backup.
Whether you are installing SQL Backup for the first time, or upgrading an existing installation, the basic process is the same:
- Install or upgrade the SQL Backup graphical user interface (GUI).
For details, see Installing or upgrading the graphical user interface.
- Use the GUI to register the SQL Server instances on which you want to use SQL Backup.
For details, see Adding SQL Server instances.
- Install or upgrade the SQL Backup server components on the SQL Server instances as necessary.
You can use the graphical user interface to do this, or you can run the setup wizard manually. Both methods are described in Installing or upgrading on a SQL Server instance.
Note that if you are installing or upgrading the server components on a SQL Server cluster, you must run the setup wizard manually. For details see Installing on a SQL Server cluster.
When you have installed or upgraded the SQL Backup server components, if your license has not already been activated on the relevant servers, the instances are displayed in trial mode .
- Activate the licenses on the SQL Server instances as necessary.
For details, see Activating SQL Backup.
SQL Backup quality improvement program
SQL Backup can automatically send anonymous information about the features you use to Red Gate. This information helps Red Gate improve the reliability and performance of SQL Backup and decide which new features to add and bug fixes to prioritize.
When you run the SQL Backup graphical user interface for the first time, you are given the option to participate in the quality improvement program. If you choose not to participate, SQL Backup will not send any usage data back to Red Gate.
If you later change you mind about participating in the quality improvement program, you can change your participation status by following these instructions on the SQL Backup Support Center.
You can add any SQL Server instance to the SQL Backup GUI, but you must have a license for each server on which you want to use the backup and restore features.
Note that the trial version offers the same features as a licensed version of SQL Backup.
Details of how you add SQL Server instances to the SQL Backup GUI are provided in Adding SQL Server instances.
Details of how you activate SQL Backup on a SQL Server once you have purchased a license are provided in Activating SQL Backup.
Microsoft SQL Server support
SQL Backup supports 32-bit and 64-bit versions of Microsoft SQL Server 2012 and 32-bit, 64-bit, and Itanium versions of Microsoft SQL Server 2008, SQL Server 2005 and SQL Server 2000. The following editions are supported:
- Business Intelligence Edition (SQL Server 2012)
- Developer Edition
- Enterprise Edition
- Standard Edition
- Web Edition
- Workgroup Edition
SQL Backup provides limited support for SQL Server Express Edition; the SQL Backup graphical user interface does not support scheduled backup jobs, scheduled restore jobs or log shipping with this edition.
For SQL Server 2008, Service Pack 1 is supported (but not required). For SQL Server 2005, Service Packs 1, 2 and 3 are supported (but not required). For SQL Server 2000, Service Pack 3a or later is required.
The graphical user interface requires .NET version 2, 3.0 or 3.5.
Microsoft Windows support
SQL Backup supports the following Microsoft Windows operating systems:
- Windows 2000 Professional Service Pack 4
- Windows 2000 Server Service Pack 4
- Windows 2000 Advanced Server Service Pack 4
- Windows XP Professional Service Pack 1, 2 and 3
- Windows Server 2003 Standard Edition and Windows Server 2003 Enterprise Edition:
For 32-bit versions of Windows, Service Pack 1 and Service Pack 2 are supported but not required.
For 64-bit versions of Windows, Service Pack 1 is required. You must install this separately for Itanium; for x64 it is installed automatically. Service Pack 2 is supported but not required.
- Windows Server 2008 Service Pack 1 and 2 (Standard Edition and Windows Server 2008 Enterprise Edition)
- Windows Vista Service Pack 1 and 2
- Windows Server 2008
- Windows Server 2008 R2
- Windows 7
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