When deploying in a multi-cloud environment or select an object storage type in Public Cloud, consider the following:
- Optimal network path
- Run a Microsoft 365 network connectivity test to help discover potential connectivity problems for your location.
- Data transfer charges (e.g. egress)
Please check each vendor’s website for detailed cost specifications.
Different deployment types come with different recommendations:
1. VB365 deployment on-premises + on-premises object storage.
In this scenario all backup and restore traffic stays within the same private cloud infrastructure.
Check with your object storage vendor for best practices and proper sizing for items such as: - Loadbalancer requirements and configuration - Capacity sizing - IOPS/throughput sizing - Maximum bucket size
2. VB365 deployment in Public Cloud (e.g. Azure) + Public Cloud object storage (e.g. Azure Blob).
In this scenario all backup and restore traffic stays within the same public cloud infrastructure.
However depending on where all the components are deployed, data transfer charges might incur.
Keep in mind that most public cloud providers charge for cross region traffic
3. VB365 deployment on-premises + Public Cloud object storage.
In this scenario all data will be downloaded from the M365 cloud towards the VB365 Proxy Servers and then back uploaded to the Public Cloud object storage.
When recovering data, data traffic will flow in the exact opposite direction. This might result in a slower performance.
Depending on the Public Cloud vendor, egress costs might incur.
Deploying all VB365 components on-premises including on-premises backup storage means all traffic stays local and does not have to leave the data center.
4. VB365 deployment in Public Cloud (e.g. Azure) + Public Cloud object storage (e.g. AWS).
In this scenario all data traffic leaves the Azure network which means egress charges will incur.
From a DR perspective it seems like a good solution to spread the risk, however from a networking and cost perspective it is not very effective.
In case you prefer to have backup data in another Public Cloud, create Backup jobs to Azure Blob and then create Backup Copy jobs to AWS Glacier.
This way the main backup and restore traffic will remain within Azure and the AWS Glacier archive is only used for disaster recovery or compliance.
For info on TLS cipher suites or using a Internet Proxy, check the general VB365 BP guide page.