To all you MCSE people.

Need to test a disaster recovery of the domain at work. And as I'm the only person who looks after the domain how do you do it

Right So far my plan was to install a fresh server 2003 as part of a workgroup on different hardware .

Install veritas and restore the system state. Then before reboot set the Burflags to share the sysvol folder after a reboot.

And then as it fails to boot.

So now I have a server 2003 with a restored system state which is unable to boot

Now in windows 2000 you use to have a repair os option. Server 2003 only has the recovery console to which are administrator password will not let me login

So the question is am I barking up the wrong tree?

Why wont the admin password work? Is it because we have renamed the admin account?

If I am going about it the right way and I get into the recovery console what next?

:rofl: :rofl:

As you can guess I'm having a laugh as they pay me **** money and expect me to know this.

Did you boot into directory services restore mode before restoring from backup?

Did you boot into directory services restore mode before restoring from backup?

That would be a no. But I just read that somewhere. Thats at the safe mode prompt isnt it?

Do a need to recover the system state from their?

Yes , hit F8 as it's booting then use that option to restore your backup

Yes , hit F8 as it's booting then use that option to restore your backup

Right I'll give that ago. Good job I've made an image.

So after the restore will the pc reboot? I take it I need to set the burflags to restore the sysvol share?

You'll need a reboot after the restore.

As for the Burflags , pass.

What version of Backup Exec are you using?

Sorry ment to say after the restore. When I reboot will the os load or just blue screen?

Using version 9.1.

Cheers

After the restore it *should* just reboot and function normally

After the restore it *should* just reboot and function normally

Right well just restoring my image then I'll give it ago.

Cheers for your help.

After the restore it *should* just reboot and function normally

But usually only if the hardware is the same. If restoring to a different disk controller type it will blue screen.

I do this every year, to check that the backups are valid and that my employer can get up and running again. What I do is,

1) Install 2003, and any patches required to get the backup software to install.

2) Install Backup software, and any required agents.

3) Configure all the drives as per the original machine, partition sizes dont matter as long as the drive letters are the same and each one is larger than the data to be restored.

4) Performe a whole restore in one hit, make sure the options to restore registry and system state are ticked if your software requires this.

5) Reboot, most likely will blue screen.

6) if it blue screens, then run a repair install of 2003 over the top, the first repair may fail, if so just start the repair process again and it will go through the second time.

7) install any drivers needed for networking and configure.

Voila, should all be running.

You only need to use DS restore mode on the DC.

Cheers Mannyo.

So when load the os cd I only see an option for a fresh install of the os?

Also does the PC name need to be the same?

Cheers Mannyo.

So when load the os cd I only see an option for a fresh install of the os?

Yes, thats right, then proceed and it should once all the drivers have loaded locate your current install and offer you the chance to repair it.

This is different to repairing using the recovery console, if you see that just press enter to install a fresh copy, its the seconf repair option you want.

When you do the initial install, the computer name can be anything you like, as when you restore over the top with the registry and system state restored then thats overwritten anyway.

When you do the initial install, the computer name can be anything you like, as when you restore over the top with the registry and system state restored then thats overwritten anyway.

Thats what I thought.

So I was on the right lines before then. Cool. Just when I didnt see a repair os option I thought it was no longer available

Any idea why in the recovery console my password doesnt work?

Any idea why in the recovery console my password doesnt work?

Because you dont have a working AD. The password that is needed is the local administrator password not the domain one.

that didnt work either :confused:

Anyway just about to restore now.

PMSL....

just get more DCs and GCs.. you can never have too many

that didnt work either :confused:

Anyway just about to restore now.

How to Change the Recovery Console Administrator Password on a Domain Controller

PMSL....

just get more DCs and GCs.. you can never have too many

I already have 3.

We now have a contingency site. So as part of are DR we need to know if we can recovery the domain from a total loss

Well I'm at home now so I'll find out tomorrow if I can do it or not. If not no one can.

Just on a side note.. if restoring to the same hardware it might be worth checking out BartPE just save time having to do an OS install and config...

Just on a side note.. if restoring to the same hardware it might be worth checking out BartPE just save time having to do an OS install and config...

Trying to avoid the same hardware to give a true test.

BartPE is cool. But now like Reatogo XPE

Update.

with a fresh 2003 server in a workgroup. I've restored the system state using Veritas 9.1. Note at the end of the restore it fails as it cannot overwrite 1 file??? :confused:

Ignoring that. reboot server. Blue screen.

Repair OS. Hangs on Windows 2003 server loading screen.

Repair OS again. windows gets to the installation screen but with a erro message saying Directory Service cannot start. Restart into Recovery mode.

Cant understand why Veritas fails on 1 file and the report doesnt tell me which file or anyfile thats been restored.

Manyo any advice?

Tell them its f00ked until they pay you more...

Has the system state backed up correctly, did you set the restore options to restore said system state, and the registry.

Its normal for the first repair to fail.

Try this, forget about veritas for a moment.

Backup the live server C: drive using the builtin "NTBACKUP" program, backup to a file on say the D: drive rather than to tape. Include the system state in this backup. Copy the large file to a blank dvd media or USB stick.

Restore that backup on the target server, including system state whilst in DS restore mode and then do the 2003 repair again.