Merge pull request MicrosoftDocs#36756 from floschmsft/patch-9

Jak-MS · web-flow · commit c8a3b1133bcd · 2019-08-08T16:09:49.000-05:00
Update backup-architecture.md
diff --git a/articles/backup/backup-architecture.md b/articles/backup/backup-architecture.md
@@ -116,7 +116,7 @@ Back up deduplicated disks | | | ![Partially][yellow]<br/><br/> For DPM/MABS ser
     - Only blocks of data that changed since the last backup are copied.
     - Data isn't encrypted. Azure Backup can back up Azure VMs that were encrypted by using Azure Disk Encryption.
     - Snapshot data might not be immediately copied to the vault. At peak times, the backup might take some hours. Total backup time for a VM will be less than 24 hours for daily backup policies.
-1. After the data is sent to the vault, the snapshot is removed, and a recovery point is created.
+1. After the data is sent to the vault, a recovery point is created. By default, snapshots are retained for two days before they are deleted. This feature allows restore operation from these snapshots, thereby cutting down the restore times. It reduces the time that's required to transform and copy data back from the vault. See [Azure Backup Instant Restore Capability](https://docs.microsoft.com/en-us/azure/backup/backup-instant-restore-capability).
 
 Azure VMs need internet access for control commands. If you're backing up workloads inside the VM (for example, SQL Server database backups), the back-end data also needs internet access. 
 
