Dsmsched log not updating
This means that you can have two active copies of your backups in two different locations, giving you an instant ability to recover servers in a disaster.
You can also recover data from the replicated site to the live site.
Filespaces can be in 4 states as shown in the output above.
This will not accurately determine the health of backups and may not accurately detect the true status of backups, particularly in the case of computers that have not reproted in recently.
This analysis will need to be activated for those that wish to use it.
Node Replication TSM Command line Running processes in parallel Using the dsmcutil command The effect of ASNODE on restores Setting up an Enterprise Server Which IP ports does TSM use?
lla=1500 set replserver PROD_SERVER On the DR TSM server to the Production TSM Server define server DR_SERVER SERVERPA=password hla=22.214.171.124 lla=1500 set replserver DR_SERVER Create a TSM node group on both TSM servers and add some nodes to it define nodegroup repl_group desc="Node Group for Replication" define nodegroupmember repl_group node1 define nodegroupmember repl_group node2 define nodegroupmember repl_group node2 On the production TSM server, enable replication for each node: update node node1 replstate=enabled update node node2 replstate=enabled update node node3 replstate=enabled On the production TSM server, add an admin schedule to run the replication: define schedule replicate_nodes type=admin cmd="replicate node repl_group wait=yes" desc="3 Hourly Node Replication Schedule" dayofweek=any period=3 perunits=hours active=yes starttime= Now all 3 nodes will replicate their backup data to the DR server every three hours.
You can check the progress of replication with the Query Process command.