Skip to main content
NetApp Knowledge Base

Restored VM failed to boot up with error: Failed to extend swap file from 0 KB to size KB

  1. Last updated
  2. Save as PDF
Views:
362
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapVault
  • Veeam

Issue

  • VMware NFS Datastores are being backed up by Veeam using SnapVault 
  • Veeam successfully restores the datastore however VM fails to boot
  • VM doesn't boot up when the VM is restored using Flexclone option as described below:

How to manually restore a VMware ESX virtual machine from a snapshot volume/LUN

  • Power on VM fails with error:

Failed to extend swap file from 0 KB to size KB.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.