Now that you mention it, you do have to be local admin. In addition, when
the system is rebuilt to its original OS and Service Pack level, it should
*not* be added to its domain before the recovery. (This was true for 6.x
should be for 7.x too).
When the new build is added to the domain with the same name as the
original, the SID of the machine account on the domain is changed. When
the SYSTEM_STATE is recovered over the new build, the local machine's SID
is changed back to the original at the time of the last backup applied
(SYSTEM_STATE is always a Full backup). When you reboot to complete the
recovery, you can't get on the domain because the SID's don't match. If
you don't add the machine to the domain before the recovery (and hence use
a local administrator account), the SID of the machine is overwritten with
the proper SID so when it reboots, there aren't any mismatches.
The work-around if you add the system first and then restore is to drop
the machine from the domain and re-add it or reset the secure channel (AD
environment). If you do the recover the recommended way, it saves you
these steps (....and reboots).
Not adding it to the domain works because Legato doesn't care about domain
membership; just user account rights & permissions. We have done this
*many* times both testing and when we needed it with no problems.
Jeff Mery - MCSE, MCP
National Instruments
-------------------------------------------------------------------------
"Allow me to extol the virtues of the Net Fairy, and of all the fantastic
dorks that make the nice packets go from here to there. Amen."
TB - Penny Arcade
-------------------------------------------------------------------------
Ernst Bokkelkamp <ernst AT BOKKELKAMP DOT DE>
Sent by: Legato NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
04/26/2005 03:12 PM
Please respond to
Legato NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please
respond to
Ernst Bokkelkamp <ernst AT BOKKELKAMP DOT DE>
To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc
Subject
Re: [Networker] Windows 2000 box won't boot after recovery
If I remember correctly this is your problem:
>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 am sure that the documentation states that it must be a local admin
because we ran into a similar problem.
I've looked for a reference but the only thing I could find is on page 34
of
the 7.2 release notes for Windows.
Bye
Ernie
----- Original Message -----
From: "George Sinclair" <George.Sinclair AT NOAA DOT GOV>
To: <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
Sent: Tuesday, April 26, 2005 9:52 PM
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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
