Arctera Application Mobility Service Help
Defining migration plan
To define a migration plan, complete the following steps:
- In Applications, select the box next to the application you want to migrate.
The Plan migration option is enabled, and all applications that belong to other clusters are disabled for selection.
- Click Plan migration.
Note:
Click Next to continue configuring the migration plan. You can click Cancel to delete the information you entered, or Save and exit to save the plan. If you click Save and exit, the plan is listed in Migration plans.
- In Basic Details, the applications you selected for migration are listed.
Assign a name for this plan in the Migration plan name.
Select the datacenter to which you want to migrate in Select target datacenter. Only the connected cloud datacenters with the latest gateway RPM version are listed.
You can Save and exit, Cancel, or click Next.
- In Target configuration assign a Resource prefix for this migration. The Application Mobility Service prepends this resource prefix to all cloud resources created through migration plan execution. You can then use this resource prefix to search all cloud resources in the AWS or Azure portal.
Ensure that you meet the following conditions while assigning the resource prefix name:
It should be unique for every plan. Else, migration plan execution fails.
Permissible characters for AWS plan include only alphanumeric characters and hyphens (-).
Permissible characters for Azure plan include only lowercase letters, numerals, and hyphens (-).
Following are the cloud Resources that are created through migration plan execution:
Network interfaces (two per EC2 instance/virtual machine)
AWS EC2 instances or Azure virtual machines (count depends on the size of the source cluster)
EBS or Blob storage volumes (size and count per VM depends on InfoScale volume sizes in the source cluster)
Network security group (allowing inbound traffic only from gateway node and source cluster)
Network load balancer (required during application configuration to allow clients to connect to the application)
In Topology and networking,
If you want to create a cluster in a single zone, select Within availability zone. To create a plan for multiple zones, select Across availability zones.
In the Azure case, one AZ is shown under 'First availability zone' while the remaining two are shown under 'Second availability zone'.
For Availability zones, select the required Eth0 and Eth1 subnet names per availability zone, whereas the Eth2 field is optional.
Note:
Since Azure zones and subnets are independent, you can select same subnets for both the Eth0 cases.
For the Azure case, a read-only Selected resource group field is available. The information is fetched from the gateway registration process.
Select a port number and the protocol to be used for application configuration. Elastic load balancer (ELB) is created with the provided port number and the protocol.
Elastic load balancer (ELB) is required for clients to access applications. You can configure an application manually to listen to the port number.
In Compute, select the EC2 type or Virtual machine type.
Enter the path of the
.pemfile on the cloud Gateway in Security key.Example:
/tmp/VRTS.pemFor more information, refer Prerequisites subsection of the Introduction chapter.
To exercise the Custom Machine Image feature, select the box next to Bring your own image and provide the correct Machine Image ID or name.
Note:
The bandwidth and latency of the network influences the time taken to execute a Custom Machine Image plan. Therefore, if timeouts occur and
Download RPMtask fails, retry it a few times to proceed.In the Storage and file system, select the EBS volume type and EBS volume IOPS for AWS, and Disk types for Azure. Click Next.
Note:
For better application performance, it is recommended to use EBS optimized and ENA enabled/supported EC2 instance types with some dedicated network bandwidth. You can select only one type of EBS volume provisioning. Refer to AWS documentation for correct provisioning of EBS volumes as per application performance requirements.
- In Migration options, select None for manual data migration or Veritas Volume Replicator (VVR) for automated data migration.
If the Veritas Volume Replicator (VVR) option is selected,
Enter virtual IP address under Replication IP of source.
In the Post migration option, choose Retain Source to keep the data migration configuration or Retire Source to clean up the same.
Arctera recommends adding relevant port numbers to the on-premises firewall.
By default, VVR assumes that the on-premises cluster is directly connected to cloud VPC. Hence, IP masquerading does not take place. If you have a router in between which changes the source IP address of the on-premises connection to cloud, add those IP address ranges and VVR port numbers (4145 (TCP/UDP), 8199 (TCP), 8989 (TCP)) in the security groups created for newly deployed EC2 instances.
Note:
The IP address ranges and VVR port numbers can be added before initiating data migration from the portal. For more information about the port numbers used by VVR, refer to the InfoScale Replication Administrator's Guide available at SORT.
- In Review, you can verify all entries. Click Edit if anything needs to be updated, or Save and exit to save the configuration. Else, click Execute to run the plan.
A message 'Plan execution for plan name started successfully' is displayed.
- Click Refresh to update the migration plan list. You can check the overall progress of the operation by clicking the field under 'Status' column against the plan name.