Skip to content

Commit 3395419

Browse files
committed
Cache storage for V2A
1 parent 900b655 commit 3395419

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

articles/site-recovery/vmware-physical-azure-support-matrix.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -367,7 +367,14 @@ Maximum data churn per day supported by a Process Server | 2 TB
367367
- Site Recovery is capable of handling higher throughput based on overlap ratio, larger write sizes, and actual workload I/O behavior.
368368
- These numbers assume a typical backlog of approximately five minutes. That is, after data is uploaded, it is processed and a recovery point is created within five minutes.
369369

370-
## Storage account limits
370+
## Cache Storage account
371+
372+
This table summarizes support for the cache storage account used by Site Recovery during replication.
373+
374+
**Setting** | **Support** | **Details**
375+
--- | --- | ---
376+
General purpose V2 storage accounts | Supported | Site Recovery is transaction-intensive, a general-purpose v1 account may be more cost-effective.
377+
Soft delete | Not supported | Soft delete isn't supported because once it is enabled on cache storage account, it increases cost. Azure Site Recovery performs frequent creates/deletes of log files while replicating causing costs to increase.
371378

372379
As average churn on the disks increases, the number of disks that a storage account can support decreases. The below table may be used as a guide for making decisions on number of storage accounts that need to be provisioned.
373380

0 commit comments

Comments
 (0)