Question & Answer
When setting up the Tivoli Storage Manager Scheduler for Data Protection for SQL, how do I add Data Protection for SQL services to the Microsoft Failover Cluster?
Windows 2003 and Windows 2008 have different steps for adding cluster administration services
Add a Data Protection for SQL resource to the Microsoft Failover Cluster Management in Windows 2008, Windows 2008 R2, Windows 2012, Windows 2012 R2 cluster environments by completing the following tasks:
This example shows how to add the resource when setting up the Tivoli Storage Manager Scheduler for Data Protection for SQL.
I. Follow the steps in the section "Complete these tasks on the Tivoli Storage Manger server" in the "Using the Tivoli Storage Manger Scheduler" topic of the Data Protection for SQL Installation & User's Guide.
II. Ensure that the SQL Server has the following environment:
- The Tivoli Storage Manager Backup-Archive client is installed on the SQL Server in this directory:
- Data Protection for SQL is installed on the SQL Server in this directory:
- The communications option in the dsm.opt option files located in these directories point to the Tivoli Storage Manager server to which the SQL databases are to be backed up.
The options file that is defined for Data Protection for SQL is used by the scheduler when validating the node and password. The options file is also used when contacting the Tivoli Storage Manager for schedule information.
If this message displays:
A communications error occurred connecting to the Tivoli Storage Manger Server
then ensure that the following conditions are met:
- The communication options in the dsm.opt file points to the correct Tivoli Storage Manger server.
- The Tivoli Storage Manger server is running.
- The secondary node of the cluster must have ownership of the SQL virtual server.
- The primary node of the cluster must contain the command file on the file share used to create the scheduler service.
- The name of the service created by the dsmcutil inst command and the cluster service must have the same logon authority
Ensure that the following conditions are met:
V. Complete the following steps (1-4) on both nodes of the SQL Server:
1. Login using a Windows account that has administrative privileges.
2. Open a Windows command prompt window.
3. In the command prompt window, issue the following command:
cd /d d:\"Program Files"\Tivoli\TSM\baclient
You must place quotation marks around the section of a directory pathname that contains a space, for example:
You can also use the short form of a pathname by placing a tilde ("~") and unique identifier after the first six characters in the pathname. An example of the short form of the pathname is shown below:
Note: If a Tivoli Storage Manger scheduler is already installed on your computer (for the regular backups of the Windows system), you must install another scheduler (with a unique name) to run the schedules defined for Data Protection for SQL. The Tivoli Storage Manger scheduler must have a different node name from the regular Tivoli Storage Manger backup-archive client.
4. In the command prompt window, issue the following command:
dsmcutil inst /name:"Data Protection for SQL Scheduler" /node:mynode /password:mypassword /autostart:no clusternode:yes /clustername:myclustername /clientdir:"d:\"Program Files"\Tivoli\TSM\baclient" /optfile:"d:\Program Files\Tivoli\TSM\TDPSql\dsm.opt" /startnow:no
The Windows ID that is used to start the scheduler service may require that you specify the client dsmcutil options ntdomain, ntaccount, and ntpassword in this command.
Note: To make corrections after installing a service, follow these steps:
a. Remove the service by issuing the dsmcutil remove command, for example:
dsmcutil remove /name:"Data Protection for SQL Scheduler"
b. Make any corrections.
c. Install the service again with the dsmcutil inst command.
After you have completed these steps (1-4) on both nodes, the Data Protection for SQL scheduler service is ready to be tied to a cluster group.
The Tivoli Storage Manager scheduler is now installed but not started.
Complete the following tasks on the Microsoft Failover Cluster Management console that is included with Windows 2008:
1. Start the Failover Cluster Management Console:
Click Start–>Adminstrative Tools–>Failover Cluster Management
2. Create a new resource to represent the Data Protection for SQL scheduler by following these steps:
a. Expand your cluster in the tree view pane, then expand the Services and Applications node.
b. Right-click your SQL Server Cluster Group and select Add a resource->Generic Service. The New Resource Wizard window opens.
c. Select the Data Protection for SQL service from the list of services, and click Next.
d. A Confirmation window opens. Click Next.
e. A Summary window opens, which states whether the resource was created successfully. Click Finish.
3. Modify the new resource by following these steps:
a. In the Actions pane, expand Other Resources, right-click the Data Protection for SQL Scheduler resource, and select Properties.
b. Click the Registry Replication tab, then click Add. The Registry Key window opens. Type the exact text for the key where the Data Protection for SQL node name is listed, then click OK.
This is the format of text for the key:
Replace <nodename> with your Data Protection for SQL node name, for example:
c. In the Data Protection for SQL Properties window, click OK .
4. Open a Windows command prompt window. From the command prompt window, issue the following command to change to the Data Protection for SQL installation directory:
cd /d d:\Program Files\Tivoli\TSM\TDPSql
5. Verify that the clusternode option in the dsm.opt file is set to yes, then issue the following command:
tdpsqlc query tsm /tsmpassword=mypasword
This ensures that the correct password is stored in the registry, and allows the scheduler to properly connect automatically to the Tivoli Storage Manager server.
6 . In the Actions pane, expand Other Resources, right-click the Data Protection for SQL Scheduler resource, and select Bring this resource online.
VII. After the new resource is online, move the Group from the secondary node to the primary node cluster. Verify that the Data Protection for SQL scheduler service on the primary node has started.
VIII. Your system is now ready to run the scheduled full Legacy backups of the SQL databases.
17 June 2018