Hi,
We have Azure File Shares located in a multiple different regions. What would be most optimal placement considering cost and performance perspective when deploying Veeam backup for Azure to protect all Azure file shares?
Option 1: Deploy VBAzure in all regions to protect each region Azure files?
Option 2: Deploy VBAzure in one region, protect each region Azure files? How do we configure in this case?
Any reference blog or guide will be highlight appreciated
Thank you in advance.
-
- Enthusiast
- Posts: 36
- Liked: never
- Joined: Dec 08, 2021 10:39 am
- Full Name: Mogansundram Apna
- Contact:
-
- Product Manager
- Posts: 5874
- Liked: 1232 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Multiple regions Azure File Share snapshot best practice
Hi,
You can use 1 deployment to protect all regions in either 1 or more policies so in your case option 2 is viable.
You can use 1 deployment to protect all regions in either 1 or more policies so in your case option 2 is viable.
GitHub: https://github.com/nielsengelen
-
- Enthusiast
- Posts: 36
- Liked: never
- Joined: Dec 08, 2021 10:39 am
- Full Name: Mogansundram Apna
- Contact:
Re: Multiple regions Azure File Share snapshot best practice
Hi,
Thank you for your reply.
In the use case of option 2 (1 deployment to protect all regions in either 1 or more policies), is there any costs concern like API, traffic, etc we need to take note? Ultimately, we wanted to avoid monthly MS Cloud billing shock. Notice that there is a "Cost Estimation" in the policy, is this covered all of the cloud charges to run the file share backup for all regions?
In addition, what is the use case or benefit of the "File Share Indexing" in the policy? When enable it, will it invoke extra charges during the Azure file shares backup and restore? As the catalog save to the configuration database of VBAzure.
Thank you in advance.
Thank you for your reply.
In the use case of option 2 (1 deployment to protect all regions in either 1 or more policies), is there any costs concern like API, traffic, etc we need to take note? Ultimately, we wanted to avoid monthly MS Cloud billing shock. Notice that there is a "Cost Estimation" in the policy, is this covered all of the cloud charges to run the file share backup for all regions?
In addition, what is the use case or benefit of the "File Share Indexing" in the policy? When enable it, will it invoke extra charges during the Azure file shares backup and restore? As the catalog save to the configuration database of VBAzure.
Thank you in advance.
-
- Enthusiast
- Posts: 36
- Liked: never
- Joined: Dec 08, 2021 10:39 am
- Full Name: Mogansundram Apna
- Contact:
Re: Multiple regions Azure File Share snapshot best practice
Hi Nielsengelen,
Wondered whether you had a chance to review above and provide any comments?
Many thanks in advance.
Wondered whether you had a chance to review above and provide any comments?
Many thanks in advance.
-
- Product Manager
- Posts: 5874
- Liked: 1232 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Multiple regions Azure File Share snapshot best practice
Hi,
Sorry for the late reply. The cost estimation tool considers all costs as an estimate (API costs, network, etc.).
File share indexing is used for enhanced FLR restores which speeds up the search when browsing large file shares. This adds no additional costs.
Sorry for the late reply. The cost estimation tool considers all costs as an estimate (API costs, network, etc.).
File share indexing is used for enhanced FLR restores which speeds up the search when browsing large file shares. This adds no additional costs.
GitHub: https://github.com/nielsengelen
Who is online
Users browsing this forum: No registered users and 3 guests