Backup by DHCP usually completes within a very short period (several seconds). Please consider the following action:
- If possible, set up a retry of backup by backup software.
- Change the trigger of backup by the backup software.
- Lengthen the interval of the regular backup and cleanup by DHCP.
* Backup is also performed during the cleanup process by DHCP.
* Lengthening the interval of the regular backup and cleanup by DHCP can decrease the occurrence of this symptom.
* The interval of the regular backup and timing of the cleanup by DHCP are determined by adding the following registry value at the start time of the DHCP Server service.
The interval of the backup by DHCP can be changed by editing the following registry entry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters\BackupInterval
* The default value is 60 minutes.
* The maximum value is 71582 minutes.
The interval of the cleanup by DHCP can be changed by editing the following registry entry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DhcpServer\Parameters\DatabaseCleanupInterval
* The default value is 60 minutes.
* The maximum value is 71582 minutes.
* The cleanup process by DHCP is performed between 0:00:00 and 0:01:00 in addition to the regular cleanup. Therefore, do not set up any backup schedule during this time period.
In addition to the above-mentioned non-regular timing, cleanup is performed when a new lease request is received while allocatable IP addresses are exhausted. This timing cannot be controlled by registry or by other means. As a result, if this timing and the backup timing by the backup software which uses Volume Shadow Copy Service is accidentally matched, this symptom occurs.
However, as mentioned above, cleanup is performed between DatabaseCleanupInterval registry and between 0:00:00 and 0:01:00. Therefore, if the environment does not generate such exhaustion other than the timing mentioned above, this symptom will not occur.