Skip to content

Commit 1b2d8a8

Browse files
author
Ankita Dutta
committed
PR fixes
1 parent 1aa5573 commit 1b2d8a8

File tree

3 files changed

+6
-5
lines changed

3 files changed

+6
-5
lines changed
-13.5 KB
Loading

articles/site-recovery/site-recovery-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Site Recovery can manage replication for:
4141
**VMware VM replication** | You can replicate VMware VMs to Azure using the improved Azure Site Recovery replication appliance that offers better security and resilience than the configuration server. For more information, see [Disaster recovery of VMware VMs](vmware-azure-about-disaster-recovery.md).
4242
**On-premises VM replication** | You can replicate on-premises VMs and physical servers to Azure. Replication to Azure eliminates the cost and complexity of maintaining a secondary datacenter.
4343
**Workload replication** | Replicate any workload running on supported Azure VMs, on-premises Hyper-V and VMware VMs, and Windows/Linux physical servers.
44-
**Data resilience** | Site Recovery orchestrates replication without intercepting application data. When you replicate to Azure, data is stored in Azure storage, with the resilience that provides. When failover occurs, Azure VMs are created based on the replicated data. This also applies to Public MEC to Azure region Azure Site Recovery scenario. In case of Azure Public MEC to Public MEC Azure Site Recovery scenario (the ASR functionality for Public MEC is in preview state), data is stored in the Public MEC.
44+
**Data resilience** | Site Recovery orchestrates replication without intercepting application data. When you replicate to Azure, data is stored in Azure storage, with the resilience that provides. When failover occurs, Azure VMs are created based on the replicated data. This also applies to Public MEC to Azure region Azure Site Recovery scenario. In case of Azure Public MEC to Public MEC Azure Site Recovery scenario (the Azure Site Recovery functionality for Public MEC is in preview state), data is stored in the Public MEC.
4545
**RTO and RPO targets** | Keep recovery time objectives (RTO) and recovery point objectives (RPO) within organizational limits. Site Recovery provides continuous replication for Azure VMs and VMware VMs, and replication frequency as low as 30 seconds for Hyper-V. You can reduce RTO further by integrating with [Azure Traffic Manager](./concepts-traffic-manager-with-site-recovery.md).
4646
**Keep apps consistent over failover** | You can replicate using recovery points with application-consistent snapshots. These snapshots capture disk data, all data in memory, and all transactions in process.
4747
**Testing without disruption** | You can easily run disaster recovery drills, without affecting ongoing replication.

articles/site-recovery/tutorial-shared-disk.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,8 @@ To enable replication for shared disks, follow these steps:
6464

6565

6666
> [!IMPORTANT]
67-
> Ensure to select all the virtual machines representing your cluster. <br> If you don't select all the virtual machines, Site Recovery prompts you to choose the ones you missed. If you continue without selecting them, then the shared disks for those machines won't be protected.
67+
> Ensure to select all the virtual machines representing your cluster.
68+
> If you don't select all the virtual machines, Site Recovery prompts you to choose the ones you missed. If you continue without selecting them, then the shared disks for those machines won't be protected.
6869
6970
1. Under **Replication settings** tab, in the **Storage** section, select **View/edit storage configurations**. This opens the **Customize target settings** page where you can view and confirm the shared disk settings.
7071

@@ -84,10 +85,10 @@ To enable replication for shared disks, follow these steps:
8485
1. Under the **Manage** tab, do the following:
8586
1. In the **Shared disk clusters** section, assign a **Cluster name** for the group, which is used to represent the group throughout their disaster recovery lifecycle. This name is used to trigger any operations, monitor, or operate via PowerShell/REST.
8687

87-
> [!TIP]
88-
> We recommend that you use the same name as your cluster.
88+
> [!TIP]
89+
> We recommend that you use the same name as your cluster.
8990
90-
:::image type="content" source="media/tutorial-shared-disk/shared-disk-cluster.png" alt-text="Screenshot showing cluster name.":::
91+
:::image type="content" source="media/tutorial-shared-disk/shared-disk-cluster.png" alt-text="Screenshot showing cluster name.":::
9192

9293
1. Under **Replication policy** section, select an appropriate replication policy and extension update settings.
9394
1. Review the information and select **Enable replication**.

0 commit comments

Comments
 (0)