Date: Fri, 29 Mar 2024 05:50:28 +0000 (GMT)
Message-ID: <92403550.567.1711691428334@ip-172-31-38-4.eu-west-1.compute.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_566_1400143680.1711691428326"
------=_Part_566_1400143680.1711691428326
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
This page applies to:
You can install SQL Backup on a Microsoft Cluster S=
ervice without using the clustering functionality of the SQL Backup install=
er. For example, you may want to do this if you have already experienced pr=
oblems using the installer on a cluster.
This page describes:
Licensing
You must have a SQL Backup Pro license for each ser=
ver on which you want to install the SQL Backup server components. This mea=
ns that each node (physical computer) must have its own license.
For example, a two node active-active cluster must =
have two licenses, and a two node active-passive cluster must also have two=
licenses.
Cleaning up an existing installat=
ion
If you have already attempted to install SQL Backup=
on the cluster but the installation did not complete successfully, you mus=
t 'clean up' the SQL Server instances.
To do this, perform the following steps on each of =
the SQL Server instances on which the installation failed:
- Uninstall the s=
erver components using the Add or Remo=
ve Programs dialog box.
You will be asked whether you want to remove the SQL Backup file containin=
g the history of the backup and restore activity. If you want to save or ar=
chive the data store, ensure you click No on thi=
s dialog box.
- Open the Regist=
ry Editor (regedit.exe) and navigate to the SQL Backup b=
ranch in the registry editor:
For all ve=
rsions of SQL Backup on 32-bit servers, and for SQL Backup 6.4 and later on=
64-bit servers, the branch is in HKEY=
_LOCAL_MACHINE\SOFTWARE\Red Gate
For SQL Backup 6.3 and earli=
er on 64-bit servers, the branch is in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Red Gate
- In the next ste=
p you will delete the contents of the =
SQL Backup branch, so if =
you want to copy your settings back later you should export the branch; sel=
ect the SQL Backup branch and on the File men=
u, click Export.
- Del=
ete the following subkeys from the SQL=
Backup branch:
BackupSettings\<instance name>
BackupSettingsGlobal\<instance name>
InstalledInstances\<instance name>
When you have performed these steps on the SQL Serv=
er instances as required, you can start the manual installation.
=
Installing manually
To install the SQL Backup server components, =
perform the following steps on each SQL Server instance in the cluster.
- To start the SQ=
L Backup (server components) Setup Wizard, run SQBServerSetup.exe on=
the cluster node.
- On =
step 2 of the wizard, the clustered SQL Server instances will be shown in t=
he list of available instances in the wizard. Select a clustered instance a=
nd click Next.
- On =
step 3, ensure you clear the option to Install SQL Backup on all cluster nodes.=
- On step 4, specify a domain account with=
sufficient privileges to run as a service, including the Log on as a service permission, for the SQL Backup Agent service to run as.=
span>
- On step 5, choose the authentication mode fo=
r the SQL Backup Agent service to connect to the SQL Server cluster. The ac=
count must be a member of the sysadmin fixed server role=
.
- On step 6, specify a location for the SQL Ba=
ckup data store which is a shared drive, accessible by all nodes in the clu=
ster. The location must be specified as a local path (for example, E:\SQLBackupData\(local)\), and not as a UNC path (for example, \=
\server\share\(local)\).
- On step 7, the location for the SQL Backup s=
erver component files must be a local drive.
For more information about using SQBServerSetup=
.exe see Installing the server components on a SQL Server cluster.
- Use=
the Services application to stop the SQL Backup=
Agent service if it is running. If you are stoppin=
g this service on a non-default instance, the service name will be in the f=
orm: SQL Backup Agent-<instance>=
.
- Open the =
Registry Editor (regedit.exe) and navigate to the SQL Backup&=
nbsp;branch in the registry editor:
For all versions of SQL Backup on 32-bit servers, and for SQL Backup 6.4 a=
nd later on 64-bit servers, the branch is in =
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate
For SQL Backup 6.3 and earlier=
on 64-bit servers, the branch is in HKEY_LOC=
AL_MACHINE\SOFTWARE\Wow6432Node\Red Gate
- Create or modify the following registry entries in the SQL Backup branch:<=
/span>
- In Bac=
kupSettingsGlobal\<instance>, create a string value called =
DataPath and set the value to a folder on the shared storage.=
- In &=
nbsp;InstalledInstances\<instance>, create a dword value called IsCluster and set the va=
lue to 1.
When you have completed these steps on all the SQL =
Server nodes in the cluster, create the clustered resource using the Failov=
er Cluster Management tool:
- In the left-hand pane, expand the cluster, then expand&=
nbsp;Services and Applications.
- Right-click on =
the SQL Server group, click Add a Resource, then click Generic Service.
The New Resource Wizard is displayed.
- Select SQL Backup Agent-<instance> from the list then click Next.
The list is not ordered alphabetically, so yo=
u may have to scroll through the entire list to find the SQL Backup Agent-<instance> resource.
=
Note: If the SQL Backup Agent service is already clustered=
, it will not be available in the list.
- Click Next on =
the Confirmation page of the wizard.
- Click Finish on the Summary page of the wiz=
ard.
The new resource has now =
been created (offline) and is listed under Other Resources.
- Under Other Resources s=
elect SQL Backup Agent-<instance>, then, on the=
Actions list click Properties for this resource.
The SQL Backup Agent-<instance> Properties dialog is displayed.
- On the General tab, ent=
er the Startup parameters as
-i <i=
nstance>
- On the Dependencies tab=
, we recommend that you add the SQL Server instance and the physical disk.<=
/li>
- On the Policies tab, se=
lect the If resource fails, attempt restart on current node option.
- On the Advanced Policies&nbs=
p;tab, ensure that all the nodes in the Possible Owners list are selected.
- On the Registry Replication&=
nbsp;page, add the following registry keys (do not include the HKE=
Y_LOCAL_MACHINE prefix):
For all v=
ersions of SQL Backup on 32-bit servers, and for SQL Backup 6.4 and later o=
n 64-bit servers:
SOFTWARE\Red&nb=
sp;Gate\SQL Backup\BackupSettings\<instance>
SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\<instance>=
For SQL Backup 6.=
3 and earlier on 64-bit servers:
SOFTWAR=
E\Wow6432Node\Red Gate\SQL Backup\BackupSettings\<instance>
<=
em class=3D"tcemphasis">SOFTWARE\Wow6432Node\=
Red Gate\SQL Backup\BackupSettingsGlobal\<instance>
- Bring the Clustered Resource online.=
You have now completed the manual installation.
Testing the installation
To ensure that SQL Backup is clustered correctly, y=
ou can perform the following test. This procedure includes at least one fai=
lover of the resource group.
- Open the SQL Ba=
ckup graphical user interface and use the Back Up wizard to perform a backu=
p, ensuring that you save the backup settings to a template by selecting th=
e Save as template check box on Step 6 of the wizard.
T=
he template will be included in the registry under BackupSettings\<instance>
In Microsoft=
SQL Server Management Studio, list the backup that you have just performed=
by typing the following query:
master..=
sqbdata 'SELECT * FROM backuphistory'
- Fail over to th=
e second node.
- Use the Back Up wizard to perform a second backup using the template you=
created.
If the registry keys have been correctly re=
plicated, the template will be displayed in the list of templates in Step 1=
of the wizard.
In SQL Server Management Studio, list the backups y=
ou have performed by typing the following query:
master..=
sqbdata 'SELECT * FROM backuphistory'
If the data stored has been cor=
rectly replicated, this will list both backups.
- If required, fa=
il over to the first node.
------=_Part_566_1400143680.1711691428326--