Skip to content

Commit 054eaa3

Browse files
authored
Merge pull request #189600 from mepand/patch-36
Update backup-azure-files-faq.yml
2 parents 349029b + aa10d9b commit 054eaa3

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

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

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,11 @@ sections:
2424
Why can't I see some of my Azure file shares in the Storage Account when I'm trying to configure backup?
2525
answer: |
2626
Check if the Azure file share is already protected in the same Recovery Services vault or if it has been deleted recently.
27+
28+
- question: |
29+
Why is it recommended to enable lock on the storage account?
30+
answer: |
31+
The current Azure Files backup solution keeps snapshots in the same storage account as the backed-up file share. If the storage account gets deleted, you will lose all your snapshots. To protect your account against accidental deletion, Azure Backup takes a Delete lock on the storage account. It means authorized users can still read and modify a resource, but they can't delete it. The lock also restricts the deletion of any file share under the storage account. Hence, you get protection from the accidental deletion of both the storage account and files shares.
2732
2833
- question: |
2934
Can I protect File Shares connected to a Sync Group in Azure Files Sync?

0 commit comments

Comments
 (0)