Merge pull request #72651 from ThalathBhagya/master

PRMerger18 · web-flow · commit 6a9d4aa534e0 · 2019-04-10T16:48:57.000+08:00
instant restore content update
diff --git a/articles/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md b/articles/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
@@ -46,7 +46,7 @@ After you register and schedule a VM for the Azure Backup service, Backup initia
 **Error code**: UserErrorRpCollectionLimitReached <br>
 **Error message**: The Restore Point collection max limit has reached. <br>
 * This issue could happen if there is a lock on the recovery point resource group preventing automatic cleanup of recovery point.
-* This issue can also happen if multiple backups are triggered per day. Currently we recommend only one backup per day as the instant RPs are retained for 7 days and only 18 instant RPs can be associated with a VM at any given time. <br>
+* This issue can also happen if multiple backups are triggered per day. Currently we recommend only one backup per day as the instant restore points are retained for 1-5 days as per the configured snapshot retention and only 18 instant RPs can be associated with a VM at any given time. <br>
 
 Recommended Action:<br>
 To resolve this issue, remove the lock on the resource group of the VM, and retry the operation to trigger clean-up.
