Cross BlueShield of Tennessee
423-752-6574 (desk)
423-785-7347 (cell)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Prather, Wanda
Sent: Wednesday, January 25, 2006 11:29 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] System object restore pr
Reed
Sent: Wednesday, January 25, 2006 4:54 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: System object restore problem
Thomas,
One other thing. You mention that you have actually managed to complete
this method successfully with 5.1.x.x and 5.2.x.x code. Bear in mind
that there were a number of bug
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thomas Denier
Sent: 24 January 2006 21:25
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] System object restore problem
We just went through a disaster recovery test, using the following
process
for each
e a
restore LAN segment from this.
Leigh
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thomas Denier
Sent: 24 January 2006 21:25
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] System object restore problem
We just went through a disaster recovery
We just went through a disaster recovery test, using the following process
for each Windows 2000 system involved:
1.Give the replacement system a different computer name than its production
counterpart.
2.Execute a 'rename node' command against the recreated TSM database to
change the node name ma
Our NT admins requested that we build one server(HCB1) from another servers
backups(SYR1). The servers are Windows 2000 Advanced Server running
service pack one with identical hardware. Our TSM server is V4.1.2 on AIX
4.3 and the Windows Client is 4.1.2.14. We used the TSM B/A CLI with the
vi
