DHCP database
I searched around and couldn't find exactly what i was looking for..so i want to ask.
This is really just for informational purposes, not a problem per se.
I have several dhcp reservations and such that i don't want to recreate if i have a failure, as those ip's are entered into firewalls/web filters etc....
What I am thinking is to use robobcopy to backup the dhcp database =C:\windows\system32\dhcp\
If I only have one dhcp server and it completely fails,...and I have a backup of the database, can that be used on a new server with dhcp installed?
My other question is, what's a good/the best way to backup dhcp?
set up a batch file to export with the netsh command on a weekley basis?
Use windows backup?
just wanting some information and opinions....
This is really just for informational purposes, not a problem per se.
I have several dhcp reservations and such that i don't want to recreate if i have a failure, as those ip's are entered into firewalls/web filters etc....
What I am thinking is to use robobcopy to backup the dhcp database =C:\windows\system32\dhcp\
If I only have one dhcp server and it completely fails,...and I have a backup of the database, can that be used on a new server with dhcp installed?
My other question is, what's a good/the best way to backup dhcp?
set up a batch file to export with the netsh command on a weekley basis?
Use windows backup?
just wanting some information and opinions....
ASKER
Thanks arnold.
I have indeed used the netsh dump command from time to time.
Dhcp creates that database backup automatically from what i understand. I would assume it does so for a reason, but i haven't found any real world examples of anyone using it. Just wondered if there was a way to use it for backup.
i will likely just use a batch file to dump it into txt once a week.
What do you think of this? (my imagination at work- lookout!)
Have one authorized DHCP server running-DHCP1
Have one unauthorized DHCP server running-DHCP2
run a batch file to export/dump from DHCP1 to file
run a batch file to import to DHCP2
It all happens automatically on a nightly basis with scheduled tasks.
if DHCP1 dies, just authorize DHCP2 and go about your business.
sound feasible?
I have indeed used the netsh dump command from time to time.
Dhcp creates that database backup automatically from what i understand. I would assume it does so for a reason, but i haven't found any real world examples of anyone using it. Just wondered if there was a way to use it for backup.
i will likely just use a batch file to dump it into txt once a week.
What do you think of this? (my imagination at work- lookout!)
Have one authorized DHCP server running-DHCP1
Have one unauthorized DHCP server running-DHCP2
run a batch file to export/dump from DHCP1 to file
run a batch file to import to DHCP2
It all happens automatically on a nightly basis with scheduled tasks.
if DHCP1 dies, just authorize DHCP2 and go about your business.
sound feasible?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
good advice.
I would definitely limit the export/import to the reservations.
I also use a subnet mask of 255.255.248.0 which gives me a lot of addresses.
so....I could have:
scope 192.168.0.0 on both servers
all reservations on both servers in range of 192.168.2.xxx
DHCP1 leasing out 192.168.0.1 - 192.168.1.254
DHCP2 leasing out 192.168.3.1 - 192.168.4.254
correct?
I would definitely limit the export/import to the reservations.
I also use a subnet mask of 255.255.248.0 which gives me a lot of addresses.
so....I could have:
scope 192.168.0.0 on both servers
all reservations on both servers in range of 192.168.2.xxx
DHCP1 leasing out 192.168.0.1 - 192.168.1.254
DHCP2 leasing out 192.168.3.1 - 192.168.4.254
correct?
In this setup, I think you should look at using super scopes versus a single contigous one.
I.e. are the segments broken up using switches where a dhcp agent can be configured such that each "location" has their own segment. The benefit is to minimize traffic that goes within one segment being seen by all since your scope consists of eight class C networks (254*8 usable IPs)
You could use/configure it in the way you outline. Note 192.168.0.1 is often the router's IP i.e. your allocatable range will be 192.168.0.2-192.168.7.254 based on your netmask.
I.e. are the segments broken up using switches where a dhcp agent can be configured such that each "location" has their own segment. The benefit is to minimize traffic that goes within one segment being seen by all since your scope consists of eight class C networks (254*8 usable IPs)
You could use/configure it in the way you outline. Note 192.168.0.1 is often the router's IP i.e. your allocatable range will be 192.168.0.2-192.168.7.254 based on your netmask.
ASKER
Thanks Arnold..
I think what I'll chose to do is this:
reduce the net mask to 255.255.252.0
on both DHCP servers use 192.168.2.1 - 192.168.2.254 as reservations
DHCP1 will lease 192.168.1.1 - 192.168.1.254
DHCP2 will lease 192.168.3.1 - 192.168.3.254
that should allow plenty of addresses on either server if I have under 200 devices/computers.
I think what I'll chose to do is this:
reduce the net mask to 255.255.252.0
on both DHCP servers use 192.168.2.1 - 192.168.2.254 as reservations
DHCP1 will lease 192.168.1.1 - 192.168.1.254
DHCP2 will lease 192.168.3.1 - 192.168.3.254
that should allow plenty of addresses on either server if I have under 200 devices/computers.
I'm puzzled at your point assignment choice?
using netsh you can preserve the configuration.
My comment about splitting the IP scope such that one DHCP server assigns one section and the other non-overlaping seems to be the solution you are using.
using netsh you can preserve the configuration.
My comment about splitting the IP scope such that one DHCP server assigns one section and the other non-overlaping seems to be the solution you are using.
ASKER
I planned on doing that for quite sometime.
My main question was to see if I could somehow use the backed up DHCP database in case of a server failure.
the other question was just wanting some varied opinions about what others use to back up their database or DHCP config.
I didn't really get an answer about the backed up database question. You did comment about splitting the IP scope....I had planned on doing that anyway.
I'll be happy to award you the points for your participation. I meant nothing by it, just didn't seem to get the main answer I was looking for.
My main question was to see if I could somehow use the backed up DHCP database in case of a server failure.
the other question was just wanting some varied opinions about what others use to back up their database or DHCP config.
I didn't really get an answer about the backed up database question. You did comment about splitting the IP scope....I had planned on doing that anyway.
I'll be happy to award you the points for your participation. I meant nothing by it, just didn't seem to get the main answer I was looking for.
ASKER
Thanks Arnold
IMHO, there is no point of backing up the DHCP database since I think it only contains info on the leased IPs as well as the netsh dhcp is the tool to use.
http://technet.microsoft.com/en-us/library/cc781140%28WS.10%29.aspx
http://support.microsoft.com/kb/325473
http://technet.microsoft.com/en-us/library/cc781140%28WS.10%29.aspx
http://support.microsoft.com/kb/325473
ASKER
I see... thank you.
When I saw that windows makes it's own backup of the database it just made me wonder if it could be used to easily transfer to another server in case of failure.
When I saw that windows makes it's own backup of the database it just made me wonder if it could be used to easily transfer to another server in case of failure.
I think this is what you are looking for versus trying to copy/backup an MDB file which I am not sure what it has nor whether if you drop it into the location and start DHCP will do what you are looking for.
netsh dhcp server dump (for local server)
see options/examples below
http://msdn.microsoft.com/en-us/library/ms175903.aspx