Migrating Servers To Oracle Cloud

White Paper
IT Operations Management
Best Practices for Migrating

Servers to Oracle Cloud
with PlateSpin Migrate
Updated for PlateSpin® Migrate 12.2.2

Table of Contents page
Introduction to Server Migrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Overview of the Migration Process and Pre-Requisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Inventory of the Source and Target Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Configuration of the Full Migration in PlateSpin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Learn More At. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
PlateSpin Migrate is a Introduction to Server Migrations
powerful server portability
solution that automates In today’s dynamic world, the need for cost reduction and the desire to increase operational efficiency have
the process of migrating a constant impact on the organization of IT resources. Enterprises are relentlessly looking for better ways
servers over the network
to manage infrastructure, systems and applications— and this often leads to the execution of projects
between physical machines,
virtual hosts, and enterprise where large numbers of servers are moved from one platform or data center to another. Typical examples
cloud platforms—all from include the migration of physical servers onto a virtual platform, the migration of virtual machines from
a single point of control. one virtual platform to another, traditional data center consolidations, and the migration of on-premise
servers into a managed or public cloud, like Oracle Cloud.
This White Paper contains best practices for migrating servers into Oracle Cloud with PlateSpin Migrate
from Micro Focus®. PlateSpin Migrate is a powerful server portability solution that automates the process
of migrating servers over the network between physical machines, virtual hosts, and enterprise cloud
platforms—all from a single point of control. When migrating such servers, PlateSpin Migrate refers to
these servers as “workloads.” A workload in this context is the aggregation of the software stack installed
on the server: the operating system, applications, and middleware, plus any data that resides on the server
volumes. PlateSpin Migrate provides enterprises and service providers with a mature, proven solution for
migrating, testing, and rebalancing workloads across infrastructure boundaries. Some of the key features
in PlateSpin Migrate are:
■■ Anywhere-to-anywhere workload migration capabilities
■■ Horizontal scalability with up to 40 concurrently active migrations per individual PlateSpin

Migrate server
■■ Zero service downtime during replication phases, and near-zero service downtime during final cutover
■■ Ability to fully test a migrated workload before cutting it over in production
www.microfocus.com 1
White Paper
Best Practices for Migrating Servers to Oracle Cloud with PlateSpin Migrate
Overview of the Migration Process

and Pre-Requisites
PlateSpin Migrate offers the capability to replicate machines to Oracle Cloud Infrastructure Compute. At
the moment, only the Full Migration process, which replicates the entire volume data from Source to Target,
is available. Server synchronization, which synchronizes Source and Target without transferring the entire
volume data, is not available at this time.
For a Full Migration, you must ensure the Source machine is not being utilized during the entire time of the
Full Migration, to avoid any changes that would not be replicated to the Target. Once the Full Migration has
completed, the Source is cut over, powering down and the Target is brought online.
Diagram
■■ The Source is the machine to be migrated to Oracle Could Infrastructure Compute.
■■ The Target is a VM instance, to be created manually in a Compartment on Oracle

Cloud Infrastructure. It is to be launched from the PlateSpin custom image.
■■ The PlateSpin Migrate Server is a machine where the Migrate components have been installed.
It will manage/orchestrate the migration process. It can be installed either inside (see first
diagram below) or outside of Oracle Cloud Infrastructure (see second diagram below below).
■■ The PlateSpin Migrate Client is the Graphical User Interface. It can be installed either on the PlateSpin
Migrate Server or on a separate machine. Only one user at a time can use the PlateSpin Migrate Client.
Figure 1. Oracle Cloud Infrastructure Compute Compartment
2
Figure 2. Oracle Cloud Infrastructure Compute Compartment
Installation of the PlateSpin Migrate Server

The installer can be downloaded from the Micro Focus Downloads web page. For more details with regard
to the installation process, you may refer to the Installation Guide (HTML version or PDF version).
Supported Operating Systems for Source Machines

Though PlateSpin Migrate does not officially support migration to Oracle Cloud Infrastructure Compute,
the process is similar to a semi-automated migration to Physical machine (X2P).
You may refer to the User Guide for the list of Operating Systems tested and supported for migration
to Physical machine (HTML version or PDF version page 23 “2.1.1 Supported Source Workloads For
Migration to Non-Cloud Platforms”).
Import of the PlateSpin custom image in Oracle Cloud Infrastructure

