I want to take a backup of my DHCP server & it's scope.
Can I set schedule task? if yes how to do it?
Step-by-step process
The following steps define the process required in order to make sure that the standby server can take
over the provision of DHCP services by starting the service:
On the live server, create a copy of the DHCPServer Registry hive (using Regdmp).
Copy this file to the standby server.
Duplicate the DHCP backup directory from the live server onto the same point on the standby server
(using Robocopy).
On the standby server, copy the files in the {backup}\jet\new directory to the %winroot%\system32
\dhcp directory.
On the standby server, import the Registry hive into the Registry (using Regini).
It’s possible for a bad network connection, a busy server, or heavy network traffic to slow down the
process of copying the DHCP backup directory between servers. It could result in one of the files being
open when the DHCP service on the live server starts the backup process. To guard against this, you can
add these steps:
On the live server, create a copy of the DHCPServer Registry hive (using Regdmp).
Copy this file to the standby server.
Copy the DHCP backup directory from the live server into another directory on the live server (using
Robocopy).
Duplicate this backup directory from the live server into a directory on the standby server.
On the standby server, copy the directory structure in this backup directory to the DHCP backup
directory.
On the standby server, copy the files in the {backup}\jet\new directory to the %winroot%\system32
\dhcp directory.
On the standby server, import the Registry hive into the Registry (using Regini).
You can build a batch file to carry out these steps, and at the click of a button (metaphorically speaking), you will have a server that’s ready to take over the provision of the DHCP service if the live DHCP server fails. However, to ensure that your standby server is current, you’ll need to run your batch file every time the DHCP service backup finishes.One other step needs to be considered. When the standby server takes over the provision of DHCP services, client PCs with DHCP leases that subsequently expire will attempt to renew automatically from the DHCP server that originally provided the lease. These attempts will fail because that server (identified by its IP address) will not respond. However, on the new live server, the DHCP service will release that IP address, and it will become available for use by any other client requesting an address. Should that IP address be reissued, an IP conflict will occur.Therefore, you may decide that any fail-over should include this final step: swapping names and IP addresses so that the live DHCP server always has the same name and IP address. However, keep in mind that it’s only a potential problem and will occur only if the client PC is not rebooted and the user does not log off between the fail-over and the expiration of the lease. Any such issue can be resolved quickly by using Winipcfg (on Windows 9x) or Ipconfig (on Windows NT) to force a release and
renewal of the client’s IP address.
0 comments:
Post a Comment