#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
TRY NOW
book meeting
BACK TO KB LIST

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

KB ID: 4301
Product: Veeam Backup & Replication | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13
Published: 2022-04-20
Last Modified: 2022-08-09
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

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/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.)
<test>
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.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.