Why Cannot Storage Devices Be Discovered on Hosts When I Execute a Recovery Plan to Implement Tests, Planned Migration, or Fault Recovery

18

1.Check whether the LUNs mapped to the hosts are normal.

If no, troubleshoot the LUNs and go to 3.
If yes, go to 2.

2.Check whether the service network communication between hosts and storage devices is normal.

If no, troubleshoot the service network and go to 3.
If yes, contact Huawei technical support engineers.

3.Clear the recovery plan and perform a test again.

Other related questions:
Introduction to recovery plan tests executed by the OceanStor ReplicationDirector
You can test a recovery plan to verify the availability of the data replicated to the disaster recovery site. During a test, the disaster recovery site generates test data using snapshots, which does not have any impact on the production site. After the test is complete, the test environment must be cleaned up. Before a failover or planned migration, at least one recovery plan test must be executed successfully. The test can be performed only in the disaster recovery management system at the disaster recovery site.

Differences between fault recovery and planned migration of OceanStor ReplicationDirector
If data or applications at a production site need to be recovered from a disaster recovery site, you need to perform planned migration at the disaster recovery site. The latest data changes at the production site will be synchronized to the disaster recovery site. Planned migration is performed only in the disaster recovery management system at the disaster recovery site. If data or applications at the production site become unavailable due to disasters or faults, you need to perform fault recovery. Fault recovery is performed only in the disaster recovery management system at the disaster recovery site. The latest backup data at the disaster recovery site is used to recover data.

In Host Replication Scenarios, the DR VRG Has Alarms that Affect VM Recovery, Resulting in Planned Migration or Fault Recovery Failure
1.Log in to DR OceanStor BCManager and choose Monitor > Alarms > Current Alarms. Then view current alarms on OceanStor BCManager. 2.Search for alarms reported by VRGs and related to VMs contained in recovery plans. 3.In the Name area, click the names of alarms. View details about alarms and perform recommended actions to troubleshoot faults. After alarms are cleared, perform planned migration or fault recovery again. If VRG alarms persist, manually confirm and clear alarms without affecting services. Then perform planned migration or fault recovery again.

Message Failed Is Displayed in the Back up application data or Delete application data backup Step and No Execution Detail Is Displayed When Planned Migration or Fault Recovery Is Executed
The failure in the Back up application data or Delete application data backup step does not affect disaster recovery services. The execution result can be ignored.

What Can I Do If Protected Groups and Recovery Plans Cannot Be Deleted at the Production End When the Disaster Recovery End Encounters an Irrecoverable Fault?
1.Check whether backup data exists at the disaster recovery end. If yes, go to 2. If no, go to 3. 2.Backup data exists at the disaster recovery end. Reinstall the OceanStor BCManager at the disaster recovery end. For details, see Installing OceanStor BCManager Server. Import the backup data to the disaster recovery end to restore its data. For details, see Importing Backup Data. NOTE: After performing this operation, you do not need to delete the data and reconfigure the disaster recovery environment at the production site if the disaster recovery end recovers. 3.Backup data does not exist at the disaster recovery end. a.Reinstall the OceanStor BCManager at the disaster recovery end. For details, see Installing OceanStor BCManager Server. NOTE: When the OceanStor BCManager is installed, the management IP address and admin password of the OceanStor BCManager must be the same as those of the OceanStor BCManager at the disaster recovery end before the fault occurs. b.After the OceanStor BCManager is installed successfully, wait about 5 to 10 minutes. After the OceanStor BCManager Server starts, log in to the OceanStor BCManager at the disaster recovery end. If the login succeeds, the OceanStor BCManager is installed successfully at the disaster recovery end. c.On the OceanStor BCManager at the production end, delete the recovery plans, protected groups, resource mappings, and sites related to the OceanStor BCManager at the disaster recovery end before the fault occurs. d.On the OceanStor BCManager at the disaster recovery end, re-perform operations in Creating a Site and Adding Resources. e.On the OceanStor BCManager at both the production end and disaster recovery end, add the local management server of each other as remote management server. f.On the OceanStor BCManager at the production end, perform operations in Creating a Resource Mapping and Creating a Recovery Plan.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top