SQL Backup - 7.1
Installing on a SQL Server cluster
This topic explains how to install or upgrade the SQL Backup server components on SQL Server clusters.
You can install the SQL Backup server components on all SQL Server instances in a cluster at the same time. If you have a SQL Backup multi-server license, you can then activate SQL Backup on all of the nodes.
Note that if you are using SQL Backup with clustered SQL Servers, you are strongly recommended to save backup files on a shared drive within the cluster. This ensures that the backups are available in the event of failure of one of the clustered SQL Servers.
When you install the server components on a cluster, the SQL Backup Agent service application is clustered so that it can run backup and restore operations on whichever cluster node is active. In addition, the following registry keys in the SQL Backup branch are replicated:
- BackupSettingsGlobal\<instance name>
- BackupSettings\<instance name>
These registry keys contain details of saved SQL Server settings, templates, and other resources that are specific to SQL Backup. Note that SQL Backup scheduled backup jobs, scheduled restore jobs and log shipping jobs are replicated by the SQL Server instance.
It is also possible to install the server components on a SQL Server cluster unattended using the command line. For more information, see Installing SQL Backup server components unattended.
Before you install the SQL Backup server components for the first time, consider the following:
- On which clustered instance do you want to install the components?
- Do you want to use the Windows® authentication of the account, or a separate SQL Server authentication?
- The recommended method for installing the server components on a cluster involves running SQBServerSetup.exe from one of the clustered machines on which the components will be installed. When you install in this way, more information is provided if a problem occurs (particularly for post-installation checks).
Note that, from SQL Backup 6.3, it is no longer possible to use the SQL Backup GUI to remotely install server components to clustered servers.
For the installation, you will need to know:
- the account name and password of the administrator for all cluster nodes
- the account name and password that the SQL Backup Agent service application will run as; you are recommended to use a domain account rather than a local or built-in account
Upgrading from a previous release
If you are upgrading from a previous release of the SQL Backup server components to SQL Backup 7, prior to installation you must do the following:
- Ensure that no existing SQL Server Agent jobs involving SQL Backup tasks are running, and none will execute during the installation process.
- Ensure that no backup processes that use SQL Backup are running, and none will start during the installation process.
- Ensure that you have uninstalled SQL Backup version 4.x installed on any of the servers.
- In the 'Cluster Administrator' disable the SQL Backup Resource. This prevents the cluster from being failed over if there is a problem with the SQL Backup Agent during the upgrade process.
Installing using SQBServerSetup.exe
To install SQL Backup on a SQL Server cluster, copy SQBServerSetup.exe to the active node on the cluster, and run the program.
1. Welcome page
The following page is displayed:
You can cancel the installation at any time prior to the files being copied by clicking Cancel. The following dialog box will be displayed. Click Yes to cancel the installation; no files will be installed or upgraded.
2. Selecting instances
When you click Next on the Welcome page, a list of available instances is displayed. The list contains instances local to the computer from which you are running the setup program, and clustered instances for the SQL Server cluster that the computer is participating in.
The information in the lower pane indicates which architecture the SQL Server instance is using: 32-bit, 64-bit, or Itanium. For example, a SQL Server 2000 instance running on a 64-bit computer is listed as using 32-bit architecture because the SQL Server instance runs in 32-bit mode.
If you are upgrading the components to the same major version of SQL Backup (for example, from version 7.0 to 7.1), SQL Backup remembers the previous settings and takes you straight to the Ready to Install page of the wizard (step 7) when you click Next.
3. Cluster installation options
The Setup wizard detects that the SQL Server is part of a cluster, and provides the option to install SQL Backup on all the cluster nodes. If the check box is cleared, the server components are not installed as a clustered resource and you must configure the cluster manually (see Manually installing SQL Backup server components on clusters (Windows Server 2003) and Manually installing SQL Backup server components on clusters (Windows Server 2008)). You are recommended to select the check box and let the installer configure the server components as a clustered resource for you.
You must then enter the account name and password for a user that is an administrator on all nodes on the cluster (a 'cluster' administrator).
The Setup wizard also provides the option to automatically fail over to another cluster node if the SQL Backup Agent service cannot be started. You are recommended to clear this check box if you do not want all the resources in the group to failover. (Note that this option is not available if you are upgrading the server components.)
Cluster nodes lists all computers that are participating in the clustered SQL Server instance. In this example, there are two nodes: SQLCLUSTER1 and SQLCLUSTER2.
When you click Next, the account name and password are checked on all the cluster nodes. If any of the nodes cannot be correctly authenticated, an error message is displayed. In the example below, the authentication information was valid for SQLCLUSTER1 but not for SQLCLUSTER2.
4. SQL Backup Agent service application credentials
For any new installation, the installer requires information about which account the SQL Backup Agent service application will run as. The SQL Backup Agent performs SQL Backup backup and restore operations, maintains the SQL Backup activity history, and communicates information to the SQL Backup graphical user interface.
A Built-in account can be any account from those listed in the wizard. By default, this is Local System, but it can also be Local Service or Network Service.
For a clustered installation, you are recommended to use a domain account rather than a built-in account; select This account and enter the credentials. The Setup wizard checks that:
- The account name and password are correct.
- The account has sufficient permissions to run as a service, including the Log on as a service permission. If this permission has not been granted, the SQL Backup installer will attempt to grant the permission. For information on the permissions required for the SQL Backup Agent service, see Security Model.
If the credentials are not valid, an error message is displayed:
5. SQL Server authentication mode
For any new installation, the SQL Backup Agent service application needs to know whether to connect using the Windows authentication of the account it runs as, or to use a separate SQL Server authenticated account.
You can check the authentication details that you have entered by clicking Test. The Setup wizard tests that the account has sufficient SQL Server permissions (the SQL Backup Agent service application requires sysadmin privileges). If it has sufficient permissions, the following message is displayed.
If any other message is displayed, the credentials you have entered are incorrect, or the account does not have sysadmin privileges.
6. Data store location
SQL Backup stores data about backup and restore operations in a SQL Server Compact database. This information includes error and warning messages and various statistics such as compression details. SQL Backup also creates a log for each backup or restore process that it runs.
Specify locations on a shared disk that are accessible by all nodes in the cluster to store the database and logs.
7. Installation location
A summary is displayed, showing the location in which the server components will be installed. By default this is %ProgramFiles%\Red Gate\SQL Backup 7\<instance name> or %ProgramFiles (x86)%\Red Gate\SQL Backup 7\<instance name>.
Note: It is not possible to specify the location in which the server compnents are installed from the wizard. If you want to specify the location, run SQBServerSetup.exe from the command line and use the
/PATH parameter. For more information see Installing SQL Backup server components unattended.
This is the last point at which you can cancel the installation. When you click Install, the Setup wizard will install or upgrade the SQL Backup server components.
8. Installation progress
The progress of the installation is displayed.
The installer performs the following tasks:
- If the SQL Backup Agent service application is currently running, it is taken offline. Any backup or restore operations that are in progress are stopped.
- The server components are installed to the specified location on disk.
- Registry settings for the SQL Backup Agent service application are generated. These can be modified later using the SQL Backup graphical user interface.
- The SQL Backup Agent service application is created with the supplied credentials.
- For the cluster:
- The installer is copied to the same location on each of the computers in the cluster in turn. The SQL Backup server components are installed with the same settings as the current computer.
- The service is registered with the Cluster Administrator, and the registry keys are added to the clustered resource so that they will be copied between computers in the cluster and are always available to SQL Backup.
- Finally, the installer attempts to start the service.
If there are any problems during installation (such as the service failing to start), a warning message is displayed to inform you of the problem. For example:
9. Installation summary
When the installation has completed, the completion page is displayed.
The server components should now be correctly installed on the cluster.If any warnings were displayed during the installation (in stage 8), you can resolve them now by following the instructions in the message.
Once the upgrade process is successfully completed, re-enable the SQL Backup Resource in the SQL Server Service.
Activating on clusters
Once you have installed the server components, you will need to activate SQL Backup on the cluster. For general information about activating, see Activating SQL Backup. In addition, when you activate on clusters, note the following points.
To activate SQL Backup on a cluster:
- You must have a multi-server license key. You can review your serial numbers at http://www.red-gate.com/myserialnumbers
- You must use the Product Activation wizard. This is installed in your %Program Files%\Red Gate\SQL Backup 7 folder. Alternatively, you can start the program from the SQL Backup graphical user interface; on the Tools menu, select Utilities, then select Product Activation.
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