Based on the location of your PlateSpin Migrate server, review the following sections:
PlateSpin Migrate requires the use of Microsoft Azure Resource Management for migrating workloads into the Microsoft Azure cloud. For migrations to Microsoft Azure Cloud, you must prepare your Azure account, subscriptions, and services in the Azure global environment or the sovereign Azure China environment, based on your migration goals.
Table 9-1 describes the minimum configuration you must perform in the appropriate Azure environment before you can migrate workloads to Azure.
Table 9-1 Minimum Required Configuration for Your Azure Account
|
Azure Configuration |
Description |
|---|---|
|
Microsoft Azure Account |
Create a account in the Azure environment where you will migrate workloads. Use the Azure Portal for an account for use in the global environment. Use the Azure China Portal, to create an account for use in that sovereign environment. In PlateSpin Migrate, you must specify an administrator-level user name and password combination for the Azure account. It can be the Account owner or a user in the Contributor role for the specified Subscription. |
|
Azure Subscription ID |
The ID for the Azure Subscription in the specified Azure account that you want to bill for Azure-related costs. An account can have multiple subscriptions. |
|
Contributor user for the subscription created in Azure Active Directory |
A user created as a Contributor for the specified subscription in your Azure Active Directory. |
|
A non-administrative user for PlateSpin Migrate interactions with Azure created in Azure Active Directory |
See Section 9.6, Configuring an Azure User for PlateSpin Migrate to Use. |
|
Application ID |
An ID that represents PlateSpin Migrate as it makes use of the Microsoft Azure API when it replicates or migrates workloads on your behalf to VMs in the target Azure account. See Section 9.5, Registering a Azure Application to Represent PlateSpin Migrate. |
|
Azure Marketplace permission for PlateSpin Migrate Replication Environment images |
For each Subscription that you use as a target container, you must permit the programmatic deployments for the PlateSpin Migrate Replication Environment images for the account. See Enabling Programmatic Deployment of PlateSpin Migrate Replication Environment. |
|
Azure Virtual Network and Subnet |
You must create least one Virtual Network with a Subnet in the specified Subscription. If you have an site-to-site VPN set up, the subnet must be different than the default Gateway Subnet. Network resources are never created automatically by PlateSpin Migrate, so they always must be set up manually in advance. For instructions, refer to Azure documentation. |
|
Azure Storage account |
Your VM disks will use the Azure page blob type of general-purpose storage, which can run on Standard (HDD) or Premium (SSD) storage media. A Standard Storage Account can be used for Azure VM sizes that use Standard or Premium storage media. A Premium Storage Account can be used only for Azure VM sizes that use Premium storage media. If no Azure Storage Account is associated with a subscription, PlateSpin Migrate sets up a Standard general-purpose storage account to use as the datastore for the target VM. The datastore name is based on the Azure Resource Group for the Subscription. If you want full control over your Azure Storage Accounts, configure a Standard or a Premium general-purpose storage account for each Azure Subscription before you begin migrating workloads to Azure. Your storage account is shown as a datastore for the target Azure Subscription in the Migrate Web Interface. For information about Azure Storage Accounts, refer to Azure documentation. |
For more information about setting up your Azure cloud account to work with PlateSpin Migrate, see the white paper Best Practices for Migrating Servers to Microsoft Azure with PlateSpin Migrate
on the PlateSpin Migrate Resources web page.
If you set up an Azure site-to-site VPN (or an Azure Express Route connection) between the premises where your source workloads reside and the target Azure environment, you can deploy your PlateSpin Migrate server on-premises. Before you use PlateSpin Migrate to migrate workloads to Microsoft Azure, ensure that the following cloud access prerequisites are correctly configured and available:
A PlateSpin Migrate license.
A PlateSpin Migrate server deployed on-premise.
A site-to-site VPN connection between your local data center and Microsoft Azure Portal.
For information, see the following Microsoft resources:
A default Gateway Subnet.
The minimum network-related prerequisites for a successful migration are:
The on-premise source workload and the cloud-based target workload must be able to communicate with the PlateSpin Migrate server through HTTPS (TCP/port 443) over the site-to-site VPN connection.
The on-premise PlateSpin Migrate server must be able to communicate with the Microsoft Azure API endpoint through HTTPS (TCP/port 443).
The PlateSpin Migrate server must be able to communicate with the source workloads on the ports that are used for discovery. See Requirements for Discovery and Section 20.6, Discovering Details for Source Workloads.
You can alternatively use the Migrate Agent utility to register source workloads with the Migrate server using HTTPS (TCP/port 443). See Section 20.7, Registering Workloads and Discovering Details with Migrate Agent.
The cloud-based target workload must be able to communicate (target to source) with the on-premise source workload on port 3725 (TCP) over the site-to-site VPN connection.
The port number is configurable. See port 3725 in Section 2.6.2, Requirements for Migration.
If you use Migrate Agent for registration and discovery, the default direction of the replication connection must be reversed (source to target) by changing advanced settings on the Migrate server. See Section 5.9, Configuring the Contact Direction for the Replication Port.
Before you use PlateSpin Migrate to migrate workloads to Microsoft Azure, ensure that the following cloud access prerequisites are correctly configured and available:
A PlateSpin Migrate license
An Azure Marketplace image of the PlateSpin Migrate server in the target Azure environment
NOTE:The cloud-based Migrate server does not require a site-to-site VPN connection between your local data center and Microsoft Azure Portal. When no VPN is provided between the source network and the cloud-based Migrate server, you can use Migrate Agent to register workloads with the cloud-based Migrate server using secure communications over the public Internet. Internet access and public IP addresses are required. For deployment information, see Figure 9-2, Cloud-Based Migrate Server for Automated Migration to Azure.
Specify Static as the allocation method for the public IP address of the Migrate server to ensure that the IP address does not change when the server is restarted.
NOTE:A change in IP address on the PlateSpin Server breaks the heartbeat communications with source workloads.
You cannot specify the actual IP address assigned to the public IP resource. Azure allocates and reserves an IP address from a pool of its available IP addresses in the Azure location where you deploy the Migrate server. The address persists through server restarts. Azure releases the IP address only when you delete the resource or change the resource’s allocation method to Dynamic.
The minimum network-related prerequisites for a successful migration are:
Open TCP port 443 in your network firewall for outbound traffic. The source workload must be able to register (using the Migrate Agent utility) and communicate with the cloud-based PlateSpin Migrate server through HTTPS (TCP/port 443). The PlateSpin Migrate Server uses secure SSL for communications with the workloads you want to migrate.
Open TCP port 3725 in your network firewall for outbound traffic. The on-premise source workload must be able to connect to the cloud-based target workload on TCP port 3725. The PlateSpin Migrate Server uses secure SSL for communications with the workloads you want to migrate.
The direction of the communication (source to target) is automatic, but the port number is configurable.For information about changing the default port setting, see port 3725 in Requirements for Migration.
Allow inbound connections for the Network Security Group (NSG) in Azure on TCP port 3725 (or configured port) for target workloads.
For information about creating and configuring a Network Security Group in Azure, see Filter Network Traffic with Network Security Groups..
Allow inbound connections in the Network Security Group for HTTPS (TCP port 443) and RDP (TCP port 3389) for the cloud-based Migrate server. The <Migrate-server-name>-nsg is created automatically when you deploy the Migrate server in Azure.
If you use PlateSpin Transformation Manager with the cloud-based Migrate server, allow inbound connections in the Network Security Group for STOMP communications (TCP port 61613) related to Event Messaging.
NOTE:No messages are published by Event Messaging unless you open port 61613 on the Migrate server host to allow registration by subscribers, and a PlateSpin Migrate Connector subscribes. See Section 5.6, Enabling Event Messaging for PlateSpin Migration Factory.
Install the Migrate Agent on the source workload, then register the workload with the cloud-based PlateSpin Migrate server. See Registering Workloads and Discovering Details with Migrate Agent.
To download the Migrate Agent, launch the PlateSpin Migrate Web Interface and click the Downloads tab. For information about installing and using the Migrate Agent, see Migrate Agent Utility.