|
1 | 1 | --- |
2 | 2 | title: Move a Service Fabric Mesh application to another region |
3 | | -description: The meta-description is not crawled for search rank, but is displayed in the browser. Include the words "move" and "region". |
| 3 | +description: You can move Service Fabric Mesh resources by deploying a copy of your current template to a new Azure region. |
4 | 4 | author: erikadoyle |
5 | 5 | ms.author: edoyle |
6 | 6 | ms.topic: how-to |
7 | 7 | ms.date: 01/14/2020 |
8 | | - |
| 8 | +ms.custom: subject-moving-resources |
| 9 | +#Customer intent: As an Azure service administrator, I want to move my Service Fabric Mesh resources to another Azure region. |
9 | 10 | --- |
10 | 11 | # Move a Service Fabric Mesh application to another Azure region |
11 | 12 |
|
12 | | -Introductory paragraph. |
13 | | -<!---Required: |
14 | | -- Lead with a intro that sets the context to help customers understand why they might move resources to another region. |
15 | | -- Answer the fundamental “why would I want to do this?” question. |
16 | | -- Exact detail and scope of the intro will depend on your service. |
17 | | -- Sample paragraph: |
18 | | ----> |
19 | 13 | This article describes how to move your Service Fabric Mesh application and its resources to a different Azure region. You might move your resources to another region for a number of reasons. For example, in response to outages, to gain features or services available in specific regions only, to meet internal policy and governance requirements, or in response to capacity planning requirements. |
20 | 14 |
|
| 15 | + [Service Fabric Mesh does not support](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/region-move-support#microsoftservicefabricmesh) the ability to directly move resources across Azure regions. However, you can move resources indirectly by deploying a copy of your current Azure Resource Manager (ARM) template to the new target region and then redirecting ingress traffic and dependencies to the newly created Service Fabric Mesh application. |
| 16 | + |
21 | 17 | ## Prerequisites |
22 | | -<!---Required: |
23 | | -- Mention anything that must be in place before starting to move resources to another region. |
24 | | -- These might be requirements or limitations to be aware of, checks that should be made, or steps that must be taken before the move. |
25 | | -begin. |
26 | | ----> |
27 | | - |
28 | | -## Prepare and move resources |
29 | | -<!---Required: |
30 | | -These are all the steps you need to do to prepare and actually move the resources. |
31 | | -- As an example, you might describe how to export a resource group and then import it into the new region. |
32 | | -- The actual steps will depend on the solution your service uses to shift resources across regions. |
33 | | ----> |
34 | | - |
35 | | -## Verify the move |
36 | | -<!---Required: |
37 | | -Short instructions to check that the resources now appear in the target region. |
38 | | ----> |
39 | | - |
40 | | - |
41 | | -## Discard target resources |
42 | | -<!---Required: |
43 | | -This section contains instructions that explain how to remove the target resources after they've been moved from the source region. IT's optional, but useful if customers do a move as a POC only, or if they no longer need the resources after the move. |
44 | | ----> |
| 18 | + |
| 19 | +* Ingress controller (such as [Application Gateway](https://docs.microsoft.com/en-us/azure/application-gateway/)) to serve as an intermediary for routing traffic between clients and your Service Fabric Mesh application |
| 20 | +* Service Fabric Mesh (Preview) availability in the target Azure region (`westus`, `eastus`, or `westeurope`) |
| 21 | + |
| 22 | +## Prepare |
| 23 | + |
| 24 | +1. Take a "snapshot" of the current state of your Service Fabric Mesh application by exporting the Azure Resource Manager template and parameters from the most recent deployment. To do this, follow the steps in [Export template after deployment](https://docs.microsoft.com/azure/azure-resource-manager/templates/export-template-portal#export-template-after-deployment) using the Azure portal. You can also use [Azure CLI](../management/manage-resource-groups-cli.md#export-resource-groups-to-templates), [Azure PowerShell](../management/manage-resource-groups-powershell.md#export-resource-groups-to-templates), or [REST API](/rest/api/resources/resourcegroups/exporttemplate). |
| 25 | + |
| 26 | +2. If applicable, [export other resources in the same resource group](https://docs.microsoft.com/azure/azure-resource-manager/templates/export-template-portal#export-template-from-a-resource-group) for redeployment in the target region. |
| 27 | + |
| 28 | +3. Review (and edit, if needed) the exported template to ensure the existing property values are the ones you want to use in the target region. The new `location` (Azure region) is a parameter that you will supply during redeployment. |
| 29 | + |
| 30 | +## Move |
| 31 | + |
| 32 | +1. Create a new resource group (or use an existing one) in the target region. |
| 33 | + |
| 34 | +2. With your exported template, follow the steps in [Deploy resources from custom template](https://docs.microsoft.com/azure/azure-resource-manager/templates/deploy-portal#deploy-resources-from-custom-template) using the Azure portal. You can also use [Azure CLI](https://docs.microsoft.com/azure/azure-resource-manager/templates/deploy-cli), [Azure PowerShell](https://docs.microsoft.com/azure/azure-resource-manager/templates/deploy-powershell), or [REST API](https://docs.microsoft.com/azure/azure-resource-manager/templates/deploy-rest). |
| 35 | + |
| 36 | +3. For guidance on moving related resources such as [Azure Storage accounts](../storage/common/storage-account-move), refer to guidance for individual services listed under the topic [Moving Azure resources across regions](../azure-resource-manager/management/move-region.md). |
| 37 | + |
| 38 | +## Verify |
| 39 | + |
| 40 | +1. When the deployment is complete, test the application endpoint(s) to verify the functionality of your application. |
| 41 | + |
| 42 | +2. You can also verify the status of your application by checking the application status ([az mesh app show](https://docs.microsoft.com/cli/azure/ext/mesh/mesh/app?view=azure-cli-latest#ext-mesh-az-mesh-app-show)) and reviewing the application logs and ([az mesh code-package-log](https://docs.microsoft.com/cli/azure/ext/mesh/mesh/code-package-log?view=azure-cli-latest)) commands using the [Azure Service Fabric Mesh CLI](https://docs.microsoft.com/azure/service-fabric-mesh/service-fabric-mesh-quickstart-deploy-container#set-up-service-fabric-mesh-cli). |
| 43 | + |
| 44 | +## Commit |
| 45 | + |
| 46 | +Once you've confirmed equivalent functionality of your Service Fabric Mesh application in the target region, configure your ingress controller (for example, [Application Gateway](../application-gateway/redirect-overview.md)) to redirect traffic to the new application. |
45 | 47 |
|
46 | 48 | ## Clean up source resources |
47 | | -<!---Required: |
48 | | -Instructions in this section describe how to clean up/delete the resources in the source region, after they've been moved and verified in the target region. |
49 | | ----> |
50 | 49 |
|
| 50 | +To complete the move of the Service Fabric Mesh application, [delete the source application and/or parent resource group](../azure-resource-manager/management/delete-resource-group.md). |
51 | 51 |
|
52 | 52 | ## Next steps |
53 | 53 |
|
54 | | -<!---Optional |
55 | | -Required if it makes sense for your service |
56 | | ----> |
| 54 | +* [Move Azure resources across regions](../azure-resource-manager/management/move-region.md) |
| 55 | +* [Support for moving Azure resources across regions](../azure-resource-manager/management/region-move-support.md) |
| 56 | +* [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md) |
| 57 | +* [Move operation support for resources](../azure-resource-manager/management/move-support-resources.md |
| 58 | +) |
0 commit comments