Skip to main content

VM Restore Failing at 92% – Commvault v11.32.76


Forum|alt.badge.img+1

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 and NBD 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?

Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19

The first thing I recommend is updating to the latest maintenance release, as the version you're currently running was released in early December hence you are missing 400+ fixes. !--startfragment>


Forum|alt.badge.img+1
  • Bit
  • April 28, 2025

Hi ​@Onno van den Berg 

This is a homologation environment, we imported the catalog in this version, would there be a problem if we updated it?


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings