Skip to content

Commit 07be13e

Browse files
authored
Merge pull request #197347 from V-SSenthilna/05May-ContentImprovement
Modified the content.
2 parents 0b2f379 + 804317a commit 07be13e

File tree

3 files changed

+19
-14
lines changed

3 files changed

+19
-14
lines changed

articles/site-recovery/azure-to-azure-support-matrix.md

Lines changed: 13 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Support matrix for Azure VM disaster recovery with Azure Site Recovery
33
description: Summarizes support for Azure VMs disaster recovery to a secondary region with Azure Site Recovery.
44
ms.topic: article
5-
ms.date: 11/29/2020
5+
ms.date: 05/05/2022
66
author: Sharmistha-Rai
77
ms.author: sharrai
88
---
@@ -19,14 +19,14 @@ This article summarizes support and prerequisites for disaster recovery of Azure
1919
**Azure portal** | Supported.
2020
**PowerShell** | Supported. [Learn more](azure-to-azure-powershell.md)
2121
**REST API** | Supported.
22-
**CLI** | Not currently supported
22+
**CLI** | Not currently supported.
2323

2424

2525
## Resource move/migrate support
2626

2727
**Resource action** | **Details**
2828
--- | ---
29-
**Move vaults across resource groups** | Not supported
29+
**Move vaults across resource groups** | Not supported.
3030
**Move compute/storage/network resources across resource groups** | Not supported.<br/><br/> If you move a VM or associated components such as storage/network after the VM is replicating, you need to disable and then re-enable replication for the VM.
3131
**Replicate Azure VMs from one subscription to another for disaster recovery** | Supported within the same Azure Active Directory tenant.
3232
**Migrate VMs across regions within supported geographical clusters (within and across subscriptions)** | Supported within the same Azure Active Directory tenant.
@@ -127,7 +127,8 @@ Oracle Linux | 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5,
127127
> [!NOTE]
128128
> For Linux versions, Azure Site Recovery does not support custom OS kernels. Only the stock kernels that are part of the distribution minor version release/update are supported.
129129
130-
**Note: To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch), follow steps mentioned in [this article](service-updates-how-to.md#azure-vm-disaster-recovery-to-azure). This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.
130+
> [!NOTE]
131+
> To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch), follow steps mentioned in [this article](service-updates-how-to.md#azure-vm-disaster-recovery-to-azure). This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.
131132
132133
#### Supported Ubuntu kernel versions for Azure virtual machines
133134

@@ -157,9 +158,11 @@ Oracle Linux | 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5,
157158
20.04 LTS |[9.45](https://support.microsoft.com/topic/update-rollup-58-for-azure-site-recovery-kb5007075-37ba21c3-47d9-4ea9-9130-a7d64f517d5d) | 5.4.0-1058-azure </br> 5.4.0-84-generic </br> 5.4.0-1061-azure </br> 5.4.0-1062-azure </br> 5.4.0-89-generic |
158159
20.04 LTS |[9.44](https://support.microsoft.com/topic/update-rollup-56-for-azure-site-recovery-kb5005376-33f27950-1a07-43e5-bf40-4b380a270ef6) | 5.4.0-26-generic to 5.4.0-60-generic </br> 5.4.0-1010-azure to 5.4.0-1043-azure </br> 5.4.0-1047-azure </br> 5.4.0-73-generic </br> 5.4.0-1048-azure </br> 5.4.0-74-generic </br> 5.4.0-81-generic </br> 5.4.0-1056-azure |
159160

160-
**Note: To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in [this article](service-updates-how-to.md#azure-vm-disaster-recovery-to-azure). This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.
161+
> [!Note]
162+
> To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in [this article](service-updates-how-to.md#azure-vm-disaster-recovery-to-azure). This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.
161163
162-
**Note: For Ubuntu 20.04, we had initially rolled out support for kernels 5.8.* but we have since found issues with support for this kernel and hence have redacted these kernels from our support statement for the time being.
164+
> [!Note]
165+
> For Ubuntu 20.04, we had initially rolled out support for kernels 5.8.* but we have since found issues with support for this kernel and hence have redacted these kernels from our support statement for the time being.
163166
164167
#### Supported Debian kernel versions for Azure virtual machines
165168

@@ -189,7 +192,8 @@ Debian 10 | [9.46](https://support.microsoft.com/topic/update-rollup-59-for-azur
189192
Debian 10 | [9.45](https://support.microsoft.com/topic/update-rollup-58-for-azure-site-recovery-kb5007075-37ba21c3-47d9-4ea9-9130-a7d64f517d5d) | 4.19.0-18-amd64 </br> 4.19.0-18-cloud-amd64
190193
Debian 10 | [9.44](https://support.microsoft.com/topic/update-rollup-57-for-azure-site-recovery-kb5006172-9fccc879-6e0c-4dc8-9fec-e0600cf94094) | 4.19.0-6-amd64 to 4.19.0-16-amd64 </br> 4.19.0-6-cloud-amd64 to 4.19.0-16-cloud-amd64 </br>
191194

192-
**Note: To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in [this article](service-updates-how-to.md#azure-vm-disaster-recovery-to-azure). This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.
195+
> [!Note]
196+
> To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in [this article](service-updates-how-to.md#azure-vm-disaster-recovery-to-azure). This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.
193197
194198
#### Supported SUSE Linux Enterprise Server 12 kernel versions for Azure virtual machines
195199

@@ -211,7 +215,8 @@ SUSE Linux Enterprise Server 15, SP1, SP2 | [9.46](https://support.microsoft.com
211215
SUSE Linux Enterprise Server 15, SP1, SP2 | [9.45](https://support.microsoft.com/topic/update-rollup-58-for-azure-site-recovery-kb5007075-37ba21c3-47d9-4ea9-9130-a7d64f517d5d) | By default, all [stock SUSE 15, SP1, SP2 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported.</br></br> 4.12.14-5.5-azure to 4.12.14-5.47-azure </br></br> 4.12.14-8.5-azure to 4.12.14-8.55-azure </br> 5.3.18-16-azure </br> 5.3.18-18.5-azure to 5.3.18-18.58-azure </br> 5.3.18-18.69-azure
212216
SUSE Linux Enterprise Server 15, SP1, SP2 | [9.44](https://support.microsoft.com/topic/update-rollup-57-for-azure-site-recovery-kb5006172-9fccc879-6e0c-4dc8-9fec-e0600cf94094) | By default, all [stock SUSE 15, SP1, SP2 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported.</br></br> 4.12.14-5.5-azure to 4.12.14-5.47-azure </br></br> 4.12.14-8.5-azure to 4.12.14-8.55-azure </br> 5.3.18-16-azure </br> 5.3.18-18.5-azure to 5.3.18-18.58-azure
213217

214-
**Note: To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in [this article](service-updates-how-to.md#azure-vm-disaster-recovery-to-azure). This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.
218+
> [!Note]
219+
> To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in [this article](service-updates-how-to.md#azure-vm-disaster-recovery-to-azure). This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.
215220
216221
## Replicated machines - Linux file system/guest storage
217222

articles/site-recovery/azure-to-azure-troubleshoot-errors.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -383,7 +383,7 @@ Go to **Virtual machines** > **Settings** > **Extensions** and check for any ext
383383

384384
## VM provisioning state isn't valid (error code 150019)
385385

386-
To enable replication on the VM, its provisioning state must be **Succeeded**. Follow these steps to check the provisioning state:
386+
To enable replication on the VM, its provisioning state must be **Succeeded**. Perform the following steps to check the provisioning state:
387387

388388
1. In the Azure portal, select the **Resource Explorer** from **All Services**.
389389
1. Expand the **Subscriptions** list and select your subscription.
@@ -535,15 +535,15 @@ Delete the replica disk identified in the error message and retry the failed pro
535535
536536
## Enable protection failed as the installer is unable to find the root disk (error code 151137)
537537
538-
This error occurs for Linux machines where the OS disk is encrypted using Azure Disk Encryption (ADE). This is valid issue in Agent version 9.35 only.
538+
This error occurs for Linux machines where the OS disk is encrypted using Azure Disk Encryption (ADE). This is a valid issue in Agent version 9.35 only.
539539
540540
### Possible Causes
541541
542542
The installer is unable to find the root disk that hosts the root file-system.
543543
544544
### Fix the problem
545545
546-
Follow the below steps to fix this issue -
546+
Perform the following steps to fix this issue.
547547
548548
1. Find the agent bits under the directory _/var/lib/waagent_ on RHEL and CentOS machines using the below command: <br>
549549

articles/site-recovery/vmware-azure-tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.custom: MVC
1111

1212
This article describes how to enable replication for on-premises VMware VMs, for disaster recovery to Azure using the [Azure Site Recovery](site-recovery-overview.md) service - Classic.
1313

14-
For information about disaster recovery in Azure Site Recovery Preview, see [this article](vmware-azure-set-up-replication-tutorial-preview.md)
14+
For information about disaster recovery in Azure Site Recovery Preview, see [this article](vmware-azure-set-up-replication-tutorial-preview.md)
1515

1616
This is the third tutorial in a series that shows how to set up disaster recovery to Azure for on-premises VMware VMs. In the previous tutorial, we [prepared the on-premises VMware environment](vmware-azure-tutorial-prepare-on-premises.md) for disaster recovery to Azure.
1717

@@ -43,10 +43,10 @@ Complete the previous tutorials:
4343
## Select a protection goal
4444

4545
1. In **Recovery Services vaults**, select the vault name. We're using **ContosoVMVault** for this scenario.
46-
2. In **Getting Started**, select Site Recovery. Then select **Prepare Infrastructure**.
46+
2. In **Getting Started**, select Site Recovery. Then, select **Prepare Infrastructure**.
4747
3. In **Protection goal** > **Where are your machines located**, select **On-premises**.
4848
4. In **Where do you want to replicate your machines**, select **To Azure**.
49-
5. In **Are your machines virtualized**, select **Yes, with VMware vSphere Hypervisor**. Then select **OK**.
49+
5. In **Are your machines virtualized**, select **Yes, with VMware vSphere Hypervisor**. Then, select **OK**.
5050

5151

5252

0 commit comments

Comments
 (0)