Hi Support,
We are planning to set up our VB365 backup infrastructure on an Azure tenant, utilizing Azure Blob storage for short-term retention of protected data created by backup jobs, and Azure Archive storage for long-term retention of protected data created by backup copy jobs.
Regarding the archiver appliance for Azure Archive storage, I believe that enabling this archiver to copy data from Azure Blob to Azure Archive storage will save egress charges if the VB365 proxy/proxy pool is set up on-premises or on any public cloud other than Azure.
Since the VB365 backup components will be set up on Azure, do I still need to enable this archiver to eliminate egress traffic?
Thanks,
John
-
- Novice
- Posts: 9
- Liked: never
- Joined: Nov 19, 2012 9:07 am
- Full Name: John
- Contact:
-
- Veeam Software
- Posts: 3495
- Liked: 832 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Archiver requirement of VB365 on Azure deployment
Hi John,
If both repositories and a backup proxy are located within the same region, there shouldn't be any egress costs, hence an appliance is not needed.
If the data is expected to be transferred cross-region, an appliance is recommended.
Thanks!
If both repositories and a backup proxy are located within the same region, there shouldn't be any egress costs, hence an appliance is not needed.
If the data is expected to be transferred cross-region, an appliance is recommended.
Thanks!
Who is online
Users browsing this forum: No registered users and 24 guests