The Target is a VM instance, in Oracle Cloud Infrastructure Compute, to be launched from the PlateSpin
custom image. The resulting VM instance will have a single disk and no additional disks or volumes can
be added until the migration has completed. The size of the disk can be specified when the VM instance
is deployed and can be as big as 16 TB.
White Paper
From “Compute” -> “Custom Images”, import the below object storage URL:
https://objectstorage.us-ashburn-1.oraclecloud.com/p/8563HKrQ_5cdi4oJQXvV4NIcGZbatb6XU
b5pshTs4-A/n/platespin/b/PlateSpinMigrate12_2_2/o/PlateSpin_Migrate_Custom_Image_12_2_2.
vmdk
Figure 3. Custom Images
Figure 4. Import Image
It will take some time for the Custom Image to get imported:
Figure 5. PlateSpin Migrate Customer Image Import
4
Communication Requirements
Source machine, Target machine and PlateSpin Migrate server must be able to communicate with each
other’s during the entire migration process.
The diagram shown previously in section “I. 1. Diagram” gives an overview of the port requirements.
For more details with regard to the communication requirements, you may refer to the User Guide
(HTML version or PDF version page 47 “2.6 Access and Communication Requirements across your
Migration Network”):
■■ Source and target workloads need to be able to communicate with the PlateSpin Migrate Server
on port HTTPS (TCP/443).
■■ The PlateSpin Migrate Server needs to be able to communicate with the target workload via
SSH (TCP/22).
■■ The PlateSpin Migrate Client needs to be able to connect to the PlateSpin Migrate Server over
HTTPS (TCP/443).
■■ To discover Windows source workloads, the PlateSpin Migrate Server needs to be able to
connect to them via WMI/RPC/DCOM (TCP/135,445) and NetBIOS (UDP/137,138 & TCP/139).
■■ To discover Linux source workloads, the PlateSpin Migrate Server
needs to be able to connect to them via SSH (TCP/22).
■■ Each target workload needs to be able to connect to its source workload on port 3725 (TCP)
or vice versa. This is the port over which the replication traffic is sent. The port number is
configurable (see below). The way of the TCP connection is also configurable (see below).
By default, the target workload will connect to the source workload on port 3725.
You may change the way the connection is done between Source and Target. By default, the Target initiates
the connection to the port 3725 on Source, trying each of its IP addresses until the connection succeeds.
You may instead change a global setting on the PlateSpin server to have the Source initiates the connec-
tion to the port 3725 on Target.
To do so, launch the URL, www.[PlateSpin_Migrate_Server_IP_or_hostname]/platespinconfiguration

search for “SourceListensForConnection” and change the value from ‘true’ to ‘false’:
Figure 6. PlateSpin Server Configuration Settings
White Paper
Figure 7. PlateSpin Server Configuration Settings
You may as well change the port used for the data transfer, set by default to 3725, to another one.
To do so, launch the URL www.[PlateSpin_Migrate_Server_IP_or_hostname]/platespinconfiguration,

search for “FileTransferPort” and change the value from ‘true’ to ‘false’:
Figure 8. File Transfer Port
You might need to set up a site-to-site VPN, such as OpenSWAN, to enable both-way communication
between your servers and your Oracle Cloud Infrastructure.
Inventory of the Source and Target Machines

Inventory of the Source Machines
CREDENTIALS REQUIRED FOR THE SOURCE MACHINES
The PlateSpin Server must be able to connect remotely to the Source machines via credentials authenti-
cation. Authentication via private SSH key is not supported for Linux workloads, so you may have to allow
root level credentials remote login.
6
This table provides guidelines for machine type selection, credential format, and syntax for inventory
parameters for workloads.
To Discover Machine Type Credentials Remarks

All Windows Windows Local or domain For the username, use this format:
workloads administrator credentials. ■■ For domain member machines: authority\principal
■■ For workgroup member machines: hostname\principal
All Linux Linux Root-level username Non-root accounts must be properly configured to use sudo.
workloads and password See KB Article 7920711 (https://www.netiq.
com/support/kb/doc.php?id=7920711).
Table 1. Machine type selection, credential format, and syntax.
INVENTORY VIA THE MIGRATE CLIENT

The inventory of the Source machine is done via the Migrate Client. Multiple Source machines can be
inventoried.
For more details with regard to the inventory of Windows and Linux Source machines via the Migrate
Client, please refer to the User Guide (HTML version or PDF version page 47 “20.6.1 Workload Discovery
in the Migrate Client”).
Here are some screenshots for the inventory process of a Windows machine and a Linux machine:
Figure 9. Windows machine Figure 10. Linux machine
White Paper
The machines are then listed in the “Servers” section of the Migrate Client:
Figure 11. Servers section of the Migrate Client
Inventory of the Target Machine

