Skip to content

Commit cd20157

Browse files
authored
Merge pull request #305670 from rohan-sahini/main
Storage Replica change
2 parents be9807e + bb37ae7 commit cd20157

2 files changed

Lines changed: 4 additions & 1 deletion

File tree

articles/backup/azure-elastic-san-backup-support-matrix.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,8 @@ Elastic SAN backup has the following supported and unsupported scenarios:
4747
| --- | --- |
4848
| On-demand backup | 10 per backup instance per day. |
4949
| Restore | 10 per backup instance per day. |
50-
50+
>[!Note]
51+
>- The Backup solution in preview supports Elastic SAN volumes size of <= 4 TB.
5152
5253
## Next steps
5354

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -441,6 +441,8 @@ Write accelerator enabled disks | Not supported
441441
Tags | Supported | User-generated tags are replicated every 24 hours.
442442
Soft delete | Not supported | Soft delete isn't supported because once it's enabled on a storage account, it increases cost. Azure Site Recovery performs very frequent creates/deletes of log files while replicating causing costs to increase.
443443
iSCSI disks | Not supported | Azure Site Recovery may be used to migrate or failover iSCSI disks into Azure. However, iSCSI disks aren't supported for Azure to Azure replication and failover/failback.
444+
Storage Replica | Not supported
445+
444446

445447
>[!IMPORTANT]
446448
> To avoid performance issues, make sure that you follow VM disk scalability and performance targets for [managed disks](/azure/virtual-machines/disks-scalability-targets). If you use default settings, Site Recovery creates the required disks and storage accounts, based on the source configuration. If you customize and select your own settings, follow the disk scalability and performance targets for your source VMs.

0 commit comments

Comments
 (0)