Skip to content

Commit d92c621

Browse files
Merge pull request #299990 from PriskeyJeronika/release-asr-pv2-pup
Updates to Premium SSD V2 public preview
2 parents 145a045 + 6a42400 commit d92c621

File tree

4 files changed

+11
-10
lines changed

4 files changed

+11
-10
lines changed

articles/site-recovery/azure-to-azure-architecture.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure to Azure disaster recovery architecture in Azure Site Recovery
33
description: Overview of the architecture used when you set up disaster recovery between Azure regions for Azure VMs, using the Azure Site Recovery service.
44
ms.service: azure-site-recovery
55
ms.topic: concept-article
6-
ms.date: 03/17/2025
6+
ms.date: 05/19/2025
77
ms.author: ankitadutta
88
author: ankitaduttaMSFT
99
---
@@ -22,7 +22,7 @@ The components involved in disaster recovery for Azure VMs are summarized in the
2222
**VMs in source region** | One of more Azure VMs in a [supported source region](azure-to-azure-support-matrix.md#region-support).<br/><br/> VMs can be running any [supported operating system](azure-to-azure-support-matrix.md#replicated-machine-operating-systems).
2323
**Source VM storage** | Azure VMs can be managed, or have nonmanaged disks spread across storage accounts.<br/><br/>[Learn about](azure-to-azure-support-matrix.md#replicated-machines---storage) supported Azure storage.
2424
**Source VM networks** | VMs can be located in one or more subnets in a virtual network (VNet) in the source region. [Learn more](azure-to-azure-support-matrix.md#replicated-machines---networking) about networking requirements.
25-
**Cache storage account** | You need a cache storage account in the source network. During replication, VM changes are stored in the cache before being sent to target storage. <br/><br/> Using a cache ensures minimal impact on production applications that are running on a VM.<br/><br/> [Learn more](azure-to-azure-support-matrix.md#cache-storage) about cache storage requirements.
25+
**Cache storage account** | You need a cache storage account in the source network. During replication, VM changes are stored in the cache before being sent to target storage. <br/><br/> Using a cache ensures minimal impact on production applications that are running on a VM.<br/><br/> [Learn more](azure-to-azure-support-matrix.md#cache-storage) about cache storage requirements.<br/><br/> **Note**: Virtual machines with Premium SSD v2 disks require High Churn and uses Premium Storage Account.
2626
**Target resources** | Target resources are used during replication, and when a failover occurs. Site Recovery can set up target resource by default, or you can create/customize them.<br/><br/> In the target region, check that you're able to create VMs, and that your subscription has enough resources to support VM sizes that are needed in the target region.
2727

2828
![Diagram showing source and target replication.](./media/concepts-azure-to-azure-architecture/enable-replication-step-1-v2.png)

articles/site-recovery/azure-to-azure-quickstart.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Set up Azure VM disaster recovery to a secondary region with Azure Site Recovery
33
description: Quickly set up disaster recovery to another Azure region for an Azure VM, using the Azure Site Recovery service.
44
ms.topic: quickstart
5-
ms.date: 07/14/2023
5+
ms.date: 05/19/2025
66
ms.custom: mvc, mode-other
77
ms.author: ankitadutta
88
author: ankitaduttaMSFT
@@ -39,6 +39,8 @@ The following steps enable VM replication to a secondary location.
3939
>[!Note]
4040
>Azure Site Recovery has a *High Churn* option that you can choose to protect VMs with high data change rate. With this, you can use a *Premium Block Blob* type of storage account. By default, the **Normal Churn** option is selected. For more information, see [Azure VM Disaster Recovery - High Churn Support](./concepts-azure-to-azure-high-churn-support.md).
4141
>:::image type="High churn" source="media/concepts-azure-to-azure-high-churn-support/churn-for-vms.png" alt-text="Screenshot of Churn for VM.":::
42+
>
43+
>Azure Site Recovery for Premium SSD Pv2 by default uses High Churn and a Premium Block Blob type.
4244
1. To start the job that enables VM replication, select **Start replication**.
4345

4446
:::image type="content" source="media/azure-to-azure-quickstart/enable-replication1.png" alt-text="Enable replication.":::

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

Lines changed: 3 additions & 6 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: concept-article
5-
ms.date: 04/07/2025
5+
ms.date: 05/19/2025
66
ms.service: azure-site-recovery
77
author: ankitaduttaMSFT
88
ms.author: ankitadutta
@@ -83,10 +83,6 @@ As average churn on the disks increases, the number of disks that a storage acco
8383
> The cache limits are specific to Azure-to-Azure and Zone-to-Zone DR scenarios.
8484
>
8585
> When you enable replication via the virtual machine workflow for cross subscription, the portal only lists the cache storage account from the source subscription, but doesn't list any storage account created in the target subscription. To set up this scenario, use [PowerShell](azure-to-azure-powershell.md).
86-
>
87-
> Azure Site Recovery isn't supported for VMs with Premium SSD v2 disks.
88-
89-
9086
9187
## Replicated machine operating systems
9288

@@ -403,7 +399,8 @@ Azure Storage firewalls for virtual networks | Supported | If you want to restr
403399
General purpose V2 storage accounts (Both Hot and Cool tier) | Supported | Transaction costs increase substantially compared to General purpose V1 storage accounts
404400
Generation 2 (UEFI boot) | Supported
405401
NVMe disks | Not supported
406-
Azure Shared Disks | Not supported
402+
Managed Shared Disk| Supported
403+
Managed Premium SSD v2 Disk| Supported
407404
Ultra Disks | Not supported
408405
Secure transfer option | Supported
409406
Write accelerator enabled disks | Not supported

articles/site-recovery/site-recovery-cost.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Understanding Azure Site Recovery for Managed Disks Charges
33
description: This article summarizes the costs disaster recovery and migration deployment scenarios.
44
ms.topic: overview
55
ms.service: azure-site-recovery
6-
ms.date: 04/22/2025
6+
ms.date: 05/19/2025
77
ms.author: ankitadutta
88
author: ankitaduttaMSFT
99
---
@@ -26,6 +26,8 @@ The Protected Instance License fee is a fundamental charge for using Azure Site
2626
Storage cost is a significant part of the overall expense when using Azure Site Recovery. This cost includes:
2727

2828
- **Replica Storage**: The replica storage in the target location mirrors source storage. This storage is used during replication, and its size and type depend on the source storage configuration. Applicable only for A2A.
29+
>[!Note]
30+
>Premium SSD v2 source disks will have Premium SSDv1 replica disks.
2931
- **Cache Storage Account Cost**:
3032
- **Azure Virtual Machines**: The cache storage account is in the source region. When a user selects *High Churn* the cache storage account uses Premium Block Blob. For *Normal Churn* it uses a General Purpose Storage Account. The charges depend on the type of storage account used. There are minimal egress costs only in A2A for Delta Replication.
3133
- **VMware/Physical Machines/Hyper-V Machines**: The cache storage account is in the target region, charged at General Purpose Storage Account pricing as per the user's selection.

0 commit comments

Comments
 (0)