Skip to content

Commit 762db40

Browse files
authored
Merge pull request #218595 from Sharmistha-Rai/main
Undo changes related to deprecation and added govt cloud URLs
2 parents 9b2aab8 + 80b1524 commit 762db40

File tree

3 files changed

+18
-6
lines changed

3 files changed

+18
-6
lines changed

articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ You deploy an on-premises replication appliance when you use [Azure Site Recover
2929
--- | ---
3030
CPU cores | 8
3131
RAM | 32 GB
32-
Number of disks | 3, including the OS disk - 80 GB, data disk 1 - 620 GB, data disk 2 - 620 GB
32+
Number of disks | 2, including the OS disk - 80 GB and a data disk - 620 GB
3333

3434
### Software requirements
3535

@@ -63,13 +63,23 @@ Ensure the following URLs are allowed and reachable from the Azure Site Recovery
6363
|`*.microsoftonline.com `|Create Azure Active Directory (AD) apps for the appliance to communicate with Azure Site Recovery. |
6464
|management.azure.com |Create Azure AD apps for the appliance to communicate with the Azure Site Recovery service. |
6565
|`*.services.visualstudio.com `|Upload app logs used for internal monitoring. |
66-
|`*.vault.azure.net `|Manage secrets in the Azure Key Vault. Note: Ensure machines to replicate have access to this. |
66+
|`*.vault.azure.net `|Manage secrets in the Azure Key Vault. Note: Ensure that the machines which need to be replicated have access to this. |
6767
|aka.ms |Allow access to also known as links. Used for Azure Site Recovery appliance updates. |
6868
|download.microsoft.com/download |Allow downloads from Microsoft download. |
6969
|`*.servicebus.windows.net `|Communication between the appliance and the Azure Site Recovery service. |
7070
|`*.discoverysrv.windowsazure.com `<br><br>`*.hypervrecoverymanager.windowsazure.com `<br><br> `*.backup.windowsazure.com ` |Connect to Azure Site Recovery micro-service URLs.
7171
|`*.blob.core.windows.net `|Upload data to Azure storage which is used to create target disks. |
7272

73+
Ensure the following URLs are allowed and reachable from the Azure Site Recovery replication appliance for continuous connectivity, when enabling replication to a government cloud:
74+
75+
| **URL for Fairfax** | **URL for Mooncake** | **Details** |
76+
| ------------------------- | -------------------------------------------| -------------------------------------------|
77+
| `login.microsoftonline.us/*` <br> `graph.microsoftazure.us` | `login.chinacloudapi.cn/*` <br> `graph.chinacloudapi.cn` | To sign-in to your Azure subscription. |
78+
| `portal.azure.us` | `portal.azure.cn` |Navigate to the Azure portal. |
79+
| `*.microsoftonline.us/*` <br> `management.usgovcloudapi.net` | `*.microsoftonline.cn/*` <br> `management.chinacloudapi.cn/*` | Create Azure AD apps for the appliance to communicate with the Azure Site Recovery service. |
80+
| `*.hypervrecoverymanager.windowsazure.us` <br> `*.migration.windowsazure.us` <br> `*.backup.windowsazure.us` | `*.hypervrecoverymanager.windowsazure.cn` <br> `*.migration.windowsazure.cn` <br> `*.backup.windowsazure.cn` | Connect to Azure Site Recovery micro-service URLs. |
81+
|`*.vault.usgovcloudapi.net`| `*.vault.azure.cn` |Manage secrets in the Azure Key Vault. Note: Ensure that the machines which need to be replicated have access to this. |
82+
7383

7484
### Folder exclusions from Antivirus program
7585

@@ -93,7 +103,7 @@ C:\Program Files\Microsoft Azure VMware Discovery Service <br>
93103
C:\Program Files\Microsoft On-Premise to Azure Replication agent <br>
94104
E:\ <br>
95105

96-
#### If Antivirus software is active on Source machine
106+
#### If Antivirus software is active on source machine
97107

98108
If source machine has an Antivirus software active, installation folder should be excluded. So, exclude folder C:\ProgramData\ASR\agent for smooth replication.
99109

articles/site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Ensure the following for a successful movement of replicated item:
4343

4444
Ensure the following before you move from classic architecture to modernized architecture:
4545

46-
- [Create a Recovery Services vault](./azure-to-azure-tutorial-enable-replication.md#create-a-recovery-services-vault) and ensure the experience has [not been switched to classic](./vmware-azure-common-questions.md#how-do-i-use-the-classic-experience-in-the-recovery-services-vault-rather-than-the-modernized-experience).
46+
- [Create a Recovery Services vault](./azure-to-azure-tutorial-enable-replication.md#create-a-recovery-services-vault) and ensure the experience has [not been switched to classic](./vmware-azure-common-questions.md#how-do-i-use-the-classic-experience-in-the-recovery-services-vault-rather-than-the-modernized-experience)
4747
- [Deploy an Azure Site Recovery replication appliance](./deploy-vmware-azure-replication-appliance-modernized.md).
4848
- [Add the on-premises machine’s vCenter Server details](./deploy-vmware-azure-replication-appliance-modernized.md) to the appliance, so that it successfully performs discovery.  
4949

articles/site-recovery/vmware-azure-common-questions.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,6 @@ This article answers common questions that might come up when you deploy disaste
1717

1818
### How do I use the classic experience in the Recovery Services vault rather than the modernized experience?
1919

20-
2120
A new and more reliable way to protect VMware virtual machines using the Azure Site Recovery replication appliance is now generally available. When a new Recovery Services vault is created, by default the modernized experience will be selected.
2221

2322

@@ -26,7 +25,7 @@ To change the experience -
2625
1. Open the vault on Azure portal.
2726
2. Click on **Site Recovery** in the **Getting started** section.
2827
3. Click on the banner on top of this page.
29-
28+
3029
[![Modify VMware stack step 1](./media/vmware-azure-common-questions/change-stack-step-1.png)](./media/vmware-azure-common-questions/change-stack-step-1.png#lightbox)
3130

3231
4. This will open the experience selection blade. Select the classic experience if you want to use configuration server and then click on **OK**. If not, close the pane.
@@ -36,6 +35,9 @@ To change the experience -
3635
> [!NOTE]
3736
> Note that once the experience type has been switched to classic from modernized, it cannot be switched again in the same Recovery Services vault. Ensure that the desired experience is selected, before saving this change.
3837
38+
### Can I migrate to the modernized experience?
39+
40+
All VMware VMs or Physical servers which are being replicated using the classic experience can be migrated to the modernized experience. Check the details [here](move-from-classic-to-modernized-vmware-disaster-recovery.md) and follow the [tutorial](how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md).
3941

4042
### What do I need for VMware VM disaster recovery?
4143

0 commit comments

Comments
 (0)