BMR Restoration Failure Caused by DHCP-based Allocation of IP Addresses
Publication Date: 2015-07-30Views: 80Downloads: 0
Data on a bare metal restore (BMR) client is successfully backed up. During BMR restoration, the BMR client cannot obtain an IP address allocated using the Dynamic Host Configuration Protocol (DHCP). The BMR restoration fails.
1. Log in to the NetBackup console as user root.
For details, see OceanStor HDP3500E Installation Guide.
2. Enter a dialog box for modifying network interface configurations.
3. Click Remove to delete the original IP address.
4. Click Add. The Add Network Identity dialog box is displayed.
5. Configure an IP address that is on the same network segment as the IP address of the DHCP server for the network interface of the client. Click OK.
Before BMR restoration, the NetBackup adds the IP address of the PXE network interface into /etc/dhcp.conf based on the network interface information.
6. Click OK.
7. Perform BMR restoration again.
For details about BMR restoration, see OceanStor HDP3500E BMR Backup and Recovery Guide.
The IP address requested by the BMR client is not on the same network segment as IP addresses that the DHCP server can allocate.
After restoration preparation, check the network interface information added by the BMR client in the /etc/dhcp.conf directory of the HDP3500E master server, as shown in Figure 1.
Figure 1 dhcp.conf information of the HDP3500E master server
The IP address of the pre-boot execution environment (PXE) network interface is not on the same network segment as that of the DHCP server. As a result, the BMR client cannot obtain the correct IP address and the BMR restoration fails.