Skip to content

Commit b68a906

Browse files
committed
docs: simplify app-consistent recovery points guidance per reviewer feedback
1 parent 76c87e8 commit b68a906

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/site-recovery/azure-to-azure-common-questions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -228,7 +228,7 @@ Because of extra content, app-consistent snapshots are the most involved, and ta
228228

229229
#### Do app-consistent recovery points impact performance?
230230

231-
Because app-consistent recovery points capture all data in memory and process, if they capture frequently, it can affect performance when the workload is already busy. We don't recommend that you capture too often for nondatabase workloads. As a general rule, a full backup for database workloads (including Azure Site Recovery) every hour is sufficient—if anything, this frequency is on the higher side. Typically, transaction log backups are combined at shorter intervals (for example, every 10 to 15 minutes) to distribute system load while meeting recovery objectives (RPO/RTO/RLO).
231+
Because app-consistent recovery points capture all data in memory and process, if they capture frequently, it can affect performance when the workload is already busy. We don't recommend that you capture too often for nondatabase workloads. Depending on your workload and its RPO requirements, you can evaluate whether to capture app-consistent points and their frequency.
232232

233233
#### What's the minimum frequency for generating app-consistent recovery points?
234234

0 commit comments

Comments
 (0)