PlateSpin Migrate uses X2P workflow to support full migration of Windows and Linux workloads to Oracle Cloud Infrastructure.
IMPORTANT:We recommend that no changes are made on the source workload during the full migration process to avoid any changes that are not replicated to the target workload.
Use the guidelines in this section to configure migration to VMs on Oracle Cloud Infrastructure virtual hosts.
Before you configure a migration job to migrate workloads to Oracle Cloud, you must discover and perform an inventory of the source workload you want to migrate. See Workload Discovery in the Migrate Client and Workload Discovery in the Migrate Web Interface.
Use the custom PlateSpin image that you imported from the Oracle Object Storage to create a target VM instance on the Oracle Cloud Infrastructure virtual host. You can then connect to this created instance and register the instance with PlateSpin Migrate server. For information about importing the custom PlateSpin image, see Importing PlateSpin Custom Images to Oracle Cloud Infrastructure.
Sign in to the Oracle Cloud Console.
Open the navigation menu. Go to Compute and click Instances. Choose your Compartment and then click Create Instance.
In the Create Compute Instance dialog box, you specify the resources to use for your instance. By default, your instance launches in the selected compartment, and the resources you choose also come from the selected compartment.
NOTE:
For the Choose an operating system or image source option, select the name of the custom image you previously imported from Oracle Object Storage. See Importing PlateSpin Custom Images to Oracle Cloud Infrastructure.
For the Configure boot volume option, you must ensure to provide the boot volume size that is large enough to recreate the volumes from the source workload.
For more information about the resources, see Oracle Cloud Infrastructure Documentation.
Click Create. The created instance displays in the instance list.
NOTE:The created VM instance has a single disk and no additional disks or volumes can be added until the migration has completed. You can specify the disk size, up to 16 TB, when the VM instance is deployed.
When the instance is fully provisioned and running, create a console connection for this created instance so that you can use SSH to connect to it. For information about creating the console connection for the instance, see Oracle Cloud Infrastructure Documentation.
Register the target VM instance with PlateSpin Migrate server. See Registering the Target Virtual Machine Instance with PlateSpin Server.
After you use the PlateSpin Custom Image to create a virtual machine instance on the Oracle Cloud Infrastructure and connect to it using SSH, you are ready to register the target VM instance with your PlateSpin Server:
IMPORTANT:Use the PlateSpin Migrate Web Interface to ensure that no value is set for the AlternateServerAddress PlateSpin Configuration parameter. See Configuring Alternate IP Addresses for PlateSpin Server.
In the Oracle Cloud Console, select the instance that you previously created on Oracle Cloud and click Reboot to shutdown the target instance and restart it. See Oracle Cloud Infrastructure Documentation.
NOTE:If rebooting the VM instance using the Oracle Cloud Infrastructure Console takes too long, then the SSH session to the target VM instance might time out. In such cases, reset the VM instance using the Oracle Cloud Infrastructure Command Line Interface.
In the SSH session that you are using to connect to the target VM instance, type one of the following boot options when prompted and press Enter:
|
Boot Option |
Boot Action |
|---|---|
|
ps |
PlateSpin Linux for taking control You can also press Enter to select this option. |
|
fcoe |
PlateSpin Linux for taking control with FCoE support |
|
next |
Boot from the next boot device set in the BIOS |
If no key is pressed for 20 seconds, the workload boots from the next boot device set in the BIOS.
At the command line, provide the required information at each individual prompt:
PlateSpin Server: Enter the PlateSpin Server URL, using the following format:
http://Your_PlateSpin_Server/platespinmigrate
Replace Your_PlateSpin_Server with the host name or the IP address of your PlateSpin Server host.
Credentials (User Name/Password): Enter the name of an administrator-level user on the PlateSpin Server host, including the domain or machine name. For example: domain\username, or localhost\Administrator. Provide a valid password for the specified user.
Network Card: Select the network card that is active, then either enter a temporary static IP address for this NIC or press Enter to dynamically obtain an IP address from a DHCP server.
Temporary hostname: Provide a temporary VM name for PlateSpin Server to use to list the newly registered VM. The workload’s target host name you select in the migration job overwrites this name.
SSL encryption: If your PlateSpin Migrate is installed on a host with SSL encryption enabled, enter Yes. If not, enter No.
PlateSpin Migrate Network: Unless you have defined your own PlateSpin Migrate Network in PlateSpin Migrate Client, press Enter. If you are working with a non-default PlateSpin Migrate Network, type its name, then press Enter.
A controller on your target virtual machine communicates with PlateSpin Server and registers the virtual machine as a physical target for a migration job.
The registered target virtual machine displays in the Servers view of the PlateSpin Migrate Client Interface and in the PlateSpin Migrate Web Interface and you can now configure migration jobs to this target VM. See Migrating the Source Workload to a Target Instance on Oracle Cloud Infrastructure.
(For non-VPN setup) After you register the target virtual machine with Migrate Server, you must set the AlternateServerAddress PlateSpin Configuration parameter to the public IP addresses of the Migrate server. For information about configuring the AlternateServerAddress parameter, see Configuring Alternate IP Addresses for PlateSpin Server.
Use either the PlateSpin Migrate Web Interface (recommended) or the PlateSpin Migrate Client to migrate the workload to the target instance:
Using PlateSpin Migrate Web Interface: See Configuring Migration to a Physical Target (P2P, V2P) Using Migrate Web Interface.
NOTE:The Oracle Cloud target VM instance is already registered with your PlateSpin Server in Registering the Target Virtual Machine Instance with PlateSpin Server. When you use the PlateSpin Migrate Web Interface to configure migrations to the physical target, ignore the step that requires you to register your target physical machine with PlateSpin Migrate by booting it with the PlateSpin ISO.
Using PlateSpin Migrate Client: See Configuring Migration to a Physical Target (P2P, V2P) Using Migrate Client.
NOTE:The Oracle Cloud target VM instance is already registered with your PlateSpin Server in Registering the Target Virtual Machine Instance with PlateSpin Server. When you use the PlateSpin Migrate Client to configure migrations to the physical target, ignore the step that requires you to register your target physical machine with PlateSpin Migrate by booting it with the PlateSpin ISO.