• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

active directory backup?

N

ncage

Golden Member
Guys will you send me to a VERY detailed link or give me detailed information on exactly how to do this. I posted this sometime back when i did something similar and i lost all my active directory stuff and had to recreate it. I don't want to have to do that again. Here is my dilema. I have active directory and my dns server installed on Windows 2003 Enterprise R2 X64. Ok in my opinion the X64 version SUCKS big time. I have had way to many blue screens and have so many services i have running on this machine (even my internet connection is based here). I can not have this machine go down so much. I had the x86 version before and had no trouble before and am going back to it. Anyways this poses a dilema for me. Most of the services i have running i am very competant at like SQL Server. When it comes to Active directory im pretty much a newbie. I do not want to love all my active directory / dns stuff.

Here is my plan. I want to set up a vmware instance of Win2003 svr on another machine. Make this machine my BDC (i know its not called this anymore but you pretty much get my gist). Before i wipe the machine i will demote the server in the active directory tree and promote my vmware instance. I need details on exactly how to do this. Like i said last time i tried it i hosed my directory and i don't want to do this again. Can anyone help please.

thanks,
ncage
 
I'm sure that some of the AD experts who hang out here will give you the exact details. As long as your DNS is AD-Integrated, it shouldn't be a big deal to migrate to the new X86 Server. Obviously, I suggest making a full system backup (including System State) with NTBackup (or some other AD-compatible backup program) before starting.

After getting instructions, you might consider doing a "practice" migration inside of a pair of virtual machines. It really doesn't take that long to install and set up Server 2003 inside a virtual machine.

I'm amazed that 2003 Enterprise RC2 X64 was blue screening like that. Did the MS Crash Analysis ever say where the problem lay?
 
Install the vmware server, and use the wizard to add dns and active directory roles to the new server. You want to be sure the new server is set up as a BDC before demoting the old server.

run dcpromo at the command line on the old server (you can probably also do this through the roles wizard). Follow the instructions to demote this server. Dcpromo will take care of transferring everything over to the new server automatically. Once this is done you can remove the old server from AD using the Computers and Users tool and reformat it or whatever you want to do with it.

And by the way, never ever ever ever never never ever never ever never remove or wipe a domain controller without running dcpromo to demote it first.
 
You should always have at least two DCs to avoid situations like this. Adding or removing a DC should be a routine operation.
 
AD is multi-master so there is no such thing as a PDC or BDC. There are some single DC only roles (FSMO roles) however they can be moved around easily (even if you loose the DC holding that role).

I'm with RM & Stash in that you need to be testing this and familiar with the process. If you're not very comfortable promoting/demoting and moving the roles around than perhaps you should consider hiring someone to come in and help.

I'm also surprised to see that you're getting crashes, it's been very stable on all my builds. I suspect a hardware/driver issue.
 
Requesting a "detailed forum post" as a means to learn how to properly backup AD is probably not the best idea.

Go do some reading. Check the product documentation and best practices at MS. Remember, and untested backup isn't really valid for disaster recovery.
 
The less-than-desirable, but-it-does-work way to do this would be to backup the system state, rebuild the box, and then restore the system state.

That will restore the computer name, status as a DC, and pretty much everything having to do with Active Directory.

I've done it once. The only issue is that it appears that passwords are not restored, so you'd need to be ready to reset everyone's password. It did not appear to break the domain admin's password, though.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top