Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Question\s+from\s+a\s+non\-TSM\s+person\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Question\s+from\s+a\s+non\-TSM\s+person\s*$/: 7 ]

Total 7 documents matching your query.

1. Question from a non-TSM person (score: 1): Author: fred johanson <fred AT UCHICAGO DOT EDU>; Date: Thu, 10 Feb 2005 16:23:56 -0600; I was asked if it was possible to move TSM from machine to machine by mirroring the DB and log, breaking the mirror, moving the mirrored portions to a new machine, adding the old mirror volumes to ds; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00218.html (11,154 bytes)
2. Re: Question from a non-TSM person (score: 1): Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>; Date: Fri, 11 Feb 2005 09:28:02 +0100; Hi Fred! It probably is. Breaking the mirror is an immediate action which is database-wise somewhat comparable with a kill -9 of the TSM server. I have had to do this in the past and TSM came up fine; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00222.html (13,030 bytes)
3. Re: Question from a non-TSM person (score: 1): Author: Svetoslav Tolev <Bugs AT BULMAG DOT BG>; Date: Fri, 11 Feb 2005 11:06:37 +0200; Hi, Be carefull with path. Because one of the machines can have numeration of drives different than the new one... Than you need to update the paths with correct values. Also - If you for "mirroring"; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00224.html (13,818 bytes)
4. Re: Question from a non-TSM person (score: 1): Author: Jim Armstrong <jim_armstrong AT STANDARDLIFE DOT COM>; Date: Fri, 11 Feb 2005 10:34:51 +0000; Fred, You could have a problem if your database and recovery logs are on more than one physical disk, because when you break the disk mirrors you could not guarantee that the data on all the mirrored; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00226.html (13,461 bytes)
5. Re: Question from a non-TSM person (score: 1): Author: "Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>; Date: Mon, 14 Feb 2005 09:58:32 -0600; We've used a similar procedure in the past for quicker upgrades and a quick backout. We would mirror the TSM Logs and DB on separate physical disk drives. These disk drives were internal to our serve; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00285.html (11,874 bytes)
6. Re: Question from a non-TSM person (score: 1): Author: Paul Fielding <paul AT FIELDING DOT CA>; Date: Mon, 14 Feb 2005 09:06:55 -0700; I agree, this should work fine. I think the thing that previous posters were commenting on (saying that the db would become corrupted), that wasn't made clear in the original question, is that you wa; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00289.html (12,996 bytes)
7. Re: Question from a non-TSM person (score: 1): Author: fred johanson <fred AT UCHICAGO DOT EDU>; Date: Fri, 18 Feb 2005 09:52:27 -0600; This worked just fine. I had done something similar on a small box (a C10?) on ADSM 2.1. We weren't sure if it would be any different dealing with LUNs in a SAN with a 200 Gb DB than it was with unpl; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-02/msg00493.html (13,546 bytes)

Current List: 1 - 7
Page: [1]