Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TSM\s+client\s+uppgrade\s+5\.1\.7\.3\s+to\s+5\.2\.3\.11\s*$/: 4 ]

Total 4 documents matching your query.

1. TSM client uppgrade 5.1.7.3 to 5.2.3.11 (score: 1)
Author: Henrik Wahlstedt <shwl AT STATOIL DOT COM>
Date: Mon, 24 Jan 2005 14:43:08 +0100
Hi, If I upgrade TSM client on a w2k3 server, 5.1.7.3 to 5.2.3.11. Then I have SYSTEM OBJECT´s in 'q fi'. Compared to a clean install of 5.2.3.11. Why does SYSTEM OBJECT remain? I think SYSTEM OBJECT
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-01/msg00653.html (12,249 bytes)

2. Re: TSM client uppgrade 5.1.7.3 to 5.2.3.11 (score: 1)
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Mon, 24 Jan 2005 07:21:32 -0700
The 5.2 (and higher) client uses Microsoft's Volume Snapshot Services (VSS) for backing up Windows 2003 system state and system services, whereas the 5.1 client uses the Microsoft "legacy" API functi
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-01/msg00655.html (13,866 bytes)

3. Re: TSM client uppgrade 5.1.7.3 to 5.2.3.11 (score: 1)
Author: Henrik Wahlstedt <shwl AT STATOIL DOT COM>
Date: Tue, 25 Jan 2005 11:14:29 +0100
Ok and thanks for your answer Andy. It makes me curious.. Why and when would I use SYSTEM OBJECT in a w2k3 restore with a 5.2 client. It got to be a reason why that possibility still exist? Documenta
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-01/msg00705.html (17,660 bytes)

4. Re: TSM client uppgrade 5.1.7.3 to 5.2.3.11 (score: 1)
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 25 Jan 2005 08:14:53 -0700
still 1) You install the 5.3 client on Monday. 2) Backup runs Monday night. New SYSTEM STATE and SYSTEM SERVICES file spaces are created. Old SYSTEM OBJECT file space is left intact. 3) You discover
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-01/msg00712.html (17,990 bytes)


This search system is powered by Namazu