Thanks to all who responded, but we've tried all the suggestions, and we
encountered a very odd problem. And in addition, the machine still won't
boot. In fact, it hangs a little over half way through the progress
meter, just like before.
Here's the scoop. We re-installed an image of the OS that we had created
after re-installing the OS the other day. We then installed the older
version of the client (6.x), unlike our first attempt where we were
using a newer version (7.x). We then logged in as a local administrator,
unlike before when we were logged in as a domain admin. The system was
NOT a member of the domain. Next, we recovered E:\ and then C:\.
Everything went prefectly smoothly. Then we marked all three of the
special savesets for recovery, allowing NetWorker to determine the
order. However, unlike before, NetWorker immediately issued the
following in the Recover Status window:
Recovering files of client 'client_name' from server 'server_name'.
Preparing for SYSTEM FILES recover, please wait...
Preparing for SYSTEM DB recover, please wait...
Preparing for SYSTEM STATE recover, please wait...
This took about 30 seconds. BUT, for whatever unexplained reasons,
NOTHING happened!!! The tape drive simply reported *NO* activity. No
moving forward or backward x files or x records like we would have
expected. Nothing. All of the special save sets are contained on the
same volume as the C:\ and E:\ savesets. It just sat, completely
dormant. I checked the log files on the server. No messages. Nothing
suspect. The server reported that the client was browsing, but about 30
seconds after issuing the recover start, the client recover program
issues the above messages, and then the server reports that the client
is done browsing! We never stopped the recover! So, no data gets
recovered. We even tried rebooting the server, stopping and re-starting
the client recover several times fro scratch again. Same mischief.
These special savesets are NOT empty. SYSTEM STATE=18 MB, SYSTEM
FILES=235 MB, and SYSTEM DB=43 MB. We noticed before, when we were using
a newer version of the client, and logged in as domain admin, it would
at least recover all three of the savesets one at a time, and not just
jump through them lickidy split, recovering nothing like it did this
time. Seems very strange. Anyway, just for laughs, we decided to reboot
anyway, knowing full well that it hadn't recovered anything for these
last savesets, but what the heck. Sure enough, it hangs at boot.
Here's what we've tried:
------------------------
x get rid of images partition F:, and make E: original size
x use local admin account
x PC not in domain
x version 6 of Legato client, not 7.x like before
x set page file to 3072 on E:, 2 on C:
x Removed network cable before rebooting after recovery
Have not tried: Install Windows to a different directory
We are running 6.1.1 on the primary server, which runs Solaris.
Any further ideas?
Thanks.
George
"Neild, Jim" wrote:
>
> Actually all you have to do is the following to get it back up and
> running:
>
> 1) Configure the disks the same as before
> 2) Rebuild the base OS, Service Pack doesn't matter as you will
> overwrite everything anyway, including the REG (It should be in a
> Workgroup)
> 3) Log in as Local Admin
> 4) Config the NIC (disable all but one if it has several) (ensure DNS
> and DNS suffixes are the same)
> 5) Configure special connectivity settings if applicable (FW port
> ranges, RPC port ranges, routes, etc.)
> 6) Install same version of Legato that was present before
> 7) Add all applicable Storage Nodes, NetWorker Server and Client entries
> in HOSTS files of all servers involved in recovery
> 8) Start WinWorker and select all savesets (drives and SYSTEM) at the
> sametime
> 9) Select OVERWRITE
> 10) Click START!
> 11) When the restore is complete, reboot as requested
> 12) Box will boot up and go down again (this is the replacement of the
> locked files and registry)
> 13) Box comes back up again and it should work like it did before.
>
> Worked for us just two days ago ;-)
>
> Cheers,
> Jim
>
> -----Original Message-----
> From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT
> EDU]
> On Behalf Of Itzik Meirson
> Sent: April 26, 2005 4:42 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Windows 2000 box won't boot after recovery
>
> George,
> The disaster recovery manual clearly states that you should leave the
> machine in a "workgroup" and not add it to the domain. This of course
> will disable your login as domain administrator.
>
> After recovering the "SYSTEM" savesets and rebooting the machine it
> should come up in the original domain. You will have also to make sure
> you used the exact same Networker client version that was originally on
> the machine.
>
> HTH,
> Itzik
>
> > -----Original Message-----
> > From: Legato NetWorker discussion
> > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of George Sinclair
> > Sent: Tuesday, April 26, 2005 22:52
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: [Networker] Windows 2000 box won't boot after recovery
> >
> > Hi,
> >
> > We had a Windows 2000 machine (service pack 4 with latest
> > updates as of a week ago) whose hard drive failed last week.
> > It was running an NTFS file system. The hard drive died
> > sometime after the most recent 'full'
> > backups were run. There were no subsequent backups after the
> > fulls, however. Our primary backup server is running on Solaris.
> >
> > We installed a new drive in the same box and reinstalled
> > Windows 2000 OS with service pack 4, but no later updates.
> > Also used NTFS file system, same as before. This system has
> > the same host name as the old one, too.
> > We then installed Legato NetWorker client and ran the recover
> > utility to recover the following "full" savesets from the
> > previous client:
> >
> > C:\
> > E:\
> > SYSTEM DB
> > SYSTEM STATE
> > SYSTEM FILES
> >
> > We recovered E:\ first, followed by C:\ and then selected all
> > of the last three special savesets, and NetWorker basically
> > chose the order to recover those guys in. We did have
> > 'overwrite and no further prompts'
> > selected. The recovery went smoothly, but when we rebooted
> > the machine, it got about half way through the boot process
> > and hung; the progress meter stopped about half way across.
> > We waited a long time, but no further action. We then power
> > cycled the host. Same problem again. What should we do now?
> > Any ideas why this would happen? Would appreciate any advice.
> >
> > The only thing I can think of is that we we're logged in as
> > the domain administrator and not the local admin. when we ran
> > the recovery. Not sure this would make a difference?
> >
> > I'm still not sure I understand just how NetWorker can
> > recover older data back on top of newer stuff and still
> > expect things to work. How does it manage such choreography?
> >
> > George
> >
> > --
> > Note: To sign off this list, send a "signoff networker"
> > command via email to listserv AT listserv.temple DOT edu or visit
> > the list's Web site at
> > http://listserv.temple.edu/archives/networker.html where you
> > can also view and post messages to the list. Questions
> > regarding this list should be sent to stan AT temple DOT edu
> > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
> >
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email
> to listserv AT listserv.temple DOT edu or visit the list's Web site at
> http://listserv.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listserv.temple DOT edu or visit the list's Web site at
> http://listserv.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
