TSM 6.3 Node Replication - Using nodegroups to make it easy.
talor 27000411MV Visits (5411)
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 server-to-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
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
On both TSM servers, create the TSM node groups, and add the members:
define nodegroup 2_hour_repl_nodes desc="TSM Node Replication nodegroup"
On the production TSM server, enable replication for each node:
update node nodeA repl
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.