LAUNCHING AN INSTANCE FROM THE PLATESPIN CUSTOM IMAGE
From “Compute” -> “Images”, click on the PlateSpin custom image you want to launch your Target from,
then click “Launch”:
Figure 12. Launching
Figure 13. Launch instance
8
Fill the fields required to launch the instance. It is not necessary to specify a hostname. Pay extra attention
to specify a “CUSTOM BOOT VOLUME SIZE” large enough to have the volumes from Source recreated:
Figure 14. Fields required to launch instance
After some time, the new VM instance will be marked as “Running”:
Figure 15. VM instance running
CREATING A CONSOLE CONNECTION

Once launched from the PlateSpin Custom Image, the Target can be accessed via SSH Console.
White Paper
You must create an SSH Console connection, specific to the Target, in order to temporarily access it for
performing the registration process into PlateSpin Migrate. To do so, click “Console Connections (x)” ->
“Create Console Connection”:
Figure 16. Console Connection
You will need a public key on the machine you want to launch the SSH Client.
If the machine, on which you want to launch the SSH Client, is Linux, this can be done via the below com-
mand, then copy the contents of ‘/root/.ssh/id_rsa.pub’:
Figure 17. ssh-keygen
10
If the machine is Windows, you may use PuTTYgen (which is part of PuTTY) to generate a public/private
key pair. Copy the OpenSSH public key (which is different format than what PuTTY would save as a public
key) and save the private key:
Figure 18. PuTTY
Figure 19. PuTTY Key Generator
White Paper
Figure 20. Dave private key
Go back to Oracle Cloud Infrastructure and paste the SSH public key to create the Console Connection:
Figure 21. Create Console Connection
12
Then, click on “…” -> “Connect with SSH”:
Figure 22. Connect with SSH
Whether your machine, on which you want to launch the SSH Client, is Linux or Windows, select Plateform
= “Linux/Mac OS” and copy the SSH Connection String:
Figure 23. SSH Connection String
On Linux, you may paste it directly into Terminal:
Figure 24. Paste directly into Terminal
White Paper
On Windows, you may use Gitbash. After Gitbash has been installed, you must export the OpenSSH private
key (previously generated and saved) to your home folder in a ‘.ssh’ directory:
Figure 25. Load private key Figure 26. Export OpenSSH key
To know the patch of your home folder, launch Gitbash and type the command
Pwd
Figure 27. Gitbash
14
Figure 28. Save
You can now paste the SSH Connection String:
Figure 29. SSH Connection String
White Paper
REGISTRATION OF THE TARGET MACHINE VIA CONSOLE CONNECTION

After you have started the SSH session, you must reboot the Target via Oracle Cloud Infrastructure. This
can be done via the Oracle Cloud Infrastructure Web user Interface.
Figure 30. Target via Oracle Cloud Infrastructure
Once the Target has rebooted, switch back to the SSH session and, when prompted, type “ps64”, press
[ENTER] and wait for the PlateSpin temporary OS to load. The default 20s timeout has been extended to
a much longer duration for convenience:
Figure 31. PlateSpin temporary OS to load
If it takes too long to reboot the VM instance via the Oracle Cloud Infrastructure Web User Interface then
the SSH session will time out. In that case you can use the Oracle Cloud Infrastructure Command Line
Interface to reset the VM instance. The command is:
oci compute instance action --action reset -instance -id [ocid]
16
For more information on the Oracle Cloud Infrastructure Command Line Interface please refer to the on-line
documentation here: https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/cliconcepts.htm
The PlateSpin Custom Image will then load. At the prompt, follow the registration process. For more details
with regard to the Target registration process, you may refer to the User Guide (HTML version or PDF ver-
sion page 203 “19.6.2 Registering Target Physical Machines Using the PlateSpin ISO”):
Figure 32. Target registration process
White Paper
After some time, the registration of the Target will have completed and the target will be listed in the
“Servers” section of the Migrate Client:
Figure 33. Running PlateSpin OFX Controller
Figure 34. Jobs view
Figure 35. Status shows completed
18
Figure 36. Server view
Configuration of the Full Migration in PlateSpin

