# Fatal Errors in VM Backup Processes

Certain errors are classified as fatal errors and may prevent VMs from being retried during backup operations. VMs affected by these errors will remain in a Skipped or Failed status due to the blocking nature of these issues.

Note

Errors are only applicable for Virtual Server jobs.

## Skipped or Failed VMs

The following conditions can result in VMs being skipped or marked as failed:

- Snapshot Creation Disabled by VMware SRM: If VMware Site Recovery Manager (SRM) has disabled snapshot creation for a VM, it will be marked as Skipped and will not be retried during subsequent backup attempts.

- Fatal Errors in Final Backup Attempt: During the last attempt of a backup job, any pending VMs encountering fatal errors will be marked as Failed. No new backup jobs will be created to protect these VMs until the issue is resolved.

- Fatal Hypervisor Errors: VMs that encounter a fatal hypervisor error (e.g., VSBKP_ERR_VMINFO) during processing will be marked as Failed.

- Missing Failback Information: VMs lacking failback information will be marked as Failed.

- Missing Application Context or Valid VM Group Details: VMs without proper application context or valid VM group details will be marked as Failed.

- Hard Indexing Errors: VMs that experience a hard indexing error during processing will be marked as Failed.

- Archive File Creation Failure: If an archive file cannot be created during an IntelliSnap backup, the affected VM will be marked as Failed.

- Invalid Disk State: VMs with disks in an invalid state will be marked as Failed.

- No Valid Disk Block Collection: VMs without valid disk block collection during backup copy operations will be marked as Failed.

- Archive File Commit Failure: VMs encountering a failure during the archive file commit process will be marked as Failed.

- Extension Startup or Backup Failure: VMs where the extension startup or extension backup process fails will be marked as Failed.

×

Loading...