Scribd
Upload
180 views

Node Replication by Nodegroup

TSM 6.3 introduces node replication which allows replication of individual nodes or groups of nodes between two TSM servers using the "replicate node" command. It is recommended to use node groups for replication as it allows scheduling replication of multiple nodes together rather than individually. Setting up replication involves defining server-to-server communication between the production and DR TSM servers, creating a node group with members, enabling replication on the production nodes, and adding an admin schedule to run periodic replication of the node group.

Uploaded by

Kiran Kumar Peteru
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
180 views

Node Replication by Nodegroup

TSM 6.3 introduces node replication which allows replication of individual nodes or groups of nodes between two TSM servers using the "replicate node" command. It is recommended to use node groups for replication as it allows scheduling replication of multiple nodes together rather than individually. Setting up replication involves defining server-to-server communication between the production and DR TSM servers, creating a node group with members, enabling replication on the production nodes, and adding an admin schedule to run periodic replication of the node group.

Uploaded by

Kiran Kumar Peteru
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

TSM 6.3 Node Replication - Using nodegroups to make it easy.

talor | July 16 2012 | Visits (7433)

inShare
Tivoli Storage Manager from 6.3 onwards has had a feature called node replication. This brings up a new command
called replicate node. The only pre-requisite is that you have two TSM servers on version 6.3 or above, and serverto-server communications are configured.
The command replicate node, can replicate an individual node, or a group of nodes. I would strongly recommend
using node groups, because you can have a single group containing many nodes, then have a schedule to replicate
the group. Having a schedule for each node to be replicated, would be a headache. TSM nodegroups are typically
used for server backupsets, but using them for replication is really useful.
So, to get this going is VERY easy. Once the below steps are complete, and you have the data replicating, you can
point your backup/archive or TDP client at either TSM server and perform restores. If you have a standby site, it
would make DR tests a lot simpler doing this.
On the DR TSM Server, define the server to server communications to the production server:

define server TSMSERVER_PROD SERVERPA=passw0rd hla=192.168.0.100 lla=1500


ping server TSMSERVER_PROD
set replserver TSMSERVER_PROD
On the Production TSM Server, define the server to server communications to the DR server:

define server TSMSERVER_DR SERVERPA=passw0rd hla=192.168.100.100 lla=1500


ping server TSMSERVER_DR
set replserver TSMSERVER_DR
On both TSM servers, create the TSM node groups, and add the members:

define
define
define
define

nodegroup 2_hour_repl_nodes desc="TSM Node Replication nodegroup"


nodegroupmember 2_hour_repl_nodes nodeA
nodegroupmember 2_hour_repl_nodes nodeB
nodegroupmember 2_hour_repl_nodes nodeC

On the production TSM server, enable replication for each node:

update node nodeA replstate=enabled


update node nodeB replstate=enabled
update node nodeC replstate=enabled
On the production TSM server, add an admin schedule to run the replication:

define schedule replicate_nodes type=admin cmd="replicate node


2_hour_repl_nodes wait=yes" desc="2 Hourly Node Replication Schedule"
dayofweek=any period=2 perunits=hours active=yes starttime=00:00
Now we have nodes nodeA, nodeB and nodeC replicating their backup data every two hours to the DR TSM server.

You might also like