Sorry but I cannot share the script as this is part of company rules.
However, I can guide you on how to put one together.
1. Setup the DD device to replicate to the DD on the DR site
2. Setup the TSM on the primary side to backup the DB to the DD device (through NFS) plus the RP, volhist and devconfig files.
1. Setup the DD device to receive replication from the primary site
2. Setup a TSM instance that has the same configuration as the original TSM instance
3. Create a script that:
- will create snapshots of the primary DD into the DR DD
- mount (NFS) the snapshots into the DR TSM server - the snapshots are normally created by the DD device with dates in it
- the date-defined snapshots will be a placeholder to easily determine which DBB volumes are needed for recovery
4. append to the script TSM restore functions:
- extract the necessary data from the RP File, etc
- restore the TSM instance via dsmserv restore ... (since the DB, logs, configuration, etc. can be seen by the DR instance via the snapshot mounts)
After this works, you can put this into CRON and you have an automated recovery mechanism.
Wanted to ask you, how would you test to make sure the DR TSM server works with DR DataDomain, while your Prod TSM server is up. If you do a DSMSERV restore, DR will get the Prod Name and in DNS will have same name but 2 ips ( Prod and DR).