Hello,
my former colleague configured Azure File-related backups in Azure. We are now a bit uncertain about their redundancy level, does this information in picture mean that it is geo-redundatly configured?
If not, how one should retroactively find out the redundancy status of backups?
BR,
Mauri
Hello @SadiqhAhmed-MSFT ,
that explained it quite a lot. So in the likely case of wanting to back up the file shares, could you please give some hints on how should it be proceeded? I mean in the bit of a broader sense.
-Lauri
I suggest you to refer to the article here - https://docs.microsoft.com/en-us/azure/storage/files/storage-files-planning#backup that should give you broader understanding of what is Azure File Share and how does Azure backup works/helps.
Hello @MauriKoiranen-4786 Thank you for contacting us. Happy to assist!
I see that you have a question on redundancy for Azure backup configured for Azure files share. Please see the response below:
Azure file share backup does not send backups to Vault. Which means for replication data, only snapshots which are stored locally will be replicated. However they will not be available based on what replication type the storage account is. For GRS, it will replicate the snapshots as well however if the snapshot is deleted in primary, it will also get deleted in secondary. There is no backup specific lock in it.
"The Storage Replication setting of the vault isn't relevant for Azure Files backup. This is because the current solution is snapshot-based and there's no data transferred to the vault. Snapshots are stored in the same storage account as the backed-up file share, and therefore replicated as per the replication setting of storage account"
Hope this answers your question. Feel free to ping with questions if need further assistance in this matter!
If the response helped, do "Accept Answer" and up-vote it
9 people are following this question.
