Using Offline Migration

Velostrata enables you to migrate workloads with operating systems that are not currently supported by Velostrata's streaming technology.

During the offline migration process, the VM storage is migrated to the cloud first, and the VM is started in the cloud only after the migration is completed. Velostrata automatically performs the detach and cleanup of residue data associated with this VM.

Offline migration can also be used for “storage only migration”. Old VMs (e.g. RedHat 4) can be migrated to the cloud with offline migration, even when unsupported by the cloud provider. Administrator can then reattach a data disk to a newer and supported cloud instance.

For AWS, you may select to encrypt the native volumes and optionally, specify the key to be used. See EBS Encryption Key Preparation.

Important notes:

- After the migration, the VM is located in the cloud with the name of the VM as defined on-premises.

- Preparation of the VM is required, before the offline migration starts.

Preparations Before the Offline Migration Process

RHEL 5.11+
  • Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and change the primary interface name to eth0 and make sure it is set to DHCP:
Ubuntu 12.x
  • Edit /etc/network/interfaces  and change the primary interface name to eth0 and make sure that it is set to DHCP:
# The primary network interface
auto eth0
iface eth0 inet dhcp
Windows Server 2003, Windows Server 2003 R2, Windows Server 2008 (non-R2) to AWS

Install the following packages:  

  • .Net 3.5 redist  - dotnetfx35setup.exe - Download link
  • Windows Management Framework Core 2.0. Reference - Download link
    Note: The specific package depends on the exact OS version, for OS - Windows 2003 - Service pack 2 is a prerequisite.
  • - Download link
  • - Download link 
    1. Extract the zip file to a temporary folder destination.
    2. Execute Citrix_xensetup.exe in the extracted folder. During the installation process, a warning message appears notifying you that the workload platform on which the installation is running is not a Citrix Xen platform, and prompts you for approval.
    3. Click OK to approve.
Windows 2008 non-R2 to GCP

No special preparation required prior to offline migration for Windows Server 2008 64 bit version. 

Windows Server 2008 32 bit version requires package installation before initiating offline migration, please contact Velostrata support for further details

Windows 2008 non-R2 to Azure
  • No special preparation required prior to offline migration.
Windows Server 2003, Windows Server 2003 R2 to Azure

Complete the following preparation prior to performing an offline migration for a Windows 2003-based VM to Azure.

  1. Copy (and extract) the Velostrata Offline for 2003 package to the GuestOS root of the c:\ drive.  

      Windows 2003 x86 package

      Windows 2003 x64 package

     The extracted package folder includes the velosoffline.cmd script which runs the following:

  • Disables hibernate.
  • Enables system restart on BSOD.
  • Installs Hyper-V integration tools post detach at Windows start up.
  1. Create a scheduled task to run the script at Windows start up.
  1. Set the task to run When my computer starts.
  1. Enter the user name and password of an administrative user for the GuestOS.
  1. For the task, select the Settings tab, and select Delete the task if it is not scheduled to run again.
  1. Migrate the VM offline (as described below).
  2. After the Detach, delete the scheduled task created before the migration.
Windows 2003 to GCP
  • No special preparation required prior to offline migration.
Onprem-toCloud: To migrate a VM offline:
  1. Perform the offline preparation as explained in previous section, exact procedure depends on specific OS.  
  2. On the vSphere Web Client, select the desired Virtual Machine.
  3. Right-click on the VM and select Velostrata Operations > Offline Migrate.

Note: The following AWS instance types support 32 bit: t2.nano, ,t2.micro, t2.small, t2.medium, and c3.large.

  1. Select the Velostrata Cloud Extension.

Note: If you select to run your VM in a CE that is in the AWS Marketplace, a message appears indicating that you may incur usage costs according to the subscription terms.

  1. Click Next.
  1. Select the Instance Type (VM size).
  2. Click Next.
  1. Select the required Security Groups.

Note: For AWS, if public access is required from the internet to the VM, a DMZ is required with an associated security group, including appropriate inbound and outbound rules.

  1. Click Next.
  1. Select a Subnet in the cloud. Typically, the selection here would be of a private network subnet. AWS - When Cloud Edge nodes (A, B) are placed in different AZs, the Cloud Edge node in the same AZ as the selected subnet is automatically used, otherwise a manual node selection is required.
  2. From the Configure Private IP drop-down list, select Auto to allow an available address on the subnet to be automatically assigned, or Static if a specific address assignment is required.
  3. If you select Static, a Static IP field appears. Enter the required static IP for the instance or specify an ENI ID (e.g. eni-xxxxx) to associate a reserved Elastic Network Interface.
  4. From the Edge Node drop-down list, select the required node. For Azure, a manual selection of the Edge Node to use is required. Select Node A or Node B. The default selection is Node A. For AWS, when Cloud Edge nodes are placed in the same Availability Zone (AZ), a manual selection of the Cloud Edge node to use is required.
  5. Click Next.
  1. Select the Storage Type.
  2. For AWS, select Encrypt EBS volume, if you are using EBS encryption for native volumes, and then from  KMS Key ID, select the encryption key alias to be used. If this is not specified, the default key is used.
  3. Click Next.

The Summary page differs slightly for AWS and Azure.

  1. Review the summary and then click Finish.
  2. To view the related migration tasks, view the Monitor > Tasks & Events tab.

After the offline migration is completed, you can connect to the VM using its private IP address or FQDN.

Cloud-to-Cloud: To migrate a VM offline:
  • To perform offline migration, run Invoke-VelosOfflineMigration [-Id] <String[]> -CloudExtension $variable [-EdgeNode <String>] -StorageSpec <String> -InstanceType <string> -CloudDetailsName <string>

For example:

Invoke-VelosOfflineMigration -Id i-04151a4a1067cfe9b -CloudExtension $gcpCe -EdgeNode NodeA -StorageSpec Standard -InstanceType n1-standard-1 -CloudDetailsName aws