General Questions - Application Migration Service

General Questions

Can Application Migration Service protect or migrate physical servers?

Because Application Migration Service works at the OS layer it can protect and migrate not only virtual servers but physical ones as well.

What data is stored on and transmitted through Application Migration Service servers?

Application Migration Service store only configuration and log data on the Application Migration Service Service Console's encrypted database. Replicated data is always stored on the customer’s own cloud VPC. The replicated data is encrypted in transit.

What is the Recovery Time Objective (RTO) of Application Migration Service?

The Recovery Time Objective (RTO) of Application Migration Service is typically measured in minutes. The RTO is highly dependent on the OS boot time.

What is the Recovery Point Objective (RPO) of Application Migration Service?

The Recovery Point Objective (RPO) of Application Migration Service is typically in the sub-second range.

What to consider when replicating Active Directory

There are two main approaches when it comes to migrating Active Directory or domain controllers from a disaster:

  1. Replicating the entire environment, including the AD server(s) - in this approach it is recommended to launch the Test or Cutover AD servers first, wait until it's up and running and then launch the other Test or Cutover instances, to make sure the AD servers are ready to authenticate them.

  2. Leaving the AD server(s) in the Source environment - in this approach, the Test or Cutover instances will communicate back to the AD server in the source environment and will take the Source server's place in the AD automatically.

    In this case, it is important to conduct any tests using an isolated subnet in the AWS cloud, so to avoid having the Test or Cutover instances communicate into the source AD server outside of a Cutover.

Does Application Migration Service work with LVM and RAID configurations?

Yes, Application Migration Service works with any such configuration.

What is there to note regarding SAN/NAS Support?

If the disks are represented as block devices on the machine, as most SAN are, Application Migration Service will replicate them transparently, just like actual local disks.

If the disks are mounted over the network, such as an NFS share, as most NAS implementations are, the AWS Replication Agent would need to be installed on the actual NFS server in order to replicate the disk.

Does Application Migration Service support Windows License Migration?

Application Migration Service conforms to the Microsoft Licensing on AWS guidelines.

Can you perform an OS (Operating System) upgrade with Application Migration Service?

No. Application Migration Service copies the entire machine as-is. However, you can copy the data disks exclusively and attach them to a new machine with an upgraded OS.

What are the MGN service quota limits?

The following are the MGN service quota limits:

Name Default Description

Concurrent Jobs in progress

Each supported AWS Region: 20

Launching a Test or Cutover instance, or a cleanup action is considered a "job". This parameter is the maximum number of Jobs that can be run concurrently. Jobs that are "completed" are not counted against this quota.

Max Active Source Servers

Each supported AWS Region: 20

The maximum number of servers that can be actively replicating at any time. You can increase this value to 60. For larger migrations, contact Support.

Max Non-Archived Source Servers

Each supported AWS Region: 4000

This parameter is used for agentless migrations. This is the max number of servers that can be managed by MGN, in non-archived state. This includes the servers that are actively replicating, as well as any servers whose replication has not yet started. The number of actively replicating servers is controlled by the parameter "Max Active Source Servers".
Max Source Servers in a single Job

Each supported AWS Region: 200

Launching a Test or Cutover instance, or a cleanup action is considered a "Job". If you select multiple servers, and perform one of these actions, they are grouped into a single Job. This is the maximum number of servers that can be grouped into a single Job.

Max Source Servers in all Jobs

Each supported AWS Region: 200

Launching a Test or Cutover instance, or a cleanup action is considered a "Job". This is the maximum total number of servers that can be configured in all active Jobs. Jobs that are "completed" are not counted against this quota.
Max Total Source Servers Per AWS Account

Each supported AWS Region: 50,000

This parameter is the maximum total servers, both active and archived, that can be migrated in a single account in each AWS Region. Servers that are deleted, are not counted against this quota.

Max concurrent Jobs per Source Server

Each supported AWS Region: 1

Launching a Test or Cutover instance, or a cleanup action is considered a "Job". This is the maximum number of active Jobs, that can be configured per server. Jobs that are "completed" are not counted against this quota.

You can learn about the MGN service limits in the AWS General Reference

Which Post Launch scripts does MGN support?

MGN can run scripts on a launched Test or Cutover instance. This is done by creating the following folder on the source server and placing the scripts within that folder.

Linux: /boot/post_launch (any files that are marked as executable)

Windows: C:\Program Files (x86)\AWS Replication Agent\post_launch\ (any .exe, .cmd or .bat files)

Once you put these scripts in the above folders on the source server, the folder will be replicated to the Test or Cutover instance and be executed once after the instance boots for the first time.

Note

Post Launch Scripts on Windows run under the Local Service context. Post Launch Scripts on Linux run under the 'root' user.

Uninstalling VMTools from Windows

The following script can be utilized to uninstall VMTools post migration from Windows. This is a powershell script. It needs to be wrapped by a .CMD file, as powershell scripts are not ran automatically by the post_launch.

$regpath = "HKLM:\Software\Microsoft\Windows\CurrentVersion\uninstall"

Get-childItem $regpath | % {

$keypath = $_.pschildname

$key = Get-Itemproperty $regpath\$keypath

if ($key.DisplayName -match "VMware Tools") {

$VMwareToolsGUID = $keypath

}

MsiExec.exe /x $VMwareToolsGUID /qn /norestart

}