Eric, Should have been update stg access=destroyed rather than unavailable. That's one thing.
Why isn't the client seeing the TSM server at the new IP? Hmmmm. The client is pointing at the new source server, not the target, correct? The new source/target combo may require updating as well since the target new the source at a different address. So the whole HLLL address thing needs to be fixed up on the new source and target. Are sessions enabled on the new source? Can the TSM client on the source talk to the source TSM server? These are all troubleshooting things I would try. Kelly Lipp Chief Technical Officer www.storserver.com 719-266-8777 x7105 STORServer solves your data backup challenges. Once and for all. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Eric Vaughn Sent: Wednesday, September 23, 2009 12:01 PM To: [email protected] Subject: [ADSM-L] DR restore of Client Data to new hardware w/ new IP Hello, Our environment consist of source to target. I have recreated and restored the db onto a new piece of hardware that would be used as the replacement source server. My issue is that the IP is new and not the address that was assigned to the original source server. My assumption lead me to change the opt file on a client to the new server address. I restarted the services and tried to open up the gui and received a TCP/IP communication failure. Can anyone tell me what I am missing? I would like to restore from the copy pool. I issued the command update stgpool secondarypool access=unav so the client would retrieve data from the archivepool but no luck. Eric Vaughn Technical Administrator Stevenson University Office (443)334-2301 [email protected]
