Migrating Physical Servers
Migrating a Physical Server
Migrating a physical server to the cloud is done by booting a Velostrata Connector ISO image into RAM from a virtual or physical DVDROM/CDROM device. The Velostrata connector maps the local storage and creates a Stub VMware VM as a management object for Velostrata cloud migration operations. From that point forward, the migration is done in a similar way to the migration of other VMs except here it takes place in write isolation mode, meaning data changes made in the cloud are not synced back to on-prem.
- The Stub VM created in the process is intended for Velostrata management operations only, and not set up for local execution on vSphere. It is set up with no network interface, and a minimal CPU/RAM setting.
- Test clone is not supported for physical servers.
- Disk types supported include SAS, SATA, SSD, virtual disks presented by hardware controller, and SAN volumes mounted on physical HBAs.
- PATA/IDE disks are not supported.
- Minimum of 4GB RAM is recommended
- For machines with less than 4GB RAM, press any key during the boot splash screen (one with the keyboard icon) and choose the Velostrata Connector (low memory) option from the menu. This uses an on-demand copy from the CD image.
- Physical DVDROM/CDROM or virtual CDROM to boot the Velostrata Connector ISO from.
1. Check OS compatibility in the Velostrata release notes.
2. For Linux OS install the Velostrata-Prep RPM, as described in the relevant chapter here.
3. Download the Velostrata Connector ISO: http://tiny.cc/VelosPhysicalConnector
4. Boot from the Velostrata ISO.
Note: This can be done by using ILO (HP Enterprise servers) or iDRAC (Dell servers).
The steps below use HP ILO:
5. Launch the remote console.
6. Select Virtual Drives > Image File CD/DVD-ROM, and select the Velostrata Connector ISO that you downloaded.
7. Select Power Switch > Reset.
8. Once the server is up, ensure that it boots from the ISO.
9. Log in to the ISO using the following credentials: ubuntu\Welcome01
10. Run ./VelosConnector.sh script to view the menu.
11. In vCenter, check for an iSCSI Software Adapter. If you do not have one, follow these steps:
11A. Navigate to Configure > Storage Adapters and add an iSCSI Software Adapter.
11B. Under Networking, select VMKernel adapters and click the edit icon.
11C. Click Port properties option.
11D. Under the Enable services area, check the Provisioning checkbox and click OK.
Note: we recommend a 1:1 relationship between a VM and an iSCSI Target.
(See screen shots below for reference):
12. Select 1) Register a Stub VM for Velostrata operations and follow the instructions. Note that registering the OS properly is required in order to create the correct AMI in the cloud and enable proper migration.
The VM appears in vCenter.
13. Now that the VM is in vCenter, you can perform the migration using the standard process as outlined here.
Deleting a Stub VM
You can delete the VM and the iSCSI target configuration on the ESX side after your migration is complete.
Note: If you create more than one VM using the same iSCSI Target, when you delete any of those VMs, it will automatically delete the iSCSI Target as well. Therefore, you must manually delete any additional VMs that were tied to that iSCSI Target.
Showing the iSCSI Target Settings
You can view the iqn, portals and luns that will be migrated to the cloud.
- Select 3) Show iSCSI Target Settings. Ensure that you can see all the disks of the server.
Managing the IP Configuration
You can view the IP of the server that will be used for the iSCSI target configuration. The ISO gets the IP from DHCP by default, but you can configure a static IP. It is necessary to have a valid IP before the stub can be registered.
- Select 4) Show IP Configuration.
- Select 5) Setup Static IP to configure a static IP.