Adding, Migrating, and Importing Virtual Machines

You can add new virtual machines (VMs) on a everRun system by:

• Creating a new VM without an existing source VM or physical machine (PM). See Creating a New Virtual Machine.

• Migrating an existing VM or PM directly over the network.

• Importing an Open Virtualization Format (OVF) file or Open Virtualization Appliance (OVA) file from an existing VM.

To copy an existing VM for the purpose of creating a new VM or creating a duplicate VM for troubleshooting, see Copying a Virtual Machine.

To back up a running VM for the purpose of recovering the VM in the event of a failure, see Backing Up a Running Virtual Machine and Recovering a Virtual Machine from a Backup.

To migrate or import a VM from another system, or to restore a VM on the same everRun system, see one of the following topics:

• Migrating a Physical Machine or Virtual Machine to a System

  Use the P2V client (virt-p2v) to transfer a PM or VM directly over the network to a new VM on the system.

• Exporting a Virtual Machine

  Use the everRun Availability Console to export the source VM to OVF and VHD files on a network share.

• Managing Snapshots

  Use the everRun Availability Console to create a snapshot of the source VM, then use the snapshot to create a new VM on the same system or export the snapshot to OVF and VHD files on a network share.

• Importing Virtualization Files

  Use the everRun Availability Console to import OVF and VHD files from another everRun system to the everRun system, or to import OVF and VHD files or an OVA file from a VMware vSphere-based system to the everRun system.

• Replacing/Restoring a Virtual Machine from an OVF File

  Use the everRun Availability Console to import OVF and VHD files back to the same system to overwrite and restore an existing VM from a previous backup copy.