Arctera Application Mobility Service Help

Datacenter goes into a disconnected state because of the timing issue.

Workaround: Restart the gateway service on the gateway, using systemctl restart gatewayd.

In rare cases, parallel execution of multiple plans for the same datacenter fails because of WebSocket re-connection issue.

Sometimes discovery or migration is stuck in a running state, because of WebSocket re-connection issue.

If different business applications use data volumes from the same InfoScale diskgroup and if only a business application is selected for migration, all volumes in that diskgroup are created at target.

All input fields are mandatory while defining a migration plan, but UI is not mandating it. Plan execution without sufficient inputs fails.

In rare cases, for data migration usecase, target configuration shows multiple entries for each task on the plan execution page.

Workaround: Cancel the plan and re-execute it.

For some specific VCS configuration, an all-in-one configuration with volume resource in it is not supported.

If multiple file systems with same size but different EBS types are specified, Application Mobility Service doesn't honor the EBS type while allocation.

Workaround: Keep different sizes for different file systems.

All the passwords in VCS configuration that are migrated from on-premises cluster do not work. Also, all VCS users are not migrated from on-premises cluster.

Workaround: Re-encrypt password manually using vcsencrypt -agent command, and create all VCS users using hauser command. For more details about the VCSEncrypt utility and hauser command, refer to the Cluster Server Administrator's Guide available at SORT.

During cloud infrastructure creation in the New Deployment case, upon cancellation of the failed plan, sometimes the service doesn't clean up the created instances.

Workaround: Log on to the cloud portal and terminate the instances.

If .pem and .pub files are not placed in the same directory, and you provide the path of .pem file for Configuration > Security key, New deployment plan creation fails throwing an undefined error.

Identical storage names and space in between the volumes name for New Deployment plan leads to failure during VCS object creation stage.

After executing the New deployment plan, there is no polling mechanism in place. Users must manually refresh the page to check the deployment status.

When the user selects Discover Applications from the kebab menu on the 'Datacenters' page, they must manually click the refresh button to view the application discovery status.

During retire, sometimes "unconfig replication on the target datacenter" gets hanged because the vradmin -g <dgname> delsec <rvgname> is hanged on the target site.

Workaround: Go to the cluster nodes and restart vras-vradmind service using systemctl restart vras-vradmind.

Gateway service would not start after the upgrade as the upgrade may delete the /var/VRTSgateway/token.json file.

Workaround: Create /var/VRTSgateway directory and re-register the gateway OR restore the backup of token.json file if available.

When selecting an existing CPS configuration for a new deployment, the list may display deleted CP server IPs.

Workaround: Before proceeding with the deployment, verify and validate the IPs in the list against the AWS/Azure console to ensure accuracy.

During New Deployment configuration in case of Azure, some virtual machine types may not support 'Premium LRS' disks which can result in deployment failure

Workaround: Refer to the Azure documentation for the list of VM types that support 'Premium LRS' disks and select an appropriate option from the dropdown.

Certain Azure virtual machine types listed in dropdown do not support the required number of network interfaces.

For example, the Standard_D4s_v5 VM type does not support two LLT links.

Workaround: Refer to the Azure documentation to review the list of supported VM types and their corresponding number of network interfaces. Select an appropriate VM type from the dropdown list based on the required number of LLT links. For instance, a single LLT link can be used with the Standard_D4s_v5 VM type.