Results 1 to 4 of 4
01-11-2010, 09:58 AM #1
TSM recovery with multiple Instances
Ideas needed for DR testing.
We do not have an offsite facility or a proper test server, but the powers that be want to know what it will take to recover our TSM server.
Here is the dilemma I ran into already, we are running on AIX, TSM5.5 with 5 instances.
I got another AIX LPAR with a different IP address, loaded the OS of my existing TSM server and zoned the existing tape library to the test lpar.
I had to do a crossdefine to the Production Library Manager so I could use the Tape Drives.
I did a database restore for the first instance on the test lpar which was successful, but when I shut it down it also shutdown the Production Instance. I'm thinking the crossdefine did me in, but it's the only way to get to the drives.
Can you rename the instances in the devconfig and dsmserv files before you do the restore? Or will I need to have the Production instances down while I recover on the Test lpar, then rename them and then bring the Production instances back online? - that will be a big pain.jan
01-11-2010, 10:16 AM #2
- Join Date
- Aug 2005
- Somewhere in the US
- Thanked 236 Times in 231 Posts
Unfortunately, you cannot rename any TSM server as the database restore will be looking for the right TSM server name.
This is why in a DR test, you need to restore on an isolated environment; or if this isn't possible, shutdown the Production TSM server/server instance.
Last edited by moon-buddy; 01-11-2010 at 01:24 PM.Ed
01-11-2010, 11:25 AM #3
Ya, that's what I thought
Which is what I told the PTBjan
01-11-2010, 12:55 PM #4
- Join Date
- Feb 2003
- Charlotte, NC
- Thanked 1 Time in 1 Post
Be careful on restored instance if you're using the production library & media! If you have an instance running as a library manager, and you bring up a restored library client, it may be out of sync with current library inventory. You could have the restored instance scratch a tape it thinks is still pending scratch, only to find out that tape has been reused by the instance between DR's db backup and present. You can end up overwriting good data when tapes in Pending state on the DR instance are released as scratch when it starts up. The library manager instance will be more than happy to return the volumes to scratch even though they have been reused after they went scratch in production.
Last edited by Eldoraan; 01-11-2010 at 01:04 PM. Reason: clarification and spellingMichael
TSM Admin since ADSM v2... wow, I'm not even that old yet either!
By 247PSH in forum TSM Installation, Upgrade and ConfigurationReplies: 2Last Post: 07-23-2009, 08:57 AM
By russdavid in forum Performance TuningReplies: 2Last Post: 02-26-2009, 11:49 PM
By khawts in forum TSM ClientReplies: 1Last Post: 03-20-2007, 06:18 PM
By cisse in forum TSM ServerReplies: 1Last Post: 04-03-2006, 12:13 PM
By shcart in forum TSM ServerReplies: 1Last Post: 10-13-2004, 02:50 PM