Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4362

SureBackup VM Power On fails with: "Failed to extend swap file" or "Error: Insufficient resources."

$
0
0

SureBackup VM Power On fails with: "Failed to extend swap file" or "Error: Insufficient resources."

KB ID: 4301
Product: Veeam Backup & Replication | 10 | 11
Published: 2022-04-20
Last Modified: 2022-04-21

Challenge

A SureBackup job, for a VMware environment, fails during the VM Power On step with either of the following errors:
Error: Module 'MonitorLoop' power on failed.  (Module 'MonitorLoop' power on failed.
Failed to extend swap file /vmfs/volumes/7f64206b-8d976ce0/TESTVM_240de4f8816d40e8a777f6b653a0ea8e/TP-TESTVM-324f152e.vswp from 0 KB to 4194304 KB : 
No space left on device, Current swap file size is 0 KB., Failed to extend the virtual machine swap file, 
Could not power on virtual machine: No space left on device., Failed to power on VM., Failed to start the virtual machine.)
failed to expand swap
Error: Insufficient resources. (Out of resources)
Insufficient resources. (Out of resources)
An error with the same message can be observed within the vSphere Client:
Error: Insufficient resources. (Out of resources)

Cause

This issue occurs when the Instant recovery write cache folder has insufficient space.

Solution

Determine which Repository contains the backup files for the VM that is failing to power on. Edit that Repository, and on the Mount Server tab, you will find the assigned Mount Server and Instant recovery cache folder path. Now you may either:

  1. Connect to the Mount Server and ensure sufficient free space on the drive where the Instant recovery cache is located.

    or
  2. Assign a different Mount Server and Instant recovery write cache location with sufficient free space.

More information

It is strongly advised to enable the "Redirect write cache" option within the Virtual Lab settings. Enabling this option will allow the SureBackup job to store the redo logs for each VM on the specified datastore instead of the Mount Server. Some files will still be stored in the Mount Server's Instant Recovery cache, but the space needs are significantly reduced. Additionally, redirecting the write cache to a datastore improves SureBackup performance.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Viewing all articles
Browse latest Browse all 4362

Trending Articles