v2v migration

Storware Backup and Recovery 7.1 introduces a robust VM-to-VM (V2V) migration capability, designed to facilitate the seamless transfer of vSphere virtual machine workloads into OpenStack environments. This advanced functionality enables direct restoration of VMware virtual machine backups to OpenStack, eliminating the need for intermediary conversion tools or manual intervention.

Before you start

• On the Node system that will be performing the migration Podman must be installed

• Execute the following script /opt/vprotect/node/scripts/setup_v2v.sh to configure and prepare the environmant for migration process.

  What this script does:

  1. Creates the /etc/subuid and /etc/subgid files that are required to support containers in rootless mode. It adds the UID and GID range for the vprotect user. Podman uses UIDs and GIDs mapped to a higher range to avoid conflicts with real users in the system.

  2. Setting the loginctl enable-linger option for the vprotect which allows this user to run processes in the background.

  3. Checks whether hardware virtualization is available and if not, sets the LIBGUESTFS_BACKEND_SETTINGS="force_tcg" variable in the /opt/vprotect/node/vprotect.env file which forces software virtualization.

• You need to have VMware provider added to your environment

  • You need to have a completed backup

• You need to have OpenStack provider added to your environment

  • The import/export mode must be configured as Disk Attachment

  • The inventory synchronization process must be completed

Migration process

1. From the main menu choose Virtual Environments -> Instances

2. Locate the VMware virtual machine you would like to migrate

3. From the Action menu choose Restore -> Migration (v2v)

4. Provide the necessary information using the migration wizard

   1. General tab

      1. Select the backup to migrate

      2. Select destination virtualization provider

      3. Select the destination project name

      4. Select the destination cluster

      5. Turn on a switch button to enable virtual machine name change

   2. Storage tab

      1. Select storage for specific virtual disk images or exclude disk from the migration process

   3. Networking tab

      1. Select destination network

   4. Advanced tab

      1. Turn on a button switch to automatically delete a virtual machine if an instance with the source name already exists in the destination environment

      2. Select a flavour for the migrated instance

      3. Select the Access key for the migrated instance

   5. Summary tab

      1. Verify all provided information

5. Click Restore

A new task will be created in the Workflow Execution Console.

Supported operating systems

Red Hat Enterprise Linux

• Red Hat Enterprise Linux 9

• Red Hat Enterprise Linux 8

CentOS

• CentOS Stream 8

• CentOS Stream 9

openSUSE

• openSUSE Leap 15.2

• openSUSE Leap 15.3

• openSUSE Leap 15.4

• openSUSE Leap 15.5

• openSUSE Leap 15.6

Fedora

• Fedora Server 41

Ubuntu

• Ubuntu 22.04

• Ubuntu 24.04

Debian

• Debian Linux 11

• Debian Linux 12

Windows (backup needs to be done on shutdown source VM)

• Windows 10 Pro

• Windows 11 Pro

• Windows Server 2019

• Windows Server 2022

Supported file systems:

• xfs

• btrfs

• ext4

• ntfs

• vfat

Limitations

• Instances with an encrypted system drive are not supported

• Instances with TPM are not supported

• Multi-boot instances are not supported

• Windows machines must be powered off before the backup that will be used to v2v restore