just as Kenny, not.
We have got, however, minor problems with network driver and vga driver,
network card could be helped by simply reconfiguring some parameters like
full duplex,
vga driver worked only in vga/svga modes but driver update helped.
While dubious, not a real problem.
No other problems so far, especially not with AD.
regards
Juraj
-----Ursprüngliche Nachricht-----
Von: Bill Boyer [mailto:bill.boyer AT VERIZON DOT NET]
Gesendet: Mittwoch, 25. Februar 2004 19:29
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: Full W2K Server restore
Did you have to boot into AD Recovery mode (F8) before doing the system
object restore??
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Salak Juraj
Sent: Wednesday, February 25, 2004 1:21 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: AW: Full W2K Server restore
I can fully second to Kenny,
very same experiences with restore
and later swap to VMWARE here.
Juraj Salak
-----Urspr|ngliche Nachricht-----
Von: Barnes, Kenny [mailto:Kenny.Barnes AT GMACINSURANCE DOT COM]
Gesendet: Mittwoch, 25. Februar 2004 17:20
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: Full W2K Server restore
We have been able to restore AD to the same hardware by restoring the
c:\* and then restoring all system objects with out rebooting. Once both
have been restored, then reboot. Restoring to different hardware is
another story.
Client version 5.1.5.
We are starting to use VMware and run a DC with no primary roles and
backup the OS as a file and restore the file from TSM.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Magalie Siaud
Sent: Tuesday, December 23, 2003 7:09 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Full W2K Server restore
Hi all.
We are using TSM 5.1.6 to backup w2k nodes. These nodes are W2K server
Domain controllers.
We are testing full restores on other kind hardwre. We have been working
on the Bare Metal restore Redbook.
Our procedure was to:
1- Bring a new machine with different hardware, same IP, same nodename
5Ip
could be different), with W2K server and TSM client 5.16 pre-installed,
2- Restore the whole machine on the new one, except systemobjects,
3- Reboot the new server, in AD reconstruction mode,
4- Restore the systemobjects,
5- Reboot.
Unfortunately, we are not able to restore the systemobjects in the 4th
step. TSm don't even allow us to do it. Object ID problem??
Anyone has been able to test a full restore for w2k servers using
different hardware, even same hardware?
The problem using different hardware versus same hardware should be HAL
compatibility slice, shouldn't it? This is solved when using Ntbackup
(merge some registry entries related to hardware specifications).
Therefore we are trying to get rid of it too with TSM...
Magalie Siaud.
----------------------------------------------------------------------------
----------------------------------------------------------------------
Note: The information contained in this message may be privileged and
confidential
and protected from disclosure. If the reader of this message is not the
intended recipient,
or an employee or agent responsible for delivering this message to the
intended recipient,
you are hereby notified that any dissemination, distribution or copying of
this communication
is strictly prohibited. If you have received this communication in error,
please notify us
immediately by replying to the message and deleting it from your computer...
Thank you.
----------------------------------------------------------------------------
----------------------------------------------------------------------
|
