S Khan
asked on
Backup DHCP Server
Hi Guys,
Currently, I have one server room, we are going to install a second server room at the back of a large building. The main reason for this is, in the event of a fire, we will have a copy of the sql server so we can resume business. all the office pc (2 dozen) will be physically uplugged from the primary network into secondary network.
Since the two database servers will be connected via fiber optics approx 300 feet away, should 1 use a failover DHCP or a seperate DHCP?
You're help is greatly appreciated.
Currently, I have one server room, we are going to install a second server room at the back of a large building. The main reason for this is, in the event of a fire, we will have a copy of the sql server so we can resume business. all the office pc (2 dozen) will be physically uplugged from the primary network into secondary network.
Since the two database servers will be connected via fiber optics approx 300 feet away, should 1 use a failover DHCP or a seperate DHCP?
You're help is greatly appreciated.
Lee W, MVP
If it's on the same network, use a split scope - half your DHCP addresses are handed out by each server. If one does down, the other can handle all of the network. Otherwise, whichever DHCP server answers first provides the address
ASKER
Hi Lee, in the event of a fire all the cables will be burnt, so the office pc's will be severed, so i will be running a separate network. my main focus is to have a backup of the entire database. I would have to physically connect the office pc to the backup DHCP server.
Do i replicate the DHCP or have a seperate one?
Here is the flow of the primary room
WAN>SonicWALL>DHCP>SQL
Here is the flow of the backup room
Backup WAN > SonicWALL>DHCP>SQL etc.
Do i replicate the DHCP or have a seperate one?
Here is the flow of the primary room
WAN>SonicWALL>DHCP>SQL
Here is the flow of the backup room
Backup WAN > SonicWALL>DHCP>SQL etc.
I'm confused - WHY would you run a separate network? Just have redundant services in two locations - or use Hyper-V replica. Ditch the sonicwall and use a VM based solution (I prefer Untangle, but PFSense and other third party systems exist that can run as a VM - and since they are running as a VM you can fail them over.
I would not use a second DHCP server. When a Windows machine boots, with an existing DHCP lease it attempts to ping the default gateway, and if it can, keeps using that lease. The default Windows DHCP lease is 8 days, leases are renewed once half expired, so clients will be fine with no DHCP server for 4 days. You could even extend the lease time, maybe to 30 days, giving you 2 weeks grace.
Longer leases can be a problem f you have a lot of devices intermittently in use and not a lot of spare IP addresses. If for instance, a visitor plugs in a laptop, and it gets a lease, that IP cannot be used for 8 days. It is possible to therefore run out of IP addresses.
Longer leases can be a problem f you have a lot of devices intermittently in use and not a lot of spare IP addresses. If for instance, a visitor plugs in a laptop, and it gets a lease, that IP cannot be used for 8 days. It is possible to therefore run out of IP addresses.
ASKER
In a fire we will loose the entire room, WAN, SonicWALL, Switches. firewall etc, The only thing that remain is a burn out Ethernet cable.
We are planning for worst case scenario.
We are planning for worst case scenario.
ASKER
also the backup DHCP will be using another gateway.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Actually you're right, same network, different location with a separate WAN.
All the machines are virtual, Thank you for the guidance.
All the machines are virtual, Thank you for the guidance.