Mike:
Yes, this does help because you have had recent experience --- I'll give
you a buzz on this after the long weekend!
C.L.Cannam
Storage Management
GENAM/St. Louis, MO/USA
ccannam AT genam DOT com
Mike Garcia <mike.garcia AT CONPAPERS DOT COM> on 05/21/98 02:32:15 PM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Cindy Cannam)
Subject: Re: adsm and required times for DR -Reply -Reply
Having just completed a bare metal restore to a NT 4.0 client, I t was a
snap once I found out that the ADSM.sys file that is created during
incremental backup of the client is where your registry information that
you need is kept. We took a new pc installed the NT server software, ADSM,
the edited dsm.opt to have the nodename indicate the old nodename. Then
performed a restore and the LAN Administrator copied the
ADSM.sys files under the system32/config where the belong and the rebooted
the system. If you need further information you may reach us at
715-422-3811 and we can discuss in further detail.
Hope this helps.
JCirocco AT GW.CTG DOT COM on 05/21/98 01:52:28 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Mike Garcia/CPI)
Subject: Re: adsm and required times for DR -Reply -Reply
Hilary,
> What method are you using to "recover" your NT servers?
We are currently attempting to recover to different hardware using the
bare metal restore red book. To identical hardware it worked like a
champ. To different hardware (manufacturer, DASD, # processors, etc)
less than acceptable (much less!!!)
Our Netware, SCO Unix, Sun and Lynux all went well. Only NT is giving
me fits. I am to the point where I will just have an identical spare
server
sitting around for the mission critical systems...
HTH,
John
John W. Cirocco
Manager, Data Center Operations
Computer Task Group, Inc.
700 Delaware Ave
Buffalo, NY 14209
Office - (716) 888-3566
Pager - 1-800-283-2255 pin#12029
JCirocco AT gw.ctg DOT com
|
