SQL Backup
Latest version: 7.2
Knowledge base
Installing SQL Backup server components unattended
Category: Installing and upgrading
Date: 22 May 2012
Product: SQL Backup
Versions: 5.2 and later
To install the SQL Backup server components, run SQBServerSetup.exe. This file is copied to the SQL Backup program folder (%Program Files%\Red Gate\SQL Backup <version number> for 32-bit servers, %Program Files (x86)%\Red Gate\SQL Backup <version number> for 64-bit servers) when the SQL Backup user interface is installed.
To install the server components unattended, call SQBServerSetup.exe from the command line with /VERYSILENT and /SUPPRESSMSGBOXES. For example:
SQBServerSetup.exe /VERYSILENT /SUPPRESSMSGBOXES
The server components will be installed on the local instance using the default settings unless you specify otherwise using the parameters described below.
SQL Backup server components installation parameters
|
Performs an installation without launching the SQL Backup (server components) Setup wizard. All the values that would normally be entered in the wizard must be defined at the command line, otherwise the default values will be used. Use in combination with |
|
Suppresses any warning or information boxes that would appear. No information will be returned if an error arises. Use in combination with |
|
Specifies the instance to install on. If this parameter is not specified, the default instance is used. Do not specify more than one instance. |
|
Installs the server components in the specified directory. When installing on a cluster, the directory can be a shared drive. If this parameter is not specified, the server components are installed in the default location (%Program Files%\Red Gate\SQL Backup <version number>\<instance name> on 32-bit machines and %Program Files (x86)%\Red Gate\SQL Backup <version number>\<instance name> on 64-bit machines). |
|
Specifies the user account used to log on to the SQL Backup Agent service (the startup account). Use either clear-text or an encrypted format. If this parameter is not specified, the account the SQL Server instance is currently running as is used. For details of the permissions required by the startup account, see Security Model. |
|
Specifies the password for the user account used to log on to the SQL Backup Agent service (the startup account). Use either clear-text or an encrypted format. Must be used with |
|
Specifies that the SQL Backup Agent service should connect to the SQL Server using the specified SQL Server authenticated account. Use either clear-text or an encrypted format. If this parameter is not specified, Windows authentication is used. For details of the permissions required by the SQL Server authenticated account, see Security Model. |
|
Specifies the password for the specified SQL Server authenticated account. Use either clear-text or an encrypted format. Must be used with |
|
Specifies the location in which the SQL Server Compact database is created. The SQL Server Compact database stores SQL Backup backup and restore information. If this parameter is not specified, the Compact database is created in the default location: %ProgramData%\Red Gate\SQL Backup\Data (Windows Vista, Windows 2008 and later) or %ALLUSERSPROFILE%\Application Data\Red Gate\SQL Backup\Data (Windows XP and Windows 2003). |
|
Specifies the location in which the SQL Backup logs are stored. SQL Backup creates a log for each backup or restore process it runs. If this parameter is not specified, the logs are stored in the default location: %ProgramData%\Red Gate\SQL Backup\Log (Windows Vista, Windows 2008 and later) or %ALLUSERSPROFILE%\Application Data\Red Gate\SQL Backup\Log (Windows XP and Windows 2003). |
|
Installs SQL Backup server components as a clustered service. SQL Server must be installed as a clustered resource on the host machine. |
|
Specifies the user name of the user that the installer will run as for clustering registration. Use either clear-text or an encrypted format. Use in combination with |
|
Specifies the password of the user that the installer will run as for clustering registration. Use either clear-text or an encrypted format. Must be used with |
|
Specifies a cluster-based install on a secondary node (rather than the primary node). The server components will not be installed on other nodes in the cluster. |
|
Writes information from the installation to a log file, which can be found in %TEMP% as "Setup Log yyyy-mm-dd #nnn.txt" |
|
Logs the outcome of the installation to the specified text file using the exit codes listed below. |
Example 1
The following command installs SQL Backup server components in the default location on the local instance, specifies the account the SQL Backup Agent service should run as, and specifies that it should use SQL Server authentication to connect to the local instance (the specified accounts should have sysadmin privileges):
SQBServerSetup.exe /VERYSILENT /SUPPRESSMSGBOXES /SVCUSER "user name" /SVCPW "password" /SQLUSER "user name" /SQLPW "password"
Note that the /SQLUSER and /SQLPW parameters are only necessary if you want the SQL Backup Agent service to connect to the SQL Server instance using SQL authentication rather than Windows authentication.
Example 2
The following command installs SQL Backup server components on the SQL2008 server in D:\SQLBackup\ServerComponents, specifies the locations of the data and log stores (D:\SQLBackup\ServerComponents\SQBData and D:\SQLBackup\ServerComponents\SQBLog respectively), and specifies the account the SQL Backup Agent service should run as:
SQBServerSetup.exe /verysilent /SUPPRESSMSGBOXES /i (SQL2008) /Path D:\SQLBackup\ServerComponents /DATAPATH D:\SQLBackup\ServerComponents\SQBData /LOGPATH D:\SQLBackup\ServerComponents\SQBLog /svcuser "SQLBACKUPsERVICEUSER" /svcpw "password"
The SQL Backup Agent Service will connect to the SQL Server using the Windows authentication of the startup account, because SQL Server authentication has not been specified.
SQL Backup Exit Codes
Exit Code |
Definition |
0 |
Installation was successful |
Pre-installation Failures |
|
5 |
Another installation is in progress. Try again later. |
6000 |
Current user has insufficient permissions to modify Windows Services. |
6010 |
Windows 2003 Itanium edition requires SP1 to be installed before installing SQL Backup server components. |
6020 |
The user account specified for the SQL Backup Agent service to log on as could not be verified. |
6030 |
The user account specified for the SQL Backup Agent service to log on as was ambiguous. Ensure the account details are fully qualified. |
6040 |
The password for the SQL Backup Agent service user account was invalid. |
6100 |
The user account specified for the SQL Backup Agent service to log on as does not have permission to log on as a service. |
6110 |
Unable to grant 'log on as a service' rights. |
6200 |
SQL authenticated user name or password is invalid. |
6210 |
SQL authenticated account is not a member of the sysadmin role. |
Post-installation failures |
|
8192 |
SQL Backup Agent service executable (SQBCoreService.exe) is not installed. |
16384 |
The version of the SQL Backup Agent service is incorrect. |
32768 |
The SQL Backup Agent service could not be registered correctly. |
65536 |
The SQL Backup Agent service was unable to start within 1 minute. |
131072 |
The SQL Backup extended stored procedure dynamic-link library (xp_sqlbackup.dll) was not installed correctly. |
262144 |
The version of the SQL Backup extended stored procedure dynamic-link library (xp_sqlbackup.dll) is incorrect. |
524288 |
Unable to confirm that the SQL Backup extended stored procedure dynamic-link library (xp_sqlbackup.dll) was registered correctly (connection error). |
1048576 |
Some SQL Backup extended stored procedures were not registered correctly. |
2097152 |
The installer could not set the SQL Backup Agent service's instance (-I) flag. |
The exit codes can be combined to form a bitmask. For example, a value of 278528 would mean that the versions of the SQL Backup Agent service and the SQL Backup extended stored procedure dynamic-link library are incorrect.
You may find this Simple Talk article about installing SQL Backup on multiple servers using SQL Multiscript useful.
Was this article helpful?
SQL Backup
- 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
all products
- 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
SQL Backup
- 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
all 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

Installing or upgrading SQL Backup