No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionCloud 6.3.1.1 Troubleshooting Guide 03

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Restore

Restore

VMware VM Fails to Boot After Restore

Symptom

When a VMware VM is restored and attempts to boot, the system displays Operating system not found.

Possible Causes

SCSI and IDE driver modes are available when a VMware is backed up. The operating system is on the SCSI driver, whereas the VM boots from the IDE driver, causing the boot failure.

Fault Diagnosis

Set the VMware VM to boot from the SCSI driver.

Procedure
  1. Go to the BIOS setting page of the VMware VM.

    • Obtain the administrator permission to perform operations on the VMware VM.
    • When the VM is booting, press Delete to go to the BIOS setting page. (The following example shows the BIOS configuration. The steps change in actual operation.)

  2. On the menu bar, choose Boot > Hard Drive.

    Figure 17-1 Initial boot options

  3. On the Hard Drive page, set the SCSI driver as the first boot option.
  4. Save the settings and exit BIOS setting page. Select Continue to reboot the VM.

Restoring a VMware VM Disk Fails Several Times

Symptom

A VMware VM disk cannot be restored after several attempts.

Possible Causes

The disk restoration fails due to a network fault. The attribute of the disk in the VMware production environment is abnormal. The disk cannot be restored after retries.

Fault Diagnosis

Check whether the attribute of the disk in the VMware production environment is normal. For example, if the disk capacity is 0, the disk attribute is abnormal.

Procedure
  1. Log in to the VMware production environment.
  2. Find the VM where the disk that fails to be restored resides.
  3. Configure the VM hardware and delete the disk whose attribute is abnormal.
  4. Restore the disk again.

After a Restore Job Is Successfully Executed, Restored Non-system Disks Are Not Displayed on the Virtual Machine Running Windows 7

Symptom

After a restore job is successfully executed, restored non-system disks are not displayed on the virtual machine running windows 7.

Possible Causes

Restricted by Windows 7.

Procedure
  1. On the desktop of the Windows 7 operating system, right-click the Computer icon.
  2. Choose Manage from the shortcut menu.

    The Computer Management window is displayed.

  3. In the left navigation tree, choose Storage > Disk Management.

  4. Right-click a restored disk and choose Online from the shortcut menu.

    NOTE:

    A disk in the Offline state is a restored disk.

    In the Disk Management area, the restored disks are displayed.

Linux VM Network Adapters Are in Disorder When Data Is Restored From a VM Or System Disks to a New VM

Symptom

After data is restored from a FusionSphere virtual machine (VM) or system disks to a new VM, Linux VM network adapters are in disorder.

Possible Causes

The configuration information for network adapters conflict in the Linux operating system.

NOTE:

When data is restored from a FusionSphere VM or system disks to a new VM, the IP address and domain name on system disks are not modified. Instead, they are to be modified by the customer.

The following uses the eth0 and eth1 network adapters as an example:

Procedure
  1. Log in to a VM using VNC. Run the following command to delete a rule file whose name contains persistent and net from the network rule directory.

    rm /etc/udev/rules.d/XX-persistent-net.rules //XX varies with environments

  2. Run the following command to restart the VM.

    reboot

  3. Log in to the VM again using VNC and run the following command to view network configuration of the VM.

    ifconfig -a

  4. Check whether the network adapter names in the network configuration information are the same as the original ones.

    • If yes, no further action is required. The network adapter names in the following example are eth0 and eth1.
    • If no, go to 5.

  5. Run the following command to use the VI editor to open the rule file whose name contains persistent and net in the network directory.

    vi /etc/udev/rules.d/XX-persistent-net.rules //XX varies with environments

  6. Press i to enter the editing mode.
  7. In the XX-persistent-net.rules file, change the disordered network adapter names to eth0 and eth1 respectively.

  8. Press Esc, enter :wq, save the modification, and exit the VI editor.
  9. Run the following command to restart the VM.

    reboot

V3 Backup or Restore Resource Cannot Be Deleted and Its Data Needs to Be Deleted On V3 Device

