Discussion Locked

Swap HD in a W2k DC

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I need to replace the HDs in our DC. This DC also holds the Master catalog
role, Exchange 5.5, Terminal services licensing, AD, File server, Print services, etc. There
are 2 other DCs in a single domain WAN.

We use BackupExec 8.5 with an HP SDLT drive for backup and appropriate
agents. My plan is to do a complete restore of all the administrative shares
& the system state.

1. Since I'm doing a complete restore, do I need to check options like
"Restore Terminal Services DB" under the Windows 2000 tab in BE? I'm not sure what that option means & in what situations it should be used.

2. Since I'm doing a restore of all the files in "exchsrvr" server folder
including log files, priv.edb, pub.edb, etc., do I also have check "Restore
Private mailboxes" & "Restore Public folders" under the Exchange tab in BE
or is that already covered by restoring all the files?

3. What about making SYSVOL the primary arbitrator? Do I need to do that?

Please, feel free to point out any other possible pitfalls, hints, etc.

Thanks,

6 replies

by p.j.hutchison

1. I suggest you do include that. The licencing info is important for TS to work.
2. If backing up all the edb, stm and trans logs, then the other options are not required (its probably a 'brick-level' type restore).
3. Not sure.

Since the server is a DC, you need to boot into Safe Mode with Directory Services Restore Mode to allow you to restore System State etc.

by carlossommer

Tried that using another machine. I checked the Restore Terminal Services DB in BE and got this error: "An error occurred retrieving the TS Database data directory. The TS Database could not be restored."

Also, when restoring the C$ share, at one point it prompted me to restart the server in order to restore files that are in use. I have done other restores of W2k Server with no AD, and never ran into this issue, but I used NTBackup rather then BE.

by carlossommer

Not a good idea because I have to sysprep the original HDs first which I don't want to do since I want the origial HDs intact so that if all else fails, I have something to go back to.

by yetanotheradmin

While I don't strictly agree with Norton Ghost being the answer, you normally use sysprep to remove any identifiers like the SID. However, if the cloned disk is going back into the same system this isn't an issue. I've never used ghost with a server before, let alone a DC so I have no idea how it would affect shares. The admin shares on a workstation are fine but that's no guarantee.

by mikex

Since Nghost is used under the NTFS dos on a low level - you'll get the exact copy of your entire hard drive which you need to replace (the new one must be with the equal or bigger size then the old one attached as a Master (old)=>Slave(new) no mather on 1st or 2nd chanel). With Veritas you cannot do the same, it's for Backup/Restore.

This discussion is closed to new replies.