Jeff
Tue Sep 02 08:09:15 CDT 2003
You can follow the steps outlined below. (note, this is a snip from a post
on a different thread I did last week)
235478 Recovering from Failed System Drive with Non-Default %SystemRoot%
Folder
If you don't like either of those options, then the way that MS documents to
do this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;263532
http://support.microsoft.com/default.aspx?scid=kb;en-us;240363
- Install W2K server from scratch using the same system folder name as the
current SBS, completing only the basic W2K server setup....not the AD, not
the rest of the stuff....just the initial process to get to the first point
you can run the server at a Windows desktop condition.
- Create partitions the same size or relatively larger as the existing
system so that you have a place to restore to, and change the drive letters
per partition to match what you had.
- Install whatever drivers and applications you need to run your tape
restore process
- make an ERD and System State backup
- reboot and start in Safe Mode DSRM mode, select to restore all data
partitions, and restore the System State from the previous machine. Do not
request to restore the Exchange databases...it's not going to work anyway at
this point. You may run into problems here with NIC bindings. This is an
unavoidable problem in W2k System State restores to different hardware.
810161 Network Adapters Are Missing or Incorrect in Device Manager After You
Run NTBackup to Restore System State Data
- Shutdown and restart in Safe Mode DSRM again. If you rebooted normally
here, following the reboot, you should get a working boot, but you will
likely have errors reported on a number of things, including the Exchange
(which has no data) and a number of services that depend upon the NICs being
properly connected....which they will not be at this time. In safe mode you
will still get errors, just fewer of them. When you can access the Network
Properties, you will want to correctly set the static IP, mask, subnet and
DNS info on each of the NICs. With those things corrected, the server should
operate normally following the next normal reboot, other than that the
Exchange will still not be functional until you have a normal restore of it.
- On the next reboot, you should startup in the normal mode. Once you are
able to logon, inspect the logs and confirm that everything looks normal,
other than Exchange. Until everything else is normal, don't try to restore
the Exchange, you are just complicating your life. Once everything else
works normally, now you do the Exchange restore. This typically in a restore
of an Online Backup in which you use the backup program to restore the live
Exchange. Alternatively, and offline backup would be restored by clearing
the databases and logs from the MDBDATA folder and copying the old ones back
in. You typically have to tick the selection in the Store reference for
"allow store to be overwritten".
These instructions are intended to be summary in form, not a literal step
process. Therefore, you need to be familiar with the concepts I just
outlined already. If you are not, you should contact an experience IT
support person to do this sort of migration. You might otherwise not
remember to do things like disconnecting the computer from the web and
network during the process, or making interim ERD disks, or preparing for
returning the old server to service in a pinch.
"Thomas Anderson" <tanderson@dynamicnetworx.com> wrote in message
news:01c901c370cf$54804720$a601280a@phx.gbl...
> We had a system crash and we are trying to get it back
> up. Backup was ran using BackupExec 8.6 SBS edition.
> First problem is the version of SBS that we are working
> with does not allow parallel install (no option during
> setup to pick WinNT directory). Then after we get the
> systme up and running, all ok at this point. We try to
> restore AD and and then all hell breaks loose. We lose
> all the drivers for NICs (called MS on this one and ended
> up worse than before I called them). We also can't get
> the Exchange to restore, keep getting error that the
> restore loses connection or something. I know there are a
> lot of issue with restoring SBS, but it has to be
> recoverable. Any links to how to get this thing back up
> and running would be greatly appreciated. Oh yeah, called
> Veritas and they say everything should be working....