Hi, this is my 1st time on this service.........
I am also in the throes of getting an ADSM NT client recovered in "BARE
METAL" restore mode.....we had many problems.....of which one was the
REGISTRY problem you described. We will be attempting this exercise again
later in February. Are there (apologies if u already discussed this subject
to death here) any important information regarding the "BARE METALS
RESTORE" steps as described in the IBM Redbook of the same name that I need
to be aware of?
Secondly, we also attempting to recover an Novell NETWARE 4.11 ADSM
client.....with problems like missing files....NDS conflicts and too big
files to built SAlone restore media with. Any input on Novell 4.11 Bare
Metal Restore will be welcomed.
Thank u in advance.
Campbell Esplin
Excalibur Business Solutions
----------
> From: Prather, Wanda <PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU>
> From: Prather, Wanda <PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Registry Restore to Identical Hardware
> Date: Sunday, January 25, 1998 6:13 PM
>
> Eric,
>
> We have done what you describe for NT 4.0 machines, i.e., restoring over
> the C drive.
> It works for us.
> There is one difference in our process, step 2.
>
> 1) Install NT from CD
> 2) Reinstall NT service packs that were on the failed machine
> 3) Install the ADSM client - edit the dsm.opt file NODENAME to be the
> same as before
> 4) Restore over the C drive.
> 5) Restore the registry
>
> When you do this, as you describe, some .dll and .exe files cannot be
> replaced during the restore because they are in use.
>
> The one time we had this fail, the machine failed to reboot as yours
> did, and it was because we skipped step (2) above. Presumably, there was
> some difference in the registry or in those .dll or .exe files that kept
> the machine from rebooting.
>
> So my belief is you can make it work IF:
>
> 1) Your backup is VERY recent, so there have been no significant
> registry changes, and
> 2) You KNOW what level of NT was installed on the machine, and can get
> it back to that level before starting the ADSM restore, so that all .dll
> files and .exe files and the registry end up at the right level.
>
> I'm not saying this is the best way to go, just that it CAN be done IF
> you know the machine well.
>
> I think the PREFERABLE WAY to do this is by installing to a different
> directory, as was described in an earlier response.
> That method is considerably safer, and not so exacting.
>
>
> ===============================================================
> Wanda Prather
> Johns Hopkins Applied Physics Lab
> 301-953-6000 X8769
> wanda_prather AT jhuapl DOT edu
>
> "Intelligence has much less practical application than you'd think."
> - Scott Adams/Dilbert
> ===============================================================
>
>
>
>
>
>
> ----------
> From: evanloon AT klm DOT nl[SMTP:evanloon AT klm DOT nl] on behalf
> of Eric
> van Loon[SMTP:evanloon AT klm DOT nl]
> Sent: Friday, January 23, 1998 3:24 AM
> To: 'ADSM: Dist Stor Manager'
> Subject: RE: Registry Restore to Identical Hardware
>
> Hi Dennis,
> If I understand you correctly you did the following:
> 1) Install NT from CD
> 2) Install the ADSM client
> 3) Do a full restore (Subdir=yes Replace=All) of the C: drive
> Am I correct??
> I did this and ADSM refused to replace .DLL, .EXE and .FNT files
> which were in use by Windows NT. This caused the PC to hang after
> rebooting and I had to repair the bootpartition using the Windows NT
> disks.
> I was using Windows NT 4.0 and I tried resoring it to the state
> before the format which was Windows NT 4.0 SP3. I tried using both the
> GUI and the commandline interface.
> Kindest regards,
> Eric van Loon
>
> ----------
> From: Dennis Riley
> Sent: donderdag 22 januari 1998 22:12
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Registry Restore to Identical Hardware
>
> Please forgive me if this is a duplicate posting.
> ---------------------- Forwarded by Dennis
> Riley/BLLVRLNS3/USWEST/US on
> 01/22/98 01:22 PM ---------------------------
>
> From: Dennis Riley on 01/21/98 11:07 AM
>
> To: ADSM-L @ VM.MARIST.EDU
> cc:
> Subject: Registry Restore to Identical Hardware
>
> We are attempting to do a baremetal restore of an NT
> client to identical
> hardware (in fact the same box) without using an
> additional maintenance
> partition. We load the OS, ADSM, and restore all the
> files to the machine
> fine, including the ADSM.SYS directory. But when we use
> 'Restore Registry', it
> says it cannot find the registry information for that
> machine. ADSM is
> capable of doing the registry restore when it thinks it
> is the same machine,
> so it seems like there must be some sort of
> precautionary measure preventing
> this from happening. How can we fool Registry Restore
> into thinking the new
> server is the old server, so we can recover the
> registry?
|
