Hi,
First, since this thread is quite stale I wonder how your solution looks now.
I'm working on similiar architecture right now, it's still not ready, but here is what I've found regarding PT and TSM.
HADR seems to work fine... but:
- additionally you need to replicate a lot of encryption related files located in "instance" directory. Otherwise "resurected" instance will not be able to autheticate virtually anything.
- turn on LOGINDEXBUILD on db2's. Even with that enabled, it can take long time to faliover.
- PT replicates cartridges. No need to create any on DR side.
- Replicas can appear in your DR site in two ways: on the shelf, shared between all defined VTLs, or in io slots of selected VTL. It depends on "visibility" setting of replication policy.
- Visibility is important - With "on" it triggers replication once the cartridge is ejected on the source library. And it appears in io slot of the target library. It makes you life easier with testing. Or is ecellent if you want to have offsite copy pool. With "visibility" off, PT replicates your cartridges more or less instantly, but they are not available in DR site untill you put it in "DR mode". Then you can find them on the shelf.
And here goes my doubts:
- If primary site goes down, both TSM and PT, on DR site I have my tapes, but the library is completly different. I'm working on clean solution of redefinig the library under the storage pool, and checking in the tapes back.
- I want to make it as automatic as possible, because I have 64 drives available lanfree to 10 hosts... That makes 705 paths to update, including TSM :-\
I'd appreciate any sugestions how to design and automate such solution.