And that's the way I have always done it in the past; sometimes it
worked, more times than not it didn't. I'm looking for something that
always works and hopefully this is it. Restoring to similar hardware was
always easier and dissimilar hardware was always a nightmare. In this
particular case, this was a VMWare virtual client and all I'm using is
the normal NetBackup Windows client. I haven't implemented anything to
protect VMWare yet. The first restore failed with a black screen that
read
Windows could not start because of an error in the software.
Please report this problem as:
Load needed DLLs for HAL.
Please contact your support person to report this problem.
In most of the failed restores, after reboot, the restored client would
go into a continuous reboot mode right after the Windows splash screen
appeared. For this restore, I tried it again and excluded the hal.dll
file and the server booted up fine but the registry had not been
restored. I think this process is going to fix that if I can find
someone to let me use their server as a guinea pig.
-----Original Message-----
From: Mike Kiles [mailto:mikekiles AT yahoo DOT com]
Sent: Thursday, February 14, 2008 10:25 AM
To: Rosenkoetter, Gabriel; Randy Samora;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Restoring Shadow Copy Component/System State
I recently did a full system restore of a win2k3
machine to another win2k3 machine and didnot follow
the doc. Here is what I did:
1. Backup server A (ALL_LOCAL_DRIVES) running win2k3
NBU6.0MP4
2. On server B, which is also win2k3, install
NBU6.0MP4
3. From Master, did a full system restore of server A
onto server B (C: D: E: F: G: and Shadow Copy
Components
4. After restore is done, I unlug network cable from
server B and reboot
5. When B came up, changed the name and IP addr, and
boot again
6. At this point server B has the same software loaded
as that of A and identical config
I did the same procdure on 3 machines so far, same
hardware, except missing one emulex HBA in one
machine.
Cheers
MK
--- "Rosenkoetter, Gabriel"
<Gabriel.Rosenkoetter AT radian DOT biz> wrote:
> Assuming that you've got either the Shadow Copy
> Components:\ target (or,
> preferably, ALL_LOCAL_DRIVES) in the policy's
> include list, then there
> are a few extra steps you should take when doing a
> full system restore
> for Win2k3 (while not using BMR, which "should" take
> care of all of this
> for you).
>
> This tech note does a pretty good job of describing
> it:
>
> http://support.veritas.com/docs/295342
>
> The main nut of it is that you need to do an OS
> install, a NetBackup
> client install, go run [...]\VERITAS\bin\w2koption
> -restore
> -same_hardware 1 once, perform the restore, then run
> the same command
> again (because you just laid down a restored
> registry in which that may
> not have been set, is my understanding), then
> reboot. And cross your
> fingers.
>
> (That said, it still tends to be hairy, especially
> for domain
> controllers--or whatever we call those in an AD
> world--and a co-worker
> has a case open in which portions of SCC fail to
> restore properly on a
> DC under 6.5...)
>
> --
> gabriel rosenkoetter
> Radian Group Inc, Unix/Linux/VMware Sysadmin /
> Backup & Recovery
> gabriel.rosenkoetter AT radian DOT biz, 215 231 1556
>
>
>
> ________________________________
>
> From: Randy Samora [mailto:Randy.Samora AT stewart DOT com]
> Sent: Wednesday, February 13, 2008 6:21 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Restoring Shadow Copy
> Component/System State
>
>
>
> Part of my requirements are test restores of
> critical boxes in a lab
> environment. The lab is isolated and when I restore
> a client, there's
> not really much we can test because the client looks
> for the production
> network. Today I had to restore a Windows 2003
> Server in the production
> environment and most of the registry wasn't
> restored; services and other
> objects were missing. With the test restores, I
> always had the option
> of doing an ntbackup of the System State and then I
> would run a full
> backup of the client. I'd take my tape to the lab,
> run a full restore,
> but before I rebooted the restored client, I
> restored the ntbackup of
> the System State (Shadow Copy Component.) That
> seemed to work just
> fine. But today when the server blew up, there was
> no opportunity to do
> an ntbackup of the SS first. I asked Symantec last
> year if the ntbackup
> was still needed and they said no, a full backup and
> restore should
> recover the client. I just never had the chance to
> test that theory.
>
>
>
> Am I missing a step? I installed the OS from a
> basic CD install, loaded
> the NBU client, and then did a full restore. But
> it's as if the system
> state was never restored so I'm wondering if I'm
> even backing it up.
> How can I tell? Do I need VSS or VSP activated in
> order to get a good
> copy of the system state? We turned VSP off over a
> year ago because we
> were having problems with the orphaned cache files.
> I've never gone
> back and changed the setting on most of the clients
> and my plans were to
> start using VSS but haven't gotten to that task
> either. Is there a
> trick or an added step to getting a good backup of
> the system state on a
> Windows 2003 Server server or is there a trick to
> restoring it?
>
>
>
> Thanks,
>
> Randy
>
>
>
> > _______________________________________________
> Veritas-bu maillist -
> Veritas-bu AT mailman.eng.auburn DOT edu
>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
________________________________________________________________________
____________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
