Merge pull request #46936 from markgalioto/jul182018

adding a FAQ section to the Backup Stack v2 article

Author: Ja-Dunn

articles/backup/backup-upgrade-to-vm-backup-stack-v2.md

@@ -1,26 +1,28 @@
 ---
 title: Upgrade to the Azure VM Backup Stack V2
 description: Upgrade process and FAQs for VM backup stack, Resource Manager deployment model
-services: backup, virtual-machines
+services: backup
 author: trinadhk
 manager: vijayts
 tags: azure-resource-manager, virtual-machine-backup
-ms.service: backup, virtual-machines
+ms.service: backup
 ms.topic: conceptual
-ms.date: 03/08/2018
+ms.date: 7/18/2018
 ms.author: trinadhk
---- 
+---
 
 # Upgrade to Azure VM Backup stack V2
+
 The Resource Manager deployment model for the upgrade to virtual machine (VM) backup stack provides the following feature enhancements:
+
 * Ability to see snapshots taken as part of a backup job that's available for recovery without waiting for data transfer to finish. It reduces the wait time for snapshots to copy to the vault before triggering restore. Also, this ability eliminates the additional storage requirement for backing up premium VMs, except for the first backup.  
 
-* Reduction in backup and restore times by retaining snapshots locally for seven days.
+* Reduces backup and restore times by retaining snapshots locally, for seven days.
 
 * Support for disk sizes up to 4 TB.
 
-* Ability to use an unmanaged VM's original storage accounts when restoring. This ability exists even when VM has disks that are distributed across storage accounts. It makes restores faster for a wide variety of VM configurations.
-    > [!NOTE] 
+* Ability to use an unmanaged VM's original storage accounts, when restoring. This ability exists even when the VM has disks that are distributed across storage accounts. It speeds up restore operations for a wide variety of VM configurations.
+    > [!NOTE]
     > This ability is not the same as overriding the original VM. 
     >
 
@@ -36,15 +38,16 @@ A recovery point is considered created only after phases 1 and 2 are done. As pa
 By default, snapshots are kept for seven days. This feature allows the restore to finish faster from these snapshots. It reduces the time that's required to copy data back from the vault to the customer's storage account. 
 
 ## Considerations before upgrade
-* The upgrade of the VM backup stack is one directional. So all backups go into this flow. Because it's enabled at the subscription level, all VMs go into this flow. All new feature additions are based on the same stack. Ability to control this at policy level is coming in future releases.
 
-* Snapshots are stored locally to boost recovery point creation and also to speed up restore. Therefore, you see storage costs that correspond to snapshots during the seven-day period.
+* The upgrade of the VM backup stack is one directional, all backups go into this flow. Because the change occurs at the subscription level, all VMs go into this flow. All new feature additions are based on the same stack. Currently you can't control the stack at policy level.
 
-* Incremental snapshots are stored as page blobs. All customers that use unmanaged disks are charged for the seven days the snapshots are stored in the customer's local storage account. According to the current pricing model, there is no cost for customers on managed disks.
+* Snapshots are stored locally to boost recovery point creation and also to speed up restore operations. As a result, you'll see storage costs that correspond to snapshots taken during the seven-day period.
 
-* If you do a restore from a snapshot recovery point for a premium VM, you see a temporary storage location that is used while the VM is created as part of the restore.
+* Incremental snapshots are stored as page blobs. All customers that use unmanaged disks are charged for the seven days the snapshots are stored in the customer's local storage account. According to the current pricing model, there's no cost for customers on managed disks.
 
-* For premium storage accounts, the snapshots that are taken for instant recovery will count towards the limit of 10 TB of allocated space.
+* If you restore a premium VM from a snapshot recovery point, a temporary storage location is used while the VM is created.
+
+* For premium storage accounts, the snapshots taken for instant recovery points count towards the 10-TB limit of allocated space.
 
 ## Upgrade
 ### The Azure portal
@@ -84,3 +87,39 @@ Get-AzureRmProviderFeature -FeatureName "InstantBackupandRecovery" –ProviderNa
 ```
 
 If it says "Registered," then your subscription is upgraded to VM backup stack Resource Manager deployment model.
+
+## Frequently asked questions
+
+The following questions and answers have been collected from forums and customer questions.
+
+### Will upgrading to V2 impact current backups?
+
+If you upgrade to V2, there's no impact to your current backups, and no need to reconfigure your environment. Upgrade and your backup environment continues to work as it has.
+
+### What does it cost to upgrade to Azure Backup stack v2?
+
+There is no cost to upgrade to Azure Backup stack v2. Snapshots are stored locally to speed up recovery point creation, and restore operations. As a result, you'll see storage costs that correspond to the snapshots taken during the seven-day period.
+
+### Does upgrading to stack v2 increase the premium storage account snapshot limit by 10 TB?
+
+No.
+
+### In Premium Storage accounts, do snapshots taken for instant recovery point occupy the 10 TB snapshot limit?
+
+Yes, for premium storage accounts, the snapshots taken for instant recovery point, occupy the allocated 10 TB of space.
+
+### How does the snapshot work during the seven-day period? 
+
+Each day a new snapshot is taken. There are seven individual snapshots. The service does **not** take a copy on the first day, and add changes for the next six days.
+
+### What happens if the default resource group is deleted accidentally?
+
+If the resource group is deleted, the instant recovery points for all protected VMs in that region, are lost. When the next backup occurs, the resource group is created again, and the backups continue as expected. This functionality is not exclusive to instant recovery points.
+
+### Can I delete the default resource group created for instant recovery points?
+
+Azure Backup service creates the managed resource group. Currently, you can't change or modify the resource group. Also, you should not lock the resource group. This guidance is not just for the V2 stack.
+ 
+### Is a v2 snapshot an incremental snapshot or full snapshot?
+
+Incremental snapshots are used for unmanaged disks. For managed disks, the snapshot is a full snapshot.