TSM DB2 : HADR

[xaminmo]

Because TSMBB is a DB2 cluster node.  DB2 knows nothing of volhist.out.  
Volhist will only be saved out where TSM is actively running, not on 
standby/backup nodes.

I'd recommend setting up shared or replicated disk where your volhist and 
devconfig, and maybe a copy of your DR plans can be saved to, though the DR 
Plan should still be sent somewhere offsite as well.

+--
|This was sent by xami...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

TSM DB2 : HADR

[Gibin]

I was able to setup HADR between two TSM servers .TSM server AA ( win 2003 ,tsm 
v6.2.2,PRIMARY) and TSM server BB (win 2008,tsm v6.2.2,STANDBY).


There are running in nearsync mode and  everything seems fine. But i am  still 
confused about the TSM volhist.dat  file .


On checking the volhist.dat file on server AA ,it is the most updated and has 
all the entries of DB backups etc.But the TSM server BB volhist file is not 
updated as in server AA. :?

As per the HADR setup proces , i took offline backup of server AA and then 
restored it on server BB using the restore command with the REPLACE history 
file option . I then started server BB as standby and server AA as primary with 
nearsync mode .


While checking the volhist file entries and file modified time on both servers, 
they are different.


Not sure why the volhist.dat is not updated on both the primary and standby 
servers.

+--
|This was sent by gibi...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--