This is a quick overview of how to configure and run a Full Migration job in PlateSpin. For more details with
regard to the configuring the migration job, you may refer to the User Guide (HTML version or PDF version
page 404 “35.2 Configuring Migration to a Physical Target (P2P,V2P)”).
■■ You may drag and drop the Source onto the Target to trigger the migration job configuration wizard:
Figure 37. Trigger the migration job configuration
White Paper
Select “Move Workload”, leave it on “Full Migration”, then “Configure job”:
Figure 38. Action
■■ In “Conversion” -> “Transfer Method”, you may leave it to “Block Based”, which is the preferred
data transfer mechanism.
However you may want to use the “File Based” method if you wish to resize the volumes on Target:
Figure 39. Job Configuration
20
Or
Figure 40. File Based Job Configuration
■■ In “Network Identification” -> “Host name”, configure the hostname for the Target
machine. This is the final hostname the Target will get at the end of the migration:
Figure 41. Network Identification
White Paper
In “Network Connection 1” -> “TCP/IP Settings”, leave it to DHCP:
Figure 42. TCP/IP Settings
■■ If you previously selected the “File Based” transfer method, you can set a new size for the
volumes to be recreated on Target. This could be useful if you want to shrink the volumes, to
reduce the size of the disk required on Target:
Figure 43. Reduce the size of the disk required on Target
22
Figure 44. Properties
■■ You may start the migration by clicking “Start”:
Figure 45. Peer-tp-Peer Conversion Job
White Paper
■■ To check the details and progression of the migration, go to the “Jobs” section and expand the job:
Figure 46. Check details
Figure 47. Job section details
24
■■ After the migration job has completed, you may check the Target machine, which has got the initial
private and public IPs assigned by Oracle Cloud Infrastructure when you initially deployed it from
the PlateSpin Custom image:
Figure 48. Check Target machine
Figure 49. Primary VNIC Information
Learn More At
1. PlateSpin Migrate documentation: www.netiq.com/documentation/platespin-migrate
2. More PlateSpin Migrate resources: www.microfocus.com/products/migrate/resources
Additional contact information and office locations:
www.microfocus.com
www.microfocus.com
162-000167-001 | M | 06/18 | © 2018 Micro Focus or one of its affiliates. Micro Focus, the Micro Focus logo, and PlateSpin, among others, are trademarks
or registered trademarks of Micro Focus or its subsidiaries or affiliated companies in the United Kingdom, United States and other countries. All other marks
are the property of their respective owners.

Migrating Servers To Oracle Cloud

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Migrating Servers To Oracle Cloud

Transféré par

Droits d'auteur :

Formats disponibles

White Paper

Best Practices for Migrating

Updated for PlateSpin® Migrate 12.2.2

Introduction to Server Migrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

■■ Horizontal scalability with up to 40 concurrently active migrations per individual PlateSpin

■■ Ability to fully test a migrated workload before cutting it over in production

Overview of the Migration Process

■■ The Target is a VM instance, to be created manually in a Compartment on Oracle

Figure 1. Oracle Cloud Infrastructure Compute Compartment

Installation of the PlateSpin Migrate Server

Supported Operating Systems for Source Machines

Import of the PlateSpin custom image in Oracle Cloud Infrastructure

Figure 3. Custom Images

Figure 4. Import Image

Figure 5. PlateSpin Migrate Customer Image Import

To do so, launch the URL, www.[PlateSpin_Migrate_Server_IP_or_hostname]/platespinconfiguration

Figure 6. PlateSpin Server Configuration Settings

Figure 7. PlateSpin Server Configuration Settings

To do so, launch the URL www.[PlateSpin_Migrate_Server_IP_or_hostname]/platespinconfiguration,

Figure 8. File Transfer Port

Inventory of the Source and Target Machines

To Discover Machine Type Credentials Remarks

Table 1. Machine type selection, credential format, and syntax.

INVENTORY VIA THE MIGRATE CLIENT

Figure 9. Windows machine Figure 10. Linux machine

Figure 11. Servers section of the Migrate Client

Inventory of the Target Machine

Figure 12. Launching

Figure 13. Launch instance

Figure 14. Fields required to launch instance

After some time, the new VM instance will be marked as “Running”:

Figure 15. VM instance running

CREATING A CONSOLE CONNECTION

Figure 16. Console Connection

Figure 17. ssh-keygen

Figure 18. PuTTY

Figure 19. PuTTY Key Generator

Figure 20. Dave private key

Figure 21. Create Console Connection

Figure 22. Connect with SSH

Figure 23. SSH Connection String

On Linux, you may paste it directly into Terminal:

Figure 24. Paste directly into Terminal

Figure 27. Gitbash

You can now paste the SSH Connection String:

Figure 29. SSH Connection String

REGISTRATION OF THE TARGET MACHINE VIA CONSOLE CONNECTION

Figure 30. Target via Oracle Cloud Infrastructure

Figure 31. PlateSpin temporary OS to load

oci compute instance action --action reset -instance -id [ocid]

Figure 32. Target registration process

Figure 33. Running PlateSpin OFX Controller

Figure 34. Jobs view

Figure 35. Status shows completed

Configuration of the Full Migration in PlateSpin

Figure 37. Trigger the migration job configuration

Select “Move Workload”, leave it on “Full Migration”, then “Configure job”:

Figure 38. Action

Figure 39. Job Configuration

Figure 40. File Based Job Configuration

Figure 41. Network Identification

In “Network Connection 1” -> “TCP/IP Settings”, leave it to DHCP:

Figure 42. TCP/IP Settings