Server 2003 clustering DHCP?

[tosca925]

I have been reading about DHCP redundancy and in particular DHCP clustering. I think for our own situation it’s a bit of an over kill and either 80/20 rule or the standby DHCP option is better for us. But after reading more on clustering (not just DHCP but SQL etc) I need some one to clarify a few things for me.

 

Now I have very little knowledge of this and have never set it up, but I understand the principle behind it. I know you have the two servers that have on IP on front of them and I also know you use a second card in each that acts as a heart beat between the two. I also read that the data has to be help on a separate drive to provide the redundancy.

 

But what happens if the server/drive holding the data goes down? What happens to the cluster then?

 

How do you back this cluster scenario up?

 

Sorry if these questions are a little basic but I know next to nothing on hits like I said.

[Geoff]

DHCP Lease information is stored in Active Directory. So assuming replication is working between the servers that are in the Cluster, they will all have accurate and up to date information on client DHCP leases.

 

Backing up the 'system state' is sufficient.

[sthe]

Check this site:

http://www.c64gg.com/dhcp-redundancy/

[Rozzer]

Cluster of DHCP has worked great here