Merge pull request #288854 from AbhishekMallick-MS/Oct-21-2024-EEE

Addressed EEE doc ask #24121752

Author: prmerger-automator[bot]

articles/backup/backup-azure-vm-backup-faq.yml

@@ -4,7 +4,7 @@ metadata:
   description: In this article, discover answers to common questions about backing up Azure VMs with the Azure Backup service.
   ms.topic: faq
   ms.service: azure-backup
-  ms.date: 09/10/2024
+  ms.date: 10/21/2024
   author: AbhishekMallick-MS
   ms.author: v-abhmallick
 
@@ -296,7 +296,7 @@ sections:
         answer: |
           Yes, it's supported for [Cross Zonal Restore](backup-azure-arm-restore-vms.md#restore-options).
 
-      - question: How do I clear iSCSI session and it's processes after running the Python script for Linux ILR?
+      - question: How do I clear iSCSI session and its processes after running the Python script for Linux ILR?
         answer: |
           After you unmount disks from the Azure portal, run the Python script with `clean` parameter (`python scriptName.py clean`) to clear the session and remove the mount paths of the recovery point from the machine.     
 
@@ -404,5 +404,25 @@ sections:
         answer: |
           The expiry time for the latest recovery point doesn't appear because it has infinite retention until a newer one gets created. The expiry time of other recovery points will be available in the Azure Portal after 24 hours of creation, depending on when the garbage collection runs (that will be within 24 hours).
 
+      - question: Will an Azure VM restore operation to original or alternate location affect a scheduled backup?
+        answer: |
+          No, the restore operation (to  the original or an alternate location) doesn't affect scheduled backups.
+
+          - **Restore to Original Location**: Azure Backup replaces the existing VM’s disks with the ones from the restore point. This process includes [taking a snapshot of the current VM before the restore ensuring that the backup schedule remains](backup-azure-arm-restore-vms.md).
+          - **Restore to Alternate Location**: Azure Backup creates a new VM using the restore point. This new VM won't have the same backup schedule as the original VM; you need to configure the Backup policy manually. Learn [about Azure VM restore](about-azure-vm-restore.md).
 
+          In these restore scenarios, the original backup policy and schedule for the original VM remain unaffected. However, if you want the restored VM (in the alternate location) to have a backup schedule, you need to set up the Backup policy.
       
+      - question: What happens to the backup configuration if I do Original/Alternate Location Restore of Azure VMs?
+        answer: |
+          In case of an Original Location Restore (OLR) or an Alternate Location Restore (ALR) for Azure VMs, Azure Backup performs the backup configuration as:
+
+          | Restore type | Backup configuration | Backup data |
+          | --- | --- | --- |
+          | **Original Location Restore (OLR)** | The backup configuration remains the same. The restored VM uses the same backup policy and schedule as the original VM. | The existing backup data is preserved, and new backups are triggered as per the original backup schedule. |
+          | **Alternate Location Restore (ALR)** | The new VM created in the alternate location doesn't inherit the backup configuration of the original VM. You need to configure a new backup policy for this VM manually. | The backup data for the original VM remains unaffected. However, the new VM starts with a fresh backup history once you configure its backup. |
+
+          >[!Note]
+          >- **OLR**: Provides a seamless continuation of backups with the same policy.
+          >- **ALR**: Requires manual setup of backup policies for the new VM.
+