What Can I Do If the Disaster Recovery Site VM Is Not Started After a Switchover?
Possible Cause
BRS asynchronous replication supports crash consistency. During a switchover, data in the memory may be lost, so the disaster recovery site VM may need to use the crash recovery capability of the application or file system to restore data. In most cases, the restored data is consistent and can be normally used.
Solution
Example: After a switchover, the disaster recovery site VM failed to be started. An XFS exception occurred (LSN verification failed), and the OS entered the emergency mode.
Solution: Run journalctl to check that the fault is caused by an XFS file system error. Enter the emergency mode of the OS and run xfs_repair to rectify the fault.
An operation example is provided as follows:
- Check the root file system, for example rhel-root, in the /dev/mapper directory.
xfs_repair /dev/mapper/rhel-root
If an error is reported, check the error cause or run the following command:
xfs_repair –L /dev/mapper/rhel-root
Information similar to the following is displayed.
- Check whether the repair is successful. Run the following command:
mount /dev/mapper/rhel-root /
If the mount is successful, the file system has been repaired.
- Restart the OS.
Run reboot. After the reboot, the VM OS can be accessed.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot