Rubrik backup job failed "snapshot creation failed for virtual machine" error

TL;DR

Snapshot creation failing for a VM is a hypervisor-side conversation first: check the VM's snapshot state in vSphere, free space on its datastore, and whether a stale snapshot or a locked disk from an earlier job is blocking a new one. Clear the stale snapshot state and confirm the datastore can hold the snapshot delta, then rerun the Rubrik job for that VM alone before the full schedule.

Rubrik backup job failed "snapshot creation failed for virtual machine" error

Use this when

• The job or restore fails with this symptom: Rubrik backup job failed with snapshot creation failed for virtual machine.
• You are working on a Rubrik protection job backing up VMware virtual machines and the failure repeats on the same target or schedule.
• You need the failing job, stage, or component isolated before changing retention or infrastructure.

Not for this skill when

• A VM whose guest quiescing fails inside the operating system, where the fix is in-guest agents rather than snapshot state.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Open the Rubrik job's event detail for the VM and note the exact snapshot sub-error returned from the hypervisor. Verify: the hypervisor-level reason is recorded
2. Inspect the VM in vSphere for existing snapshots, consolidation needs, and datastore free space. Verify: snapshot state and space are known
3. Remove stale snapshots or complete consolidation, and free or extend datastore space if the delta cannot fit. Verify: the VM is in a clean snapshot-ready state
4. Take a manual hypervisor snapshot to prove the path works outside Rubrik. Verify: a manual snapshot completes successfully
5. Rerun the Rubrik job scoped to that VM and confirm a new snapshot and backup complete. Verify: the job succeeds for the previously failing VM

Variant phrasings

rubrik snapshot creation failed for virtual machine

The verbatim phrasing.

rubrik backup failed vm snapshot vsphere datastore

The hypervisor phrasing.

rubrik job failed snapshot creation stale snapshot fix

The stale-snapshot phrasing.

Compatibility: Rubrik Cloud Data Management on VMware vSphere clusters

Why it happens

Rubrik asks the hypervisor to create the snapshot it then copies, so anything the hypervisor refuses, stale snapshots, consolidation debt, or a datastore without room for change deltas, surfaces as a generic snapshot creation failure in the backup job. The backup layer cannot fix state it does not own.

Edge cases / pitfalls

• A VM with an existing backup-tool snapshot from another product can block Rubrik; coordinate snapshot ownership per VM.
• Datastore space that suffices at job start can vanish during the job as the delta grows; check growth rate, not just free space.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_llsHPA9UMIyzJ8LNgQWVsw

Resolved from the public thread: https://vectle.com/posts/pst_llsHPA9UMIyzJ8LNgQWVsw

Thread query: Rubrik backup job failed "snapshot creation failed for virtual machine" error

TL;DR: Snapshot creation failing for a VM is a hypervisor-side conversation first: check the VM's snapshot state in vSphere, free space on its datastore, and whether a stale snapshot or a locked disk from an earlier job is blocking a new one. Clear the stale snapshot state and confirm the datastore can hold the snapshot delta, then rerun the Rubrik job for that VM alone before the full schedule.