Ensure that the VMs you want to migrate are running a supported OS version which includes
The Mobility service must be installed on each VM you want to replicate.
Site Recovery installs this service automatically when you enable replication for the VM. For automatic installation, you need to prepare an account on the EC2 instances that Site Recovery will use to access the VM. You can use a domain or local account.
You need to have a few resources ready in Azure for the migrated EC2 instances to use. These include a storage account, a vault, and a virtual network.
Images of replicated machines are held in Azure storage. Azure VMs are created from the storage when you failover from on-premises to Azure.
The new vault appears on the Dashboard > All resources, and on the main Recovery Services vaults page.
When the Azure VMs are created after the migration (failover), they're joined to this network.
On the portal page for your vault, select Site Recovery from the Getting Started section and then click Prepare Infrastructure.
Select the following values on the Protection Goal page:
When you are done, click OK to move to the next section.
On the Prepare source page, click + Configuration Server.
Use an EC2 instance running Windows Server 2012 R2 to create a configuration server and register it with your recovery vault.
Configure the proxy on the EC2 instance VM you are using as the configuration server so that it can access the Service URLs.
Download the Microsoft Azure Site Recovery Unified Setup program. You can download it to your local machine and then copy it over to the VM you are using as the configuration server.
Click on the Download button to download the vault registration key. Copy the downloaded file over to the VM you are using as the configuration server.
On the VM, right-click installer you downloaded for the Microsoft Azure Site Recovery Unified Setup and select Run as administrator.
On the VM, run cspsconfigtool.exe to create one or more management accounts on the configuration server. Make sure the management accounts have administrator permissions on the EC2 instances that you want to migrate.
When you are done setting up the configuration server, go back to the portal and select the server you just created for Configuration Server and click OK* to move on to step 3 Target Prepare.
In this section you enter information about the resources you created when you went through the Prepare Azure resources section, earlier in this tutorial.
You need to create a replication policy, before you can enable replication
In Have you completed deployment planning?, select I will do it later from the drop-down and then click OK.
When you are all done with all 5 sections of Prepare infrastructure, click OK.
Enable replication for each VM you want to migrate. When replication is enabled, Site Recovery installs the Mobility service automatically.
Under For on-premises machines and Azure VMs, click Step 1:Replicate application. Complete the wizard pages with the following information and click OK on each page when finished:
1 Source Configure:
2 Target Configure
3 Physical Machines Select
Click + Physical machine and then enter the Name, the IP Address and OS Type of the EC2 instance that you want to migrate and then click OK.
4 Properties Configure Properties
Select the account that you created on the configuration server from the drop-down and click OK.
5 Replication Settings Configure replication settings
Make sure the replication policy selected in the drop-down is myReplicationPolicy and then click OK.
When the wizard is complete, click Enable replication.
You can track progress of the Enable Protection job in Monitoring and reports > Jobs> Site Recovery Jobs. After the Finalize Protection job runs the machine is ready for failover.
When you enable replication for a VM, it can take 15 minutes or longer for changes to take effect and appear in the portal.
When you run a test failover, the following happens:
In the portal, run the test failover as follows:
On the page for your vault, go to Protected items > Replicated Items> click the VM > + Test Failover.
Select a recovery point to use for the failover:
In some scenarios, failover requires additional processing that takes around eight to ten minutes to complete.
Run an actual failover for the EC2 instances to migrate them to Azure VMs.
Right-click each VM > Complete Migration. This finishes the migration process, stops replication for the AWS VM, and stops Site Recovery billing for the VM.
Don't cancel a failover in progress: Before failover is started, VM replication is stopped. If you cancel a failover in progress, failover stops, but the VM won't replicate again.
Zendesk Theme Designed by Diziana
Copyright © Diziana. All Rights Reserved