Symptom

After an OceanStor V3 protected environment is deleted, you need to clear information about mappings created by using eBackup on the OceanStor V3 storage device.

Possible Causes

Communication between the eBackup and storage device is abnormal.

Procedure
  1. Use PuTTY to log in to the backup proxy using the IP address corresponding to the datamover_externalom_iplist field.

    Default account: hcp. Default password: PXU9@ctuNov17!.

  2. Run the su root command and enter the password of account root to switch to user root.

    The default password of the root account is Cloud12#$.

  3. Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.

    NOTE:

    After you run this command, the system continues to run when no operation is performed, posing a risk. For security purposes, you are advised to run the exit command to exit the system after completing your operations.

  4. Run the cat /etc/iscsi/initiatorname.iscsi command to obtain the name of the initiator on the backup proxy.

    In this example, InitiatorName=iqn.1996-04.de.suse:01:aa2ce58ebf57 in the command output is the initiator name.

    linux-QYuJkX:/opt/huawei-data-protection/ebackup/logs #cat /etc/iscsi/initiatorname.iscsi 
    ## 
    ## /etc/iscsi/iscsi.initiatorname 
    ## 
    ## Default iSCSI Initiatorname 
    ## 
    ## DO NOT EDIT OR REMOVE THIS FILE! 
    ## If you remove this file,the iSCSI daemon will not start. 
    ## If you change the InitiatorName,existing access control lists may reject this initiator. The InitiatorName must be unique for each iSCSI initiator. Do NOT duplicate iSCSI InitiatorNames. 
    InitiatorName=iqn.1996-04.de.suse:01:aa2ce58ebf57

  5. Log in to OceanStor DeviceManager using a browser.

    Login address: https://IP address of the storage system management network port: 8088

    Default account: admin, default password: Admin@storage

  6. Choose Huawei.Storage > Provisioning > Host. On the Host tab page, click each host in sequence to find the host containing the preceding initiator name.

  7. Choose Huawei.Storage > Provisioning > Host Group. On the Host Group tab page, click each host group to find the host group where the host obtained in the preceding step resides.

  8. Choose Huawei.Storage > Provisioning > Mapping View. Click each mapping view and Host Group under the mapping view to find the mapping view containing the host group obtained in the preceding step.

  9. Choose Huawei.Storage > Provisioning > Mapping View, find the mapping view obtained in the preceding step, and click LUN Group to obtain the LUN group name.

    Ensure that No data is displayed under the LUN group. If other LUN information is displayed under the LUN group, the LUN group is still in use and cannot be deleted. In this case, you must not perform the following operations.

  10. Delete the mapping view.

    1. Choose Huawei.Storage > Provisioning > Mapping View.
    2. Select the mapping view obtained in 8, and click Delete. In the dialog box that is displayed, click OK.

  11. Delete the host group.

    1. Choose Huawei.Storage > Provisioning > Host, and click Host Group.
    2. Select the host group obtained in 7, and click Delete. In the dialog box that is displayed, click OK.

  12. Check whether the host can be used by other host groups.

    1. Choose Huawei.Storage > Provisioning > Host, and click Host.
    2. Select the host obtained in 6, and click Properties.
    3. In the dialog box that is displayed, click Owning Host Group. If No data is displayed, host group information does not exist. Go to 13. If host group information is displayed, the host is used by other host groups and cannot be deleted. In this case, you must not perform the following operations.

  13. Deletes the host.

    1. Choose Huawei.Storage > Provisioning > Host, and click Host.
    2. Select the host obtained in 6, and click Delete. In the dialog box that is displayed, click OK.

  14. Delete the LUN group.

    1. Choose Huawei.Storage > Provisioning > LUN, and click LUN Group.
    2. Select the LUN group obtained in 9, and click Delete. In the dialog box that is displayed, click OK.

Translation
Download
Updated: 2019-08-16

Document ID: EDOC1100063248

Views: 25290

Downloads: 41

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next