Merge pull request #292744 from AbhishekMallick01/Jan-8-2025-AFS

AFS backup - FAQ added

Author: PMEds28

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

@@ -2,7 +2,7 @@
 metadata:
   title: Back up Azure Files FAQ
   description: In this article, discover answers to common questions about how to protect your Azure file shares with the Azure Backup service.
-  ms.date: 12/11/2024
+  ms.date: 01/08/2025
   ms.topic: faq
   ms.service: azure-backup
   author: AbhishekMallick-MS
@@ -74,6 +74,11 @@ sections:
           | **Daily**  | Add the retention values configured for daily, weekly, monthly, and yearly backups. For example, you configure a backup policy with the following values: <br><br> - Daily retention: 30 days <br> - Weekly retention: 40 weeks <br> - Monthly retention: 4 months <br> - Yearly retention: 6 years | This corresponds to 80 snapshots (30+40+4+6).
           | **Hourly** | There's a buffer allocated for any delay in pruning the expired snapshots. For example, you configure a backup policy with: <br><br> - Number of daily snapshots as per your schedule: 6 <br> - Daily retention: 30 days <br> - Monthly retention: 11 months <br> - Yearly retention: 8 years | Considering 1 day buffer for each daily snapshot, the daily retention of 30 days is considered as 31 days for each of the 6 daily snapshots. So, this configuration corresponds to 205 [(6X31)+11+8] snapshots.
 
+      - question: |
+          What is the maximum delay expected in backup start time from the scheduled backup time I have set in my backup policy?
+        answer: |
+          The scheduled backup is triggered within 2 hours of the scheduled backup time. For example, If 100 File Shares have their backup start time scheduled at 2:00 AM, then by 4:00 AM at the latest all the 100 File Shares will have their backup job in progress. If scheduled backups are paused because of an outage and resumed or retried, then the backup can start outside of this scheduled two-hour window.
+
 
 
   - name: Restore
@@ -98,6 +103,13 @@ sections:
         answer: |
           If a recovery point isn't listed, it must have expired. We recommend you checking the retention configured in the backup policy to understand the retention duration for recovery points of your backed-up file share.
 
+      - question: |
+          Why is my restore operation taking long time to complete?
+        answer: |
+          If you are restoring from snapshot backup, for Original Location Recovery (OLR) the total restore time depends on number of files and directories in the share. When you restore to alternate location, the restore time depends on number of files and directories in the share to be restored and  available IOPS on source and target storage account.
+
+
+
   - name: Manage backup
     questions:
       - question: |
@@ -280,7 +292,7 @@ sections:
       - question: |
           Why the expiry time for latest recovery points doesn't appear in the Azure portal?
         answer: |
-          Expiry Time of recovery points are updated when Garbage Collector (GC) runs, which is every 24 hours. After you update the backup policy, it can take up to 24 hours to show the updates in the Expiry Time, if there're no delays in GC jobs.
+          Expiry Time of recovery points is updated when Garbage Collector (GC) runs, which is every 24 hours. After you update the backup policy, it can take up to 24 hours to show the updates in the Expiry Time, if there're no delays in GC jobs.
 
       - question: |
           How is the expiry date shown when both snapshot and vaulted backups are configured?