Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+DR\s+restore\s+of\s+Client\s+Data\s+to\s+new\s+hardware\s+w\/\s+new\s+IP\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+DR\s+restore\s+of\s+Client\s+Data\s+to\s+new\s+hardware\s+w\/\s+new\s+IP\s*$/: 2 ]

Total 2 documents matching your query.

1. [ADSM-L] DR restore of Client Data to new hardware w/ new IP (score: 1): Author: Eric Vaughn <evaughn AT STEVENSON DOT EDU>; Date: Wed, 23 Sep 2009 14:01:20 -0400; 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 n; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-09/msg00261.html (11,215 bytes)
2. Re: [ADSM-L] DR restore of Client Data to new hardware w/ new IP (score: 1): Author: Kelly Lipp <lipp AT STORSERVER DOT COM>; Date: Wed, 23 Sep 2009 13:18:55 -0600; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-09/msg00264.html (12,353 bytes)

Current List: 1 - 2
Page: [1]