Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Follow\-up\:\s+Question\s+about\s+\"Hybrid\"\s+method\s+upgrade\s+to\s+TSM\s+V6\.2\.2\s+and\s+server\-to\-server\s+export\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Follow\-up\:\s+Question\s+about\s+\"Hybrid\"\s+method\s+upgrade\s+to\s+TSM\s+V6\.2\.2\s+and\s+server\-to\-server\s+export\s*$/: 2 ]

Total 2 documents matching your query.

1. [ADSM-L] Follow-up: Question about "Hybrid" method upgrade to TSM V6.2.2 and server-to-server export (score: 1): Author: "Prather, Wanda" <wPrather AT ICFI DOT COM>; Date: Tue, 13 Sep 2011 19:34:02 +0000; Posting a follow-up to this thread. Been there, done that, didn't like it when I tried it. Customer had a TSM 5.5 server with ~100G data base. Moving to 6.2.2 on new hardware. Testing showed that the; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-09/msg00082.html (14,778 bytes)
2. Re: [ADSM-L] Follow-up: Question about "Hybrid" method upgrade to TSM V6.2.2 and server-to-server export (score: 1): Author: Xav Paice <xpaice AT OSS.CO DOT NZ>; Date: Wed, 14 Sep 2011 08:54:15 +1200; We hit the exact same issue in test - so we took a rather butcher-ish approach: - When starting up the 'old' server following the extract, we defined a new, temporary stgpool and directed all new dat; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-09/msg00083.html (17,553 bytes)

Current List: 1 - 2
Page: [1]