Application-Related
- What Can I Do If UltraVR Nodes Become Faulty
- What Can I Do If Communication Between Centers Becomes Abnormal After I Change the Management IP Address
- What Can I Do If Device Alarms Cannot Be Received After I Change the Management IP Address
- What Can I Do If UltraVR Stops Running Due to an Outage During a Test, Clearing, or Planned Migration or Fault Recovery on UltraVR
- What Can I Do If the Register VM Step Fails When Planned Migration Is Executed and a Message Is Displayed, Stating "LUN that is required by the VM has not been mapped to the host, has become invalid or has not been managed by a consistent group"
- What Can I Do If Protected Groups and Recovery Plans Cannot Be Deleted at the Production Center When the DR Center Encounters an Irrecoverable Fault?
- What Can I Do If the VRG at the DR Site Encounters an Irrecoverable Fault
- What Can I Do When the FusionSphere, VRG, and UltraVR in the Production End Encounter an Irrecoverable Fault?
- What Can I Do If a Planned Migration or Fault Recovery Fails Because Alarms Affecting VM Recovery Exists on VRG at the DR Center in Host-Based Replication Scenarios
- What Can I Do If System Configuration Data Fails to Be Backed Up
- What Can I Do If Alarms or Operation Logs Fail to Be Dumped
- Why the Protected Group Is Still in Invalid State After Its Protected Objects Are All Recovered
- Why the Network Adapter Are Incorrectly Recovered After the Host-Based Replication Test
- What Can I Do If DR Fails to Be Started After I Bind Disks
- What Can I Do If UltraVR Cannot Manage OceanStor 18000 After I Upgrade the SVP of the Array
- The Create DataStore Step Fails to Be Performed and Message If a storage device is used for the first time or its file system cannot be identified, the storage device can be added as a data store only after being formatted. Add the storage device as a data store again and set it to be formatted. After it is formatted, original data on it is erased Is Displayed When the Fault Recovery Step Is Performed
- The Register VM Step Fails to Be Performed and Message Failed to register volumes and LUN that is required by the VM has not been mapped to the host, has become invalid or has not been managed by a consistent group Are Displayed When the Fault Recovery Step Is Performed
- A Message Is Displayed Indicating that the Device or Resource Does Not Exist When DR Operations Failed To Be Performed
- Snapshot Creation Step Fails During A DR Test
- Failed to Perform Planned Migration for the Geo-redundant Star Protected Group. The Error is Described As Follows: The Status of the HyperMetro Pair Does Not Meet the Recovery Requirements.
- Enabling Data Replication Fails During a DR Test
- An Error Is Reported During Clearing After a KVM Test Is Complete
- Protection Is Not Removed from the Unmounted Protected Volume of the VM and Residual Pairs Exist in the Protected Group After Fault Recovery and Reprotection
- RPOs of Non-HyperMetro and Synchronous Replication Protected Groups Cannot Be Displayed
- Failed to Set the Suspension Time
- SFTP Test Under Automatic Backup of the System Configuration Data Page Fails
- Failed to Create or Expand the HA Protected Group Because the VM Has Snapshots
- During Fault Recovery or Planned Migration on a Distributed Synchronous/Asynchronous Replication Network, the "Register VM" Step Fails, and Message "Fusionsphere:The disk already exists." Is Displayed
Copyright © Huawei Technologies Co., Ltd.