Hi everyone,
I'm facing a recurring issue when restoring a virtual machine (VMware) using Commvault version 11.32.76. The restore consistently fails at the same point, regardless of different configurations and attempts.
π οΈ Environment Overview
-
Restore type: Full Virtual Machine Restore
-
Transport modes tested:
NBD
andNBD SSL
-
MediaAgent: properly installed, communicates with vCenter and ESXi
-
Destination datastore: accessible and has sufficient free space
-
VM progress: restore completes up to 92% (~84 GB of ~91 GB total)
-
Permissions & services: confirmed running correctly
β Error Behavior
-
Restore job starts and progresses normally
-
.vmdk
files are successfully created and opened in the target datastore -
Failure occurs at the final phase, with the status:
RestoreVMData failed
yet no specific write/read/seek errors are logged
Relevant log snippet (vsrst.log
)
RestoreVMData failed. CloseArchiveRet: [0] Seek Error [0] Write Error [0] Read Error [0] Browse Error [0] Restored 80266 of 86563 extents (92%) writedisk: Bytes [84165001216], Speed [4.59 MB/s] LookupEntity - .vmdk not found! Marking VM as pending Sending FAILED complete message to JM
Already tested
-
Reduced number of streams to 4
-
Changed destination VM name (to avoid object conflicts)
-
Tried different target datastores
-
Restarted Commvault services
-
Network and port connectivity (443 & 902): tested OK
-
Installed required packages: File System Core, Virtual Server, MediaAgent
-
File-Level Restore (FLR) tested and working correctly
βLooking for guidance on:
-
Is this a known SDT or pipeline timeout issue?
-
Could this be fixed by using
HotAdd
transport mode? (not tested yet due to infra constraints) -
Any advanced settings or workarounds to force a successful commit?