Skip to content

Commit 4f7a592

Browse files
authored
Merge branch 'MicrosoftDocs:main' into main
2 parents 5d3fb38 + 7957672 commit 4f7a592

File tree

5 files changed

+107
-4
lines changed

5 files changed

+107
-4
lines changed

articles/azure-netapp-files/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -431,6 +431,10 @@
431431
href: manage-availability-zone-volume-placement.md
432432
- name: Create cross-zone replication
433433
href: create-cross-zone-replication.md
434+
- name: Relocate
435+
items:
436+
- name: Relocate volume to another region
437+
href: ../operational-excellence/relocation-netapp.md?toc=/azure/azure-netapp-files/toc.json
434438
- name: Develop
435439
items:
436440
- name: REST API

articles/operational-excellence/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,8 @@
100100
href: relocation-automation.md
101101
- name: Azure IoT Hub
102102
href: ../iot-hub/iot-hub-how-to-clone.md?toc=/azure/operational-excellence/toc.json
103+
- name: Azure NetApp Files
104+
href: relocation-netapp.md
103105
- name: Azure Static Web Apps
104106
href: relocation-static-web-apps.md
105107
- name: Power BI

articles/operational-excellence/overview-relocation.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,7 @@ The following tables provide links to each Azure service relocation document. Th
8888
| --- | --- | --- | ---|
8989
[Azure Automation](./relocation-automation.md)| ✅ | ✅| ❌ |
9090
[Azure IoT Hub](/azure/iot-hub/iot-hub-how-to-clone?toc=/azure/operational-excellence/toc.json)| ✅ | ✅| ❌ |
91+
[Azure NetApp Files](./relocation-netapp.md)| ✅ | ✅| ❌ |
9192
[Azure Static Web Apps](./relocation-static-web-apps.md) | ✅ |❌ | ❌ |
9293
[Power BI](/power-bi/admin/service-admin-region-move?toc=/azure/operational-excellence/toc.json)| ✅ |❌ | ❌ |
9394

Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
---
2+
title: Relocate Azure NetApp Files volume to another region
3+
description: Learn how to relocate an Azure NetApp Files volume to another region
4+
author: anaharris-ms
5+
ms.author: anaharris
6+
ms.reviewer: anaharris
7+
ms.date: 08/14/2024
8+
ms.service: azure-automation
9+
ms.topic: how-to
10+
ms.custom:
11+
- subject-relocation
12+
---
13+
14+
# Relocate Azure NetApp Files volume to another region
15+
16+
This article covers guidance for relocating [Azure NetApp Files](../azure-netapp-files/azure-netapp-files-introduction.md) volumes to another region.
17+
18+
[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
19+
20+
21+
## Prerequisites
22+
23+
Before you begin the relocation planning stage, first review the following prerequisites:
24+
25+
- The target NetApp account instance should already be created.
26+
27+
- Source and target regions must be paired regions. To see if they're paired, see [Supported cross-region replication pairs](../azure-netapp-files/cross-region-replication-introduction.md?#supported-region-pairs).
28+
29+
- Understand all dependent resources. Some of the resources could be:
30+
- Microsoft Entra ID
31+
- [Virtual Network](./relocation-virtual-network.md)
32+
- Azure DNS
33+
- [Storage services](./relocation-storage-account.md)
34+
- [Capacity pools](../azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md)
35+
36+
37+
## Prepare
38+
39+
Before you begin the relocation process, make sure to complete the following preparations:
40+
41+
- The target Microsoft Entra ID connection must have access to the DNS servers, AD DS Domain Controllers, or Microsoft Entra Domain Services Domain Controllers that are reachable from the delegated subnet in the target region.
42+
43+
- The network configurations (including separate subnets if needed and IP ranges) should already be planned and prepared
44+
45+
- Turn off replication procedures to disaster recovery region. If you've established a disaster recovery (DR) solution using replication to a DR region, turn off replication to the DR site before initiating relocation procedures.
46+
47+
- Understand the following considerations in regards to replication:
48+
49+
- SMB, NFS, and dual-protocol volumes are supported. Replication of SMB volumes requires a Microsoft Entra ID connection in the source and target NetApp accounts.
50+
51+
- The replication destination volume is read-only until the entire move is complete.
52+
53+
- Azure NetApp Files replication doesn't currently support multiple subscriptions. All replications must be performed under a single subscription.
54+
55+
- There are resource limits for the maximum number of cross-region replication destination volumes. For more information, see [Resource limits for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-resource-limits.md).
56+
57+
## Redeploy
58+
59+
**To redeploy your NetApp resources:**
60+
61+
1. [Create the target NetApp account](../azure-netapp-files/azure-netapp-files-create-netapp-account.md).
62+
63+
1. [Create the target capacity pool](../azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md).
64+
65+
1. [Delegate a subnet in the target region](../azure-netapp-files/azure-netapp-files-delegate-subnet.md). Azure NetApp Files creates a system route to the delegated subnet. Peering and endpoints can be used to connect to the target as needed.
66+
67+
1. Create a data replication volume by following the directions in [Create volume replication for Azure NetApp Files](../azure-netapp-files/cross-region-replication-create-peering.md).
68+
69+
1. [Verify that the health status](../azure-netapp-files/cross-region-replication-display-health-status.md) of replication is healthy.
70+
71+
72+
## Cleanup
73+
74+
Once the replication is complete, you can then safely delete the replication peering the source volume.
75+
76+
To learn how to clean up a replication, see [Delete volume replications or volumes](/azure/azure-netapp-files/cross-region-replication-delete).
77+
78+
79+
## Related content
80+
81+
82+
- [Cross-region replication of Azure NetApp Files volumes](../azure-netapp-files/cross-region-replication-introduction.md)
83+
84+
To learn more about moving resources between regions and disaster recovery in Azure, refer to:
85+
86+
- [Requirements for Active Directory Connections](/azure/azure-netapp-files/create-active-directory-connections#requirements-for-active-directory-connections)
87+
88+
- [Guidelines for Azure NetApp Files network planning](/azure/azure-netapp-files/azure-netapp-files-network-topologies)
89+
90+
- [Fail over to the destination region](/azure/azure-netapp-files/cross-region-replication-manage-disaster-recovery#fail-over-to-destination-volume)
91+
92+
- [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md)
93+
94+
- [Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md)

articles/sentinel/ops-guide.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
---
22
title: Operational guide - Microsoft Sentinel
33
description: Learn about the operational recommendations to help security operations teams to plan and run security activities.
4-
ms.date: 06/28/2024
4+
ms.date: 08/30/2024
55
ms.topic: reference
66
ms.author: cwatson
77
author: cwatson-cat
88
appliesto:
99
- Microsoft Sentinel in the Azure portal and the Microsoft Defender portal
10-
#Customer intent: As a security operations (SOC) team member or security administrator, I want to know what operational activities I should plan to do daily, weekly, and monthly with Microsoft Sentinel to help keep my organization's environment secure.
10+
#Customer intent: As a security operations (SOC) team member or security administrator, I want to know what operational activities I should plan to do daily, weekly, and monthly with Microsoft Sentinel to help keep my organization's environment secure.
1111
---
1212

1313
# Microsoft Sentinel operational guide
1414

15-
This article lists the operational activities that we recommend security operations (SOC) teams and security administrators plan for and run as part of their regular security activities with Microsoft Sentinel.
15+
This article lists the operational activities that we recommend security operations (SOC) teams and security administrators plan for and run as part of their regular security activities with Microsoft Sentinel. For more information about managing your security operations, see [Security operations overview](/security/operations/overview).
1616

1717
## Daily tasks
1818

@@ -48,4 +48,6 @@ Schedule the following activities monthly.
4848

4949
## Related content
5050

51-
- [Deployment guide for Microsoft Sentinel](deploy-overview.md)
51+
- [Security operations overview](/security/operations/overview)
52+
- [Implement Microsoft Sentinel and Microsoft Defender XDR for Zero Trust](/security/operations/siem-xdr-overview)
53+
- [Deployment guide for Microsoft Sentinel](deploy-overview.md)

0 commit comments

Comments
 (0)