vSphere replication appliance shows not accessible on the vCenter Server

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• vSphere replication appliance shows not accessible. 

• The Site Recovery Manager page shows the vSphere Replication status as not connected under Remote VR connection tab as shown below:

• No IP address showing for the vSphere Replication VM under the VM summary page.

Environment

vSphere Replication 8.x

vSphere Replication 9.x

Cause

• This issue occurs can when the vSphere Replication appliance's Virtual Machine has problems booting up. The VR VM when in a panic mode can cause issues booting up.
• The VM console screen will show message like 'could not boot'.

[201.153349] dracut-initqueue[382]: Warning: dracut-initqueue timeout - starting timeout scripts
[201.153349] dracut-initqueue[382]: Warning: dracut-initqueue timeout - starting timeout scripts
[201.155183] dracut-initqueue[382]: Warning: Could not boot.
Warning: /dev/disk/by-partuuid/edccc080-5571-447a-a92c- does not exist

Generating "/run/initramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.

Give root password for maintenance
(or press Control-D to continue):

• The VM file system can go bad when the virtual appliance experiences file inconsistencies after being forcefully halted as the result of a storage failure, power failure, or other crash.

Resolution

Fix the file system issue by referring and following the steps mentioned in the kb article, "[FAILED] Failed to start File System Check on /dev/vg_root_0/lv_root0" error on Photon OS based virtual appliances.

If following above KB does not resolve the issue, kindly request the customer to restore the vSphere Replication VM from backup and then reconfigure the appliances.