Computing.Net > Forums > Windows Server 2003 > Backup Domain Controller

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Backup Domain Controller

Reply to Message Icon

Name: Paul B (by pbedorf)
Date: April 9, 2007 at 12:30:14 Pacific
OS: 2003
CPU/Ram: 1GB
Product: IBM
Comment:

Hi, we have one primary domain controller and one backup domain controller. If the primary controller fails, will the backup domain controller automatically take over? or do we have to manually promote it to the primary domain controller?

Paul B



Sponsored Link
Ads by Google

Response Number 1
Name: wanderer
Date: April 9, 2007 at 12:48:00 Pacific
Reply:

You either have Active Directory or you don't.

Either way you don't have primary or backup DC's. Those are concepts/vocabulary from NT not Active Directory.

Google Active Directory Best Practices and get yourself a book 2003 server. You will be glad you did.

Are you ready for where Microsoft wants you to go today?


0

Response Number 2
Name: Paul B (by pbedorf)
Date: April 10, 2007 at 05:57:31 Pacific
Reply:

so if we have a backup server running active directory which is replicating between the primary server running ad, can we utilize that server if the primary one fails? will it be a true PDC or we have to change something!

Paul B


0

Response Number 3
Name: wanderer
Date: April 10, 2007 at 08:07:34 Pacific
Reply:

Everything is in the setup. Again I refer you to the best practices guide. The "pdc" is a fsmo role.

Here is some stuff in a nutshell:
1. both need to be global catalog holders
2. both should be dns servers
3. both should be backed up including system state regularly

After the basics you need to consider engaging the FRS [file replication service] to replicate user files between servers. Consider DFS [directory file services] so you can point to an alias for all shares despite where they are located. You should understand how to seize the FSMO roles if the main holder goes down and won't be back up.

Will you be able to access services/files if one server goes down? You can logon but depending one where those files/shares were located [like on the down server] they may or may not be available.

Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.


0

Response Number 4
Name: Paul B (by pbedorf)
Date: April 10, 2007 at 08:30:08 Pacific
Reply:

Hi and thanks for the reply, to be more detailed on my question this is what I have:

netsrvpdc01 - my primary domain controller running : AD, WINS, DHCP, DNS

netsrvbdc01 - my backup domain controller running : AD, WINS, DHCP, DNS

I am not worrying about users shared folders, profiles etc... because they are stored on a file server and are shared accordingly so that can be found by bdc.

To recap on my above question, the netsrvpdc01 replicates all the AD, DNS properly to the netsrvbdc01 server, both server are backed up on regular basis using ntbackup (back up of system state)

Both server DHCP is set to subnet of 192.168.0.0. So what I did last night, I shut down my pdc01 and automatically bdc01 took over, the only issue was if you had assigned your computers static ip address, you had to edit it and change your default dns server to point to my bdc01 server...

So all worked fine, however can I leave it like that or should I promote it to the true Primary Domain Controller in case of failure of my pdc01? I downloaded a tool called Server Manager, and it has the option to select the bdc01 and set it to primary domain controller by this option is not highlighted so I cannot use it.. any taughts would be appreciated!

Paul B


0

Response Number 5
Name: wanderer
Date: April 10, 2007 at 09:45:35 Pacific
Reply:

*sigh*

There are no bdcs in AD
You are already promoted both to being DC's which explains why its greyed out.
You don't need to download anything for management. You have MMC!
DHCP server should be listing primary and secondary dns servers. This way no wkst edit is required if one server goes down.

You REALLY need to get a 2003 server book and review it. You are missing basic concepts that without you will never be able to properly configure or maintain your network.

Best of luck in your endeavors.

Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.


0

Related Posts

See More



Response Number 6
Name: Glen
Date: April 11, 2007 at 09:59:41 Pacific
Reply:

Paul,

Wanderer has offered you all the help you need. You are your own worst enemy on this. You need to get help or at least educate yourself on this. As wanderer said - there are no primary domain controller or backup domain controllers. All domain controllers are equal (with the exception of the FSMO roles which is beyond this discussion right now). If one fails the other will work as long as AD and DNS are configured correctly.

You need to get familiar with these concepts or you'll be chasing your tail forever.

Good luck.


0

Response Number 7
Name: Paul B (by pbedorf)
Date: April 11, 2007 at 10:04:03 Pacific
Reply:

Thanks all, i got all set up and working properly now. Thank you again.

Paul B


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Backup Domain Controller

Creating Backup domain controller www.computing.net/answers/windows-2003/creating-backup-domain-controller-/4618.html

Domain Controller Reboot www.computing.net/answers/windows-2003/domain-controller-reboot/8252.html

Clustering Primary Domain Controlle www.computing.net/answers/windows-2003/clustering-primary-domain-controlle/6339.html