Skip to content

Latest commit

 

History

History
277 lines (146 loc) · 12.6 KB

germany-migration-compute.md

File metadata and controls

277 lines (146 loc) · 12.6 KB
title description author ms.author ms.date ms.topic ms.custom
Migration from Azure Germany compute resources to global Azure
Provides help for migrating compute resources
gitralf
ralfwi
8/13/2018
article
bfmigrate

Compute

Compute IaaS

Unfortunately, no direct migration from Azure Germany to global Azure is possible. But there's more than one way to "duplicate" your VMs.

Duplicate with Azure Site Recovery

Azure Site Recovery can help you migrate your VMs from Azure Germany to global Azure. Since source and target are in different tenants, you can't use the normal Azure Disaster Recovery option available for VMs. The trick here is to set up a Site Recovery vault in the target environment (global Azure), and to proceed like moving a physical server into Azure. Choose a replication path from not virtualized to Azure global and - after the replication finished - do a failover.

Note

These steps are the same that you would take to migrate a physical server running on-premise to Azure.

There's a good tutorial for Site Recovery available. For a quick overview, here's a shorter and slightly adopted version:

Install a Configuration/Process Server in your source environment to build the images of the servers. Then replicate the images to the Recovery Service Vault in your target environment. This is all done by the Configuration Server, and there's no need to touch the single servers.

  • Sign in to the Azure Germany Portal
  • Compare the OS version of the VMs you want to migrate against the support matrix
  • Set up a new VM in your source VNet acting as the configuration server:
    • Choose DS4v3 or higher (4-8 cores, 16 GB Memory)
    • Attach an additional disk with at least 1 TB available space (for the VM images)
    • Use Windows Server 2012R2 or higher
  • Make sure ports 443 and 9443 are open for the subnet in both directions
  • Sign in to this new VM (ConfigurationServer)
  • From within your remote desktop session, sign in to the global Azure portal with your global Azure credentials
  • Set up a VNet where the replicated VMs will run
  • Create a storage account
  • Set up the Recovery Service Vault
  • Define Protection goal (To Azure -- Not virtualized/other)
  • Download Recovery Unified Setup installation file (Prepare Infrastructure > Source). When you opened the portal URL from within the ConfigurationServer, the file will be downloaded to the correct server. If not, upload the install file to the ConfigurationServer.
  • Download the vault registration key (and upload to ConfigurationServer like above if necessary)
  • Run the Recovery Unified Setup installation on the ConfigurationServer
  • Set up the target environment (you should still be signed in to the target portal)
  • Define replication policy
  • Start replication

When replication has succeeded the first time, you should test the scenario by doing a test failover, verifying and deleting the test. Your final step is to do the real failover.

Caution

There is no synchronization back to the source VM. If you want to re-migrate, you must clean up everything and start again at the beginning!

Duplicate with Resource Manager template export/import

You can export the Resource Manager template used for the deployment to your local machine. Edit the template to change location and other parameters or variables, and then redeploy in Azure global.

Important

Change Location, Key Vault secrets, certs, and other GUIDs to be consistent with new region.

Export the Resource Manager template in the portal by selecting the resource group. Click deployments and select the most recent deployment. Click Template in the left menu and download it.

You get a zip file with several files in it. The PowerShell, CLI, Ruby, or .NET scripts help you to deploy your template. The file parameters.json has all the input from the last deployment, most likely you have to change some settings here. Edit the template.json file if you only want to redeploy a subset of the resources.

Next steps

Reference

Cloud Services

Cloud Services can be redeployed by providing the .cspkg and .cscfg definitions again.

By portal

  • Create a new Cloud Service with your .cspkg and .cscfg.
  • Update the CNAME or A record to point traffic to the new cloud service.
  • Delete your old cloud service in Azure Germany after your traffic is pointing to the new Cloud Service.

By PowerShell

New-AzureService -ServiceName <yourServiceName> -Label <MyTestService> -Location <westeurope>
New-AzureDeployment -ServiceName <yourServiceName> -Slot <Production> -Package <YourCspkgFile.cspkg> -Configuration <YourConfigFile.cscfg>
    Remove-AzureService -ServiceName <yourOldServiceName>

By REST API

https://management.core.windows.net/<subscription-id>/services/hostedservices
https://management.core.windows.net/<subscription-id>/services/hostedservices/<cloudservice-name>/deploymentslots/production
https://management.core.cloudapi.de/<subscription-id>/services/hostedservices/<old-cloudservice-name>

References

Service Fabric

It's not possible to migrate Service Fabric resources from Azure Germany to global Azure. You must re-deploy in the new environment.

You can gather some information about your current service fabric environment by using PowerShell cmdlets. You find all cmdlets related to service fabric by entering Get-Help *ServiceFabric* in PowerShell.

Next steps

References

Batch

It's not possible to migrate Batch account data from one region to another. The account may have running VMs associated with it, interacting with data in storage accounts, databases, or other storage systems.

Redeploy your deployment scripts, templates, or code in the new region, including:

Next steps

References

Functions

Migration of Functions between Azure Germany and global Azure isn't supported at this time. The recommended approach is to export Resource Manager template, change the location, and redeploy to target region.

Important

Change Location, Key Vault secrets, certs, and other GUIDs to be consistent with new region (location).

Next steps

References

Virtual Machines Scale Set

The recommended approach is to export the Resource Manager template, adopt it to the new environment, and redeploy it to target region. You should just export the base template and redeploy it in the new environment, as individual VMSS instances should all be the same.

Important

Change Location, Key Vault secrets, certs, and other GUIDs to be consistent with the new region.

Next steps

References

App Service - Web Apps

The migration of App Services from Azure Germany to global Azure isn't supported at this time. The recommended approach is to export as Resource Manager template and redeploy after changing the location property to the new destination region.

Important

Change Location, Key Vault secrets, certs, and other GUIDs to be consistent with new region (location).

Next steps

References