Replacing/Restoring a Virtual Machine from an OVF File
Replace a virtual machine (VM) from a everRun-created Open Virtualization Format (OVF) file if you want to restore (that is, recover) a VM on your everRun system by overwriting the VM with a previous backup copy. (If you want to import a VM from a different system, see the overview in Creating and Migrating Virtual Machines.)
Typically, importing a VM creates a new instance of the VM with unique hardware IDs. Restoring a VM creates an identical VM with the same SMBIOS UUID, system serial number, and MAC addresses, if provided in the VM image, that your guest operating system and applications may require for software licensing. The hardware ID, though, of the restored VM is unique. If an identical VM already exists on the everRun system, restoring the VM allows you to replace the VM and overwrite it with your previous copy.
You can restore a VM that already exists on an everRun system only if you have previously exported a VM (see Exporting a Virtual Machine ) from an everRun system or a VM snapshot (see Exporting a Snapshot) to OVF and Virtual Hard Disk (VHD) files on a supported network share or a USB device. Copy these files to your management PC, or mount the USB device or network share on the target everRun system as described in Mounting a USB Device or Network-mounted Folder on the everRun System, and then use the everRun Availability Console on the target everRun system to restore the OVF and VHD files from your management PC.
Caution: Consider backing up your existing VM on the everRun system before overwriting and restoring it. If you export the VM or another snapshot to create the backup, ensure that you do not overwrite the OVF and VHD files that you want to restore.
Notes:
- You can restore a VM from only an OVF created from an everRun system. You cannot restore a VM from an OVF created from a third-party system.
- You typically restore a VM to recover the VM from a previous backup. When restoring a VM, the system attempts to preserve the hardware ID and MAC addresses of all network interfaces.
- Restore a VM only if you are specifically trying to restore a particular instance of an everRun VM and that the restored VM will be the only copy of this VM running across all everRun servers in your network.
- The time required to restore a VM depends on the size and number of volumes in the source VM as well as network bandwidth. For example, transferring a VM with one 20 GB boot volume over a 1Gb network may take about 30 minutes.
- If you overwrite and restore an existing VM, the everRun system removes the existing VM and its volumes, but the system does not remove any of the VM's snapshots or the volume containers in which the snapshots are stored. The volume containers continue to use storage space on your everRun system until you remove the VM's snapshots (see Removing a Snapshot). If storage space is limited, you may want to remove the snapshots before starting the restore process to ensure that there will be enough storage space for the operation.
- If you previously expanded the volume containers of your VM to allow enough space for snapshots, you may want to note the current size of each volume container before you overwrite and restore the VM. Because the everRun system creates all new volume containers for a restored VM and does not preserve the expanded container sizes, you need to manually expand the volume containers of the restored VM after the restore process is finished (see Expanding a Volume Container on the everRun System).
- If the everRun system switches from the primary PM to the secondary PM while restoring a VM, the restore process fails. This does not affect the continuous uptime of your system, but you must delete the incomplete VM and associated volumes on the everRun system, and restore them again.
Prerequisites:
- Before you replace (that is, restore) a VM image from an everRun system, use the everRun Availability Console on the source everRun system to export a VM (see Exporting a Virtual Machine ) or a VM snapshot (see Exporting a Snapshot) to OVF and Virtual Hard Disk (VHD) files on a supported network share or a USB device. Copy these files to your management PC, or mount the USB device or network share on the target everRun system as described in Mounting a USB Device or Network-mounted Folder on the everRun System, and then use the everRun Availability Console on the target everRun system to restore the OVF and VHD files
- Both PMs of the everRun system must be online for the restore process to function properly.
To restore a VM
- Log on to the everRun Availability Console on the target everRun system.
- If you are restoring a VM from a USB device or network share (instead of the PC running the everRun Availability Console), mount the device or share on the everRun system as described in Mounting a USB Device or Network-mounted Folder on the everRun System.
- On the Virtual Machines page (see The Virtual Machines Page), select the VM that you want to restore in the upper panel.
- In the lower panel, click Restore or click Import/Restore near the top pane.
-
Select one of the following:
-
Browse for OVF
Click Browse and locate the OVF on a local computer.
-
Browse for OVF from USB
Select a partition from the pull-down menu, click List OVFs, and select a file from the pull-down menu.
-
Remote OVF via Windows Share(CIFS/SMB)
The restore source is a folder on a CIFS share. Enter a Username, Password, and Repository value. For Repository, enter a value in the format \\machine_URL\ShareName (for example, \\192.168.1.34\MyOVFs). Then, click List OVFs and select an OVF file from the list.
-
Remote OVF via NFS
The restore source is a folder on a remote system accessed through NFS. For Repository, enter the URL of the remote system in the format nnn.nnn.nnn.nnn (do not include http:// or https://). Then, click List OVFs to display a list of all OVF files in the remote folder. Select the file to import or restore.
- Select Restore. (Scroll down the window, if necessary.) A warning message appears.
-
Click Continue to proceed.
Caution: Restoring a VM overwrites all of its data and configuration details.
- If prompted, add VHD files.
-
Review the information and make any desired edits, if necessary:
-
Name, CPU, and Memory
Displays the name of the VM, the number of vCPUs, and the total memory the VM can use. Edit the information, if necessary.
-
Storage
Displays the name, size, destination, and sector size of each volume. In the Create column, select a box for a volume to allocate a storage container for the volume on the everRun system (the boot volume is required). In the Restore Data column, select a box to import data for a volume from the VHD file.
If the target everRun system has more than one storage group, you can also select the storage group in which to create each volume. Ensure that you select a Destination group that supports the sector size of the volume you are importing (see Planning Virtual Machine Storage) and select the Sector Size that matches the source volume (the restore wizard cannot convert the sector size of a volume). Note that the boot volume must have a sector size of 512 B. You can select the sector size, either 4K or 512B, only for data disks.
-
Network
Displays all of the available networks. You can remove a network or add one that is not already allocated. A minimum of one network is required.
- Optionally, clear the check box for Auto start Virtual Machine after restore if you need to reprovision the VM before starting it for the first time.
-
Click Restore to begin restoring the VM. When the transfer is complete, click Done to close the wizard.
Note: Restored volumes begin to appear on the Volumes page of the everRun Availability Console while the restore process is still in progress. Do not attach or remove any of these restored volumes until the restore window reports that the process is complete; otherwise, the restore process fails.
-
If applicable, use the Reprovision Virtual Machine wizard to allocate additional resources to the VM, as described in Reprovisioning Virtual Machine Resources. Also, if you want to allocate additional space in each volume container for snapshots, see Expanding a Volume Container on the everRun System.
When you are finished reprovisioning the VM, click Start to boot the VM.
After you verify that the restored VM is functioning properly, the restore process is complete; however, the everRun system may continue to synchronize data between PMs to enable High Availability (HA) or Fault Tolerant (FT) operation.
Note: Your restored VM and its associated volumes may be marked with warning symbols until the data has been synchronized and the VirtIO drivers are running.
Troubleshooting
If necessary, use the following information to resolve problems with the restore process.
To clean up after a canceled or failed restore process
In the everRun Availability Console on the target system, remove the restored VM and any volumes associated with the restored VM, if present.