Loading...
Loading...
Following the upgrade to PowerProtect version 19.22.0.16, the environment exhibits the following behavior: The backup system cannot complete a file‑level restore (FLR) of Linux virtual machines. The operation stops with error code ARV0032 . FLR job reports: "VM Direct engine is unable to restore the virtual machine '[VM‑NAME]' on vCenter '[VCENTER‑NAME]' because the mount of the virtual machine's virtual disks was unsuccessful."The issue occurs only when the PowerProtect Data Manager (PowerProtect Data Manager) server cannot reach the Data Domain (DD) data network (for example, segregated backup network that is not routable from PowerProtect Data Manager).All Linux VM FLR attempts fail under the described network condition. Log Evidence vmdm.log: 2026-02-23T08:59:20.794Z INFO [] [vproxyMonitor] [][][][TRACE_ID:ba501410177f9715;JOB_ID:a4cbe15a7b50b70e][] [c.e.b.v.r.s.VmdmMountService.statusChanged(261)] - MOUNT-MONITOR: VmdkMountSession(state=Failure, id=6c4a0e44-db78-4a45-a769-bf00d26dc9d0, error: code=0, text=Unable to mount disks.Cannot mount '10.10.10.10:/data/col1/1-ppdmserver-81ce6/vProxy-hostname.lab.domain.com-6c4a0e44-db78-4a45-a769-bf00d26dc9d0' at '/opt/emc/vproxy/runtime/state/flr/temp/nfs-6c4a0e44-db78-4a45-a769-bf00d26dc9d0': [mount.nfs: Operation not permitted for 10.10.10.10:/data/col1/1-ppdmserver-81ce6/vProxy-hostname.lab.domain.com-6c4a0e44-db78-4a45-a769-bf00d26dc9d0 on /data01/vproxy/vproxyd/runtime/state/flr/temp/nfs-6c4a0e44-db78-4a45-a769-bf00d26dc9d0]: exit status 32). State Mounting -> Failure. Progress 100%
Incorrect NFS host selection for internal mount In the 19.22 release the NFS host selection logic used by the vproxyd process was changed. The internal mount of the backup copy now uses the Data Interface IP address of the Data Domain (DD) instead of the Management Interface IP address. The PowerProtect Data Manager server resides on a backup network that cannot reach the DD Data Interface.During a Linux VM file‑level restore (FLR), vproxyd attempts to mount the backup copy over NFS using the unreachable Data Interface IP.The mount fails, generating error code ARV0032 and the message "Unable to mount disks… Operation not permitted.” Resulting failure The failed NFS mount prevents the UUID‑collision cleanup step, so the VM Direct engine cannot attach the virtual disks to the target VM, causing the FLR job to stop. Relevant log excerpt vmdm.log: 2026-02-23T08:59:20.794Z INFO [] [vproxyMonitor] [][][][TRACE_ID:ba501410177f9715;JOB_ID:a4cbe15a7b50b70e][] [c.e.b.v.r.s.VmdmMountService.statusChanged(261)] - MOUNT-MONITOR: VmdkMountSession(state=Failure, id=6c4a0e44-db78-4a45-a769-bf00d26dc9d0, error: code=0, text=Unable to mount disks. Cannot mount '10.10.10.10:/data/col1/1-ppdmserver-81ce6/vProxy-hostname.lab.domain.com-6c4a0e44-db78-4a45-a769-bf00d26dc9d0' at '/opt/emc/vproxy/runtime/state/flr/temp/nfs-6c4a0e44-db78-4a45-a769-bf00d26dc9d0': [mount.nfs: Operation not permitted for 10.10.10.10:/data/col1/1-ppdmserver-81ce6/vProxy-hostname.lab.domain.com-6c4a0e44-db78-4a45-a769-bf00d26dc9d0 on /data01/vproxy/vproxyd/runtime/state/flr/temp/nfs-6c4a0e44-db78-4a45-a769-bf00d26dc9d0]: exit status 32). State Mounting -> Failure. Progress 100%
Upgrade PowerProtect Data Manager to Fixed Release (Version 20.1) Applying the 20.1 update resolves error ARV0032 that prevents file‑level recovery (FLR) of Linux VMware VMs when the DD data network is not reachable from the PowerProtect Data Manager server. Back up the current PowerProtect Data Manager configuration and database.Download the 20.1 update package from the Dell Technologies support portal.Transfer the package to the PowerProtect Data Manager server (for example, /opt/emc/ppdm/updates ).Run the update installer. # Example commands on the PowerProtect Data Manager server cd /opt/emc/ppdm/updates sudo ./install_ppdm_20.1.sh # Verify the installer completed successfully [2026-02-23 10:15:42] INFO Update to version 20.1 completed. Reboot the PowerProtect Data Manager appliance if the installer prompts for a restart.Log in to the PowerProtect Data Manager UI and confirm that the version shows 20.1 under System → About. Post‑upgrade Validation Perform a test FLR on a Linux VM backup to ensure that the issue is resolved. # Initiate a file‑level restore from the PPDM UI or CLI ppdm restore --job-id 12345 --type FLR --vm-name test-linux-vm # Expected log entry (no ARV0032) [2026-02-23 11:02:07] INFO FLR completed successfully for VM test-linux-vm If the restore finishes without the "mount of the virtual machine's virtual disks was unsuccessful" message, the problem is resolved. Caution: Upgrading PowerProtect Data Manager may require a short service interruption. Schedule the upgrade during a maintenance window and ensure that all running backup jobs are completed or paused. Warning: Do not modify the NFS host selection logic manually. Incorrect changes can cause further mount failures and data loss. Workaround: Use Instant Access Restore. If upgrading to 20.1 is not immediately possible, recover files using an Instant Access (IA) restore of the same VM backup. From the PPDM UI, select the wanted backup and choose Instant Access Restore .Configure the IA VM to use a unique IP address that does not conflict with the production VM.Power on the IA VM and log in to its operating system.Copy the required files or folders to a location accessible from the production environment (for example, an NFS share or SCP to a management workstation).After copying, shut down and delete the IA VM to free resources. Note: The IA VM runs a temporary copy of the backup; any changes made inside the IA VM are not reflected in the production VM. Verification of Workaround Confirm that the needed files are present and intact on the target system. # Example verification on the target host $ ls -l /mnt/recovered/files/ -rw-r--r-- 1 root root 1048576 Feb 23 12:30 important_config.cfg Caution: Ensure that the IA VM’s IP address does not overlap with any existing VM to avoid network conflicts. Warning: This workaround does not provide a true FLR; it only allows file extraction. For full FLR functionality, upgrade to version 20.1 when feasible. Caution: Contact Dell Support (reference Jira PDM09G-2116) if the upgrade fails or the workaround does not meet recovery requirements.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.