The Microsoft Migration Accelerator for Azure (MA), enables easy
migration of physical and virtual servers running on VMWare, Hyper-V or
AWS cloud environments to Azure. In preview release of MA, workload
instances running on any edition of Windows (2008 or R2 or 2012 or R2)
and Linux (CentOS 6.4 or 6.5 and Oracle Linux 6.5) Operating systems are
supported.
MA provides online full-system migration including the OS and application data with significantly improved migration times. For example, a sample 6 server SharePoint farm configured with single disk on each server can be migrated to Azure in less than about 30 minutes.
You can choose particular instance/s from the discovered list of workload for migration. After the selection is made, installation of a software module called Mobility Service on the workload instances is required. The MA web portal provides a user-friendly UI driven remote cloud orchestrated installation on to the selected servers. Optionally, you can also install the Mobility Service by directly downloading and installing it on the workload instance/s. Mobility Service is required to capture data in real time enabling, sync selected volumes, filter all writes made to protected volumes, defining consistent bookmarks consistency points, and much more.
After installing Mobility Service, you can start configuring replication for the selected server instances using the Protection UI option on the web portal. MA captures the complete blueprint of the protected servers as part of discovery and uses this to provision the best suitable instance sizing for the environment within Azure. The target VHDs in the Azure are provisioned by the MA web portal as part of the orchestration. Once the replication is setup, synchronization of the on premise server disk to the target VHD in the Azure begins.
Mobility Service on the source Enterprise workload replicates the data to the cloud and simultaneously tracks and captures new data changes in real-time. The captured deltas are buffered in the Process Server until the time the initial seed of the disk is complete. The deltas from the buffer are applied to the target disk in the same order that the changes occurred on the source disk after the initial seeding of data is complete. While applying these new writes to target, the software also records old writes within retention window that provides capability to migrate to any historical data points.
In addition to replicating data, the Mobility Service is capable of bookmarking servers that are in replication. It also has the capability to orchestrate application consistency bookmark on an n- tier application spread across multiple server instances. These bookmarks are additional text strings that are recorded in retention window and one can migrate to any of these bookmarks at later point of time.
Mobility Service: Mobility Service is a light weight Scout Agent that is installed on each of the servers in source Enterprise. Mobility Service is required to capture data in real time enabling, sync selected volumes, filter all writes made to protected volumes, defining consistent bookmarks consistency points.
Master Target (MT): A dedicated VM created on the Azure to act as a target for replication is called Master Target. It is used as a target for replicating disks from source Enterprise. Master Target also contains the retention data. Retention data is the log of prior changes allowing you to recover a VM to prior point in time or to a prior application consistent point. One Master Target can accommodate migration of 15 disks to Azure. Depending on this data additional Master Targets are required to accommodate migration of more number of disks.
Process Server (PS): PS is installed on source Enterprise. Process Server facilitates communication between Mobility Service on source Enterprise and MT on Azure. It provides caching, queuing, compression, encryption and bandwidth management from itself to the Master Target.
MA: The MA is a multitenant portal. This portal enables you to discover source Enterprise and migrate this source Enterprise to Azure.
Configuration Server (CS): CS is deployed in the Azure. It provides user interface and feeds data from MT to MA. Regular synchronization happens between CS and MA.
MA supports migration of single
standalone server instances as well as a group of servers that run
distributed multi-tier production applications.
MA provides online full-system migration including the OS and application data with significantly improved migration times. For example, a sample 6 server SharePoint farm configured with single disk on each server can be migrated to Azure in less than about 30 minutes.
How MA Works
MA automates all critical processes required to migrate a source workload within an Enterprise into Azure. It discovers the source Enterprise including ESX, Hyper-V, AWS and physical servers. The workload on source Enterprise is discovered using Process Server on source Enterprise which is connected to MA portal. The discovered instances are listed in MA portal under the site name as provided by you.You can choose particular instance/s from the discovered list of workload for migration. After the selection is made, installation of a software module called Mobility Service on the workload instances is required. The MA web portal provides a user-friendly UI driven remote cloud orchestrated installation on to the selected servers. Optionally, you can also install the Mobility Service by directly downloading and installing it on the workload instance/s. Mobility Service is required to capture data in real time enabling, sync selected volumes, filter all writes made to protected volumes, defining consistent bookmarks consistency points, and much more.
After installing Mobility Service, you can start configuring replication for the selected server instances using the Protection UI option on the web portal. MA captures the complete blueprint of the protected servers as part of discovery and uses this to provision the best suitable instance sizing for the environment within Azure. The target VHDs in the Azure are provisioned by the MA web portal as part of the orchestration. Once the replication is setup, synchronization of the on premise server disk to the target VHD in the Azure begins.
Mobility Service on the source Enterprise workload replicates the data to the cloud and simultaneously tracks and captures new data changes in real-time. The captured deltas are buffered in the Process Server until the time the initial seed of the disk is complete. The deltas from the buffer are applied to the target disk in the same order that the changes occurred on the source disk after the initial seeding of data is complete. While applying these new writes to target, the software also records old writes within retention window that provides capability to migrate to any historical data points.
In addition to replicating data, the Mobility Service is capable of bookmarking servers that are in replication. It also has the capability to orchestrate application consistency bookmark on an n- tier application spread across multiple server instances. These bookmarks are additional text strings that are recorded in retention window and one can migrate to any of these bookmarks at later point of time.
Components
The following components are required for Cloud Services to work.Mobility Service: Mobility Service is a light weight Scout Agent that is installed on each of the servers in source Enterprise. Mobility Service is required to capture data in real time enabling, sync selected volumes, filter all writes made to protected volumes, defining consistent bookmarks consistency points.
Master Target (MT): A dedicated VM created on the Azure to act as a target for replication is called Master Target. It is used as a target for replicating disks from source Enterprise. Master Target also contains the retention data. Retention data is the log of prior changes allowing you to recover a VM to prior point in time or to a prior application consistent point. One Master Target can accommodate migration of 15 disks to Azure. Depending on this data additional Master Targets are required to accommodate migration of more number of disks.
Process Server (PS): PS is installed on source Enterprise. Process Server facilitates communication between Mobility Service on source Enterprise and MT on Azure. It provides caching, queuing, compression, encryption and bandwidth management from itself to the Master Target.
MA: The MA is a multitenant portal. This portal enables you to discover source Enterprise and migrate this source Enterprise to Azure.
Configuration Server (CS): CS is deployed in the Azure. It provides user interface and feeds data from MT to MA. Regular synchronization happens between CS and MA.
Thanks & Regards
Srikanth Goud
Virtualization Administrator
No comments:
Post a Comment