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

General workflow

The overall workflow for the Application Mobility Service functioning is summarized in this section. Before initiating the cluster deployment or application migration activities, Arctera recommends going through it for hassle-free operation.

  • Contact a Arctera representative and request the necessary access to the Application Mobility Service portal. It can also be directly requested from the Application Mobility portal.

  • Get your Arctera account credentials which are used for logging into the portal.

  • Ensure that you have a Cloud Service Provider account (AWS or Azure). In the case of AWS cloud services, share your target AWS account ID and region with a Arctera representative to make sure that required AMIs 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.

  • Create a target virtual private cloud (VPC) or VNet with DNS resolution and hostnames enabled in your AWS/Azure account. For more information, refer Amazon VPC User Guide or Azure Virtual Network documentation.

  • Set up and connect the gateway nodes by registering them as on-premises and cloud datacenters.

  • Log on to the Application Mobility Service portal using your Arctera account credentials.

Further, depending upon the use case (Applicant Migration or Cluster Deployment), follow the steps outlined below:

Application Migration
  1. Discover the applications on the datacenters associated with the registered gateway.
  2. Create a Migration Plan depicting the terms of configuration.
  3. Execute the Migration Plan. This includes the following steps:
    • Create target infrastructure

    • Deploy the application

    • Configure data replication (optional)

    • Switchover to target cloud instances

Cluster Deployment
  1. Create a deployment plan.

    Note:

    Ensure that the target datacenter where the cluster is deployed is in 'connected' state and has the latest gateway RPM version.

  2. Provide basic details of the deployment plan.
  3. Examine the default settings of configuration inputs for the selected deployment plan or update them, if necessary.
  4. Review and execute the deployment plan.

Once the migration or deployment plan is executed, perform the steps listed below to ensure your resilient cluster and applications are fully installed and are ready to go:

  • Configure CPS-based fencing if it was not included in the deployment plan

  • Online the data mounts (VCS service group - CFSMount)

  • Install the application

  • Configure the application agent, if any (optional)

You can view the overall statistics of different migration and deployment operations on the Application Mobility Service dashboard.