Professional Documents
Culture Documents
Step1: have to configure TDPSQL on both nodes and on local disk only, not in
shared cluster disks.
[use of backup set : Set backups are intended to be used in unusual one-of-a-kind
situations.
Because set backups are always uniquely named (like log backups), they do not
participate in expiration due to version limit.
This means that whenever a set backup is performed, it does not inactivate any of
the previous backups.
The reason for using a set backup is if you do not want the backup to be part of
your normal expiration process. Thus, set backups are uniquely named.
The TSM automatic expiration that applies is the Retain Only Version parameter,
when the backup is inactivated. See “Active, inactive, expired” on]
In active/passive setup must enable cluster node yes. Node name should be same
in both nodes like musala_sql2_a on Node A & node B dsm.opt files.
TDP does not automatically register the SQL server name (Virtual Server name), so
this must be done manually.
To do this, open configuration under Edit in the GUI, and enter the name.
2) Active/Active
The Active/Active cluster is a little more complicated, since basically, it has two SQL
servers on the same MS cluster.Due to the fact that it has two different SQL servers,
we advise you to use two TSM node names; this implies two dsm.opt and two
tqpsql.cfg files. You can use the same node name (dsm.opt) and two different
tdpsql.cfg files, but this is not recommended.
Also, there must be installed two TSM Scheduler services bound to their
corresponding SQL server (Virtual Server Resource). Both services cannot have the
same name — thus, simply give each Scheduler service a number suffix.
Now start the TDP for SQL GUI using the shortcut. Then we configure the Virtual SQL
server name and Servername (cluster Server name) in the configuration window
Copy the files created to the other cluster node: Musula_sql_B
Now we copy the six files we have created to the other server in the cluster.
The configuration files must be in the file path where TDP for SQL is installed,
while the shortcuts can be placed wherever most convenient, for example, on
the Desktop.
The files to copy are:
• SQL_A_dsm.opt
• SQL_B_dsm.opt
• Musala_SQL_A tdpsql.exe.lnk
• Musala_SQL_B tdpsql.exe.lnk
• A_tdpsql.cfg
• B_tdpsql.cfg
Now TDP for SQL is ready to be used on the Active/Active cluster, assuming you
have already registered the TSM node names (Musal_SQL2_A and Musal_SQL_B) on
the TSM server.
As part of the Storage Agent installation, the TSM device driver is installed on
the client machine but it is not enabled or started. Enable the device driver by
issuing the following command in the Storage Agent directory:
tsmscsi /enable
The output from the command will inform that support is enabled:
On NT, the message will be something like this:
The TSM server needs to know how the client sees the tape devices on the
SAN. The information is used to configure drive mapping on the TSM server.
Issue the following command in the Storage Agent directory in order to obtain
the information:
tsmdlst (C:\Program files\tivoli\tsm\server\console)
The following device information was found on our specific installation:
TSM Windows 2000 / Optical support is enabled on RAINIER.
TSM Optical Support enabled on RAINIER.
The message tells you that optical support is enabled. However, that is a
misleading message. The Managed System for SAN feature does not
support optical devices on the SAN.
Note
Computer Name: RAINIER
TSM Device Driver: Running
TSM Device Name ID LUN Bus Port TSM Device Type Device Identifier
--------------------------------------------------------------------------------
mt0.2.0.2 0 2 0 2 3570 IBM 03570C125424
lb0.3.0.2 0 3 0 2 LIBRARY IBM 03570C125424
mt0.4.0.2 0 4 0 2 3570 IBM 03570C125424