Skip to content

Commit a7cea0f

Browse files
author
David Curwin
committed
Add error message scenario
1 parent d57a1c8 commit a7cea0f

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,7 @@ This error occurs when one of the extension failures puts the VM into provisioni
5959

6060
- This issue could happen if there is a lock on the recovery point resource group preventing automatic cleanup of recovery points.
6161
- 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 per the configured snapshot retention and only 18 instant RPs can be associated with a VM at any given time. <br>
62+
- The number of restore points across restore point collections and resource groups for a VM cannot exceed 18. To create a new restore point, please delete existing restore points.
6263

6364
Recommended Action:<br>
6465
To resolve this issue, remove the lock on the resource group of the VM, and retry the operation to trigger clean-up.

0 commit comments

Comments
 (0)