VMware backup proxy is in a Disconnected state in Console as Proxy VM is in Maintenance Mode (Emergency Mode) during the boot process. | Druva

Problem description

The VMware backup proxy appears as Disconnected in the Druva Management Console. Upon investigating the virtual machine console via vCenter, the Linux-based proxy is found stuck in Maintenance Mode (also known as Emergency Mode) during the boot sequence.
The system stops at a command prompt asking for the root password or to press Control-D. This prevents the backup services from starting, rendering the proxy unavailable for backup and restore jobs.

This issue is typically caused by stale VMDKs (Virtual Machine Disk files) from protected VMs that remain "HotAdded" or attached to the backup proxy after a failed or interrupted backup job.
When the proxy attempts to boot, the Linux kernel tries to scan or mount these disks. Because these disks are snapshots or belong to other VMs, the proxy encounters file system mismatches or I/O timeouts, causing the boot process to fail and drop into maintenance mode for safety.

To restore connectivity, the stale disks must be manually detached from the backup proxy VM configuration in vCenter.

Steps to unmount/remove a stale VMDK from the backup proxy:

Power off the backup proxy VM from the vSphere client.
Right-click the proxy VM and select Edit Settings.
Review the list of Hard Disks.
- Hard Disk 1 is typically the OS disk (Do not remove).
- Look for additional Hard Disks (Hard Disk 2, 3, etc.) that point to datastore paths of other virtual machines.
Once the stale Hard Disk is identified, click the X mark on the right side of the specific disk row.
CRITICAL NOTE: Ensure the option "Delete files from datastore" is NOT selected. Selecting this will delete the actual data of the VM you are protecting.
Click OK to commit the changes.
Power on the backup proxy VM. It should now boot normally to the login prompt.

Include: This applies to Linux-based Druva Phoenix/SBC proxies using the HotAdd transport mode.
Exclude: This does not apply to Cloud-to-Cloud backups or proxies utilizing only the NBD (Network) transport mode, as disks are not attached to the proxy in those scenarios.

Console Check: Confirm the VM console shows a standard login prompt instead of the Maintenance Mode message.
Druva Console: Log in to the Druva Management Console and navigate to the Manage Proxies page.
Status Update: Ensure the proxy status has refreshed to Connected (this may take 2–5 minutes after the OS boots).
Job Test: Run a manual "Backup Now" task for a VM assigned to this proxy to ensure the disk mounting/unmounting process is functioning.