Experience with DHCP server management maintenance

The author also encountered some trouble in the management of DHCP server. Although through the author of some efforts, the ultimate solution. However, when you think of a problem with a DHCP server, you still feel very nervous. Today, the author of my own in the management of the DHCP server to do some simple summary of the problems encountered. Perhaps these topics have been met, we will discuss together to see if there is a better solution.

DHCP Server Management Maintenance tips: How to back up a DHCP server configuration

Network administrator often wants to be able to back up the DHCP server's related configuration. Wait until the next time the server fails, you can use this backup file for rapid recovery, without any more manual configuration of the DHCP server. If there are some MAC addresses in the DHCP server, then reconfiguring is a lot of work. Moreover, the DHCP server is also a more complex governance system, if due to the configuration of the omission, resulting in the failure of the DHCP server, if there is a backup file, you can use it to quickly restore the original configuration. Therefore, after the relevant configuration adjustment, even if the DHCP server configuration for the related backup, it is a good work habits.

If the DHCP server is a stand-alone server, then it is good to do. Simply backup the entire control system, including the DHCP server configuration. However, often very few enterprises will use a stand-alone server to run the DHCP service, it seems too wasteful. As a result, most enterprise DHCP services apply to a single server with other application services. In this case, if the backup control system, then the workload will be very large. Moreover, the subsequent restoration will also encounter trouble. When you restore a DHCP server, other application servers are restored as well. Obviously, this is not what we would like to see. Therefore, this method is not feasible for a DHCP server that is not independent.

In addition, we simply export the configuration of the DHCP server and do not back up the information that manipulates the system or other application services. such as the author of the enterprise DHCP server, is based on Microsoft's 2003 above. This feature is not in the DHCP Server Manager window. However, it provides a command that allows you to export the server's configuration and import it into a TXT file. If we can take advantage of this command: netsh dhcp server export e:\dhcp.txt all. The server's configuration file is exported to the root directory of e disk, whose file name is Dchp.txt. If the next time the server fails, we can use the command to recover. The command format is as follows: netsh dhcp server import e:\dhcp.txt all.

Finally, it is necessary to make two recommendations to the network administrator.

First, in the governance of the DHCP server, if you need to adjust the relevant configuration, then when the test finished without errors, to timely the current configuration export, for backup. Only in this way, the next time there is a failure, can calmly cope with.

The second is to not only make a local backup, but also need offsite backup. This is mainly to prevent the next time the DHCP server hardware failure, such as disk errors, can be timely for off-site recovery.