Loading...
Loading...
The NVP integration uses a vProxy appliance to perform file-level restores. An FLR mount operation fails while adding VMDK files to the target VM. The vProxy FLR mount session log shows the "Another task is already in progress" error during the VMDK add operation: YYYY-MM-DD HH:MM:SS INFO: Adding VMDKs to VM '[VM_NAME]' (vm-###) YYYY-MM-DD HH:MM:SS ERROR: AddDevice failed for '[EMC-FLR-[VPROXY_NAME]-[SESSION_ID]] vm-###-disk-key-2006.vmdk': Another task is already in progress. YYYY-MM-DD HH:MM:SS INFO: Unmounting after mount failure: Unable to add VMDKs to VM '[VM_NAME]' (vm-###): AddDevice failed: Another task is already in progress. The FLR cleanup process also fails as the vProxy cannot remove the partially mounted VMDK files because the concurrent task is still active: YYYY-MM-DD HH:MM:SS INFO: Removing VMDKs from VM '[VM_NAME]' (vm-###) YYYY-MM-DD HH:MM:SS ERROR: Unable to remove VMDK '[EMC-FLR-[VPROXY_NAME]-[SESSION_ID]] vm-###-disk-key-2001.vmdk' from VM '[VM_NAME]' (vm-###): Another task is already in progress. The temporary FLR datastore cannot be removed because it is still in use: YYYY-MM-DD HH:MM:SS ERROR: Unable to remove datastore 'EMC-FLR-[VPROXY_NAME]-[SESSION_ID]': ServerFaultCode: The resource 'EMC-FLR-[VPROXY_NAME]-[SESSION_ID]' is in use. After the failed FLR, orphaned VMDK files from the FLR session may remain attached to the target VM. These orphaned disks can prevent the VM from starting properly upon reboot. The administrator may be unable to manually remove the orphaned VMDK files using the vSphere Web Client because the concurrent task from the other protection product continues to block the operation. The target VM is also protected by vSphere Replication Manager or another backup/replication product. This issue can apply to all NetWorker and vProxy versions.
The target virtual machine is protected by both the NetWorker VMware Protection (NVP) vProxy solution and another protection product (such as vSphere Replication Manager). When the FLR mount operation attempts to add VMDK files to the target VM, vSphere rejects the operation with "Another task is already in progress" because the other protection product holds an active task on the VM. The vSphere API enforces a single-task lock on VM reconfiguration operations. When two products attempt to modify the VM configuration simultaneously (for example, adding/removing disks), the second operation fails. In this case: The FLR mount fails because the VMDK add operation is blocked by the concurrent task. The FLR cleanup fails because the VMDK removal is also blocked by the same concurrent task. The FLR datastore removal fails because the orphaned VMDKs are still attached to the VM. The orphaned VMDK files remain attached to the VM, potentially preventing the VM from booting correctly. Protecting a VM with multiple backup or replication products creates a conflict where concurrent operations interfere with each other. This is not a NetWorker or vProxy defect — it is a configuration conflict between competing protection products on the same VM.
Identify the Conflicting Protection Product In the vSphere Web Client, navigate to the affected VM and check Monitor → Tasks to identify which product or process holds the concurrent task on the VM. Review the environment to determine which backup or replication products protect the affected VM. In the documented case, vSphere Replication Manager was the conflicting product. Evaluate the Protection Strategy Evaluate the environment and determine the best way to protect the VM. Each VM should be protected by only one backup or replication product to avoid concurrent task conflicts on the VM. Remove the VM from either the NetWorker vProxy protection policy or the conflicting backup/replication product based on the organization's data protection requirements. Audit the Environment Review all VMs in the environment to identify any other virtual machines that are simultaneously protected by NetWorker vProxy and another backup or replication product. Remove the dual protection to prevent the same issue from occurring on other VMs. If assistance is needed identifying the conflicting product or determining the appropriate protection strategy, contact Dell Support for further investigation and reference this KB article.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.