Arctera Application Mobility Service Help

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.2, 7.4.2, 7.4.1, 1.0)
Platform: Linux

Prerequisites

Before you start application migration or cluster deployment, ensure to meet the following conditions:

  • Ensure that a Cloud Gateway is deployed in the target cloud environment, is in a connected state, and has the latest gateway RPM version.

  • For AWS, save an Amazon EC2 key pair (.pem file) on the gateway. During migration plan execution, this key pair is used for creation of EC2 instances and then to connect those through SSH.

  • In the case of Azure,

    • Download the SSH key pair (.pem file) from Azure portal while creating, and copy the .pub file from your Azure account.

    • Alternatively, generate your own key pair using an SSH key generator.

    • Use this key pair during the execution of the migration plan to create Azure virtual machines and establish SSH connections.

    • .pem and .pub files should be in the same location.

  • In case of AWS, create the following subnets, one for each target availability zone:

    • Private subnet (Eth0)

    • LLT private subnet (Eth1)

    • LLT2 private subnet (Eth2) (Optional)

    In case of Azure, the above subnets are only to be created once as Azure subnets, by default, span all availability zones.

  • Private Machine Images are available in the AWS or Azure account respectively for the provided target region. Azure Machine Images are readily available on the Azure platform whereas you must contact the Arctera representative or Technical Support to ensure that required Amazon Machine Images are privately shared with your AWS account.

    Note:

    The application migration or cluster deployment operation fails if the above details are not shared with the Arctera representative.

  • In the case of existing CPS-based Fencing, ensure to meet the following conditions:

    • To use existing CP servers, create them first using a new deployment plan in AWS or Azure. Once created, these CP servers can be reused for subsequent deployments.

    • Ensure the required number ('n') of CP servers is available in AWS or Azure to configure existing 'n'-CPS-based fencing ('n = 1' or '3').

    • From the dropdown list, select the IPs of existing CP servers that were deployed using the same gateway.

  • In the case of application migration using Veritas Volume Replicator (VVR), ensure there is a site-to-site VPN connectivity between source cluster network to target VPC with following port numbers open:

    • UDP/TCP: 4145

    • TCP: 8189, 8989, 22

    Note:

    For more information about the ports used by VVR, refer the Overview section of the Migration chapter.