JuniorStorageGuy
Newcomer
Hi All
I'm busy testing a faster DR solution for our two TSM servers so that we can DR faster and carry on working while a fresh TSM Server is being rebuilt. Our environment and solution is as follows:
We have 2 TSM 7.1 servers (AIX) in seperate buildings running 2 seperate instances:
Building 1 = TSM Server1 = instance1
Building 2 = TSM Server2 = instance2
We would like have the opposing TSM Servers to act as the DR locations for their respective primary instances.
Building 1 = TSM Server1 = instance1(PRI) + instance2(DR)
Building 2 = TSM Server2 = instance2(PRI) + instance1(DR)
In a DR situation, we would like to fail over as soon as possible rather than wait for a TSM DB restore.
So we tried the following:
Is this even possible? If not, is there a similar solution that can be achieved?
Thank You
I'm busy testing a faster DR solution for our two TSM servers so that we can DR faster and carry on working while a fresh TSM Server is being rebuilt. Our environment and solution is as follows:
We have 2 TSM 7.1 servers (AIX) in seperate buildings running 2 seperate instances:
Building 1 = TSM Server1 = instance1
Building 2 = TSM Server2 = instance2
We would like have the opposing TSM Servers to act as the DR locations for their respective primary instances.
Building 1 = TSM Server1 = instance1(PRI) + instance2(DR)
Building 2 = TSM Server2 = instance2(PRI) + instance1(DR)
In a DR situation, we would like to fail over as soon as possible rather than wait for a TSM DB restore.
So we tried the following:
- Mirroring the TSM DB volumes, log volumes and instance home directories at SAN level.We kinda preplanned doing this and gave each of the file systems names that were unique.
- On a test environment we restored instance1 successfully.
- We created a new a TSM instance using the /opt/tivoli/tsm/server/bin/dsmicfgx wizard. This new instance was created to resemble instance2, i.e instance name, file systems, db locations, log locations, etc. The only difference was that it was started on a different port. This was successful so we halted this new instance after ensuring success.
- Broke the SAN mirror and zoned the mirrored disks to the test TSM environment. We then assigend the disks to the neessary file systems, retaining the data on them. I then edited the dsmserv.opt to use port 1502.
- Tried starting the TSM instance2 using the instance owner. Which failed with the follwing error: DBI1306N The instance profile is not defined.
Is this even possible? If not, is there a similar solution that can be achieved?
Thank You