Hi everyone,
In this scenario, I have two EC2 instances on Amazon Web Services and a Microsoft 365 tenant. I need to back up both using Veeam.
How can I do this with low resource usage?
I believe the EC2 costs for Veeam for Microsoft 365 are high (8 vCPUs and 16 GB RAM with Windows Server). So, if I use Veeam for Microsoft 365 on-premises (as the backup server) and use a data mover (backup proxy) on AWS, will I save costs?
Thanks for your help!
Best answer by lukas.k
Hi
You could consider using Veeam Data Cloud (Software-as-a-Service) for M365, but this is not yet possible for AWS.
Keep in mind the following:
Veeam Backuo for M365 can be deployed within Azure (so as a VM that can be manually installed or deployed by Azure Marketplace) but you also can use the software within an on-prem VM.
Keep in mind that when you install the software on-prem, backups and restores (so the traffic) will be going through your primary internet connection (on-prem), I’m not quire sure if it makes sense or is technically possible to split the backup server for M365 and use proxies within Azure. And you have to consider using object storage as backup target due to immutability and flexibility - this can also be either on-prem (appliances like Cloudian or Scality) or cloud-based.
Also you have to calculate the effective costs of you on-prem environment, that is also something for a calculation to declace which one will be more cost-effective.
With Veeam Backup for AWS (and Azure) you have to unterstand that these are linux-based appliances that have to (!) run within the source cloud, there is no possibility to let them run on-prem.
For Azure the primary backup target has to be Azure Blob, then you can copy to another (only object based) repository. I’m about sure that this is the same for AWS bot only with AWS S3 instead of Azure Blob.
I hope that gives you some input!
Best regards
Lukas
+10Hi
You could consider using Veeam Data Cloud (Software-as-a-Service) for M365, but this is not yet possible for AWS.
Keep in mind the following:
Veeam Backuo for M365 can be deployed within Azure (so as a VM that can be manually installed or deployed by Azure Marketplace) but you also can use the software within an on-prem VM.
Keep in mind that when you install the software on-prem, backups and restores (so the traffic) will be going through your primary internet connection (on-prem), I’m not quire sure if it makes sense or is technically possible to split the backup server for M365 and use proxies within Azure. And you have to consider using object storage as backup target due to immutability and flexibility - this can also be either on-prem (appliances like Cloudian or Scality) or cloud-based.
Also you have to calculate the effective costs of you on-prem environment, that is also something for a calculation to declace which one will be more cost-effective.
With Veeam Backup for AWS (and Azure) you have to unterstand that these are linux-based appliances that have to (!) run within the source cloud, there is no possibility to let them run on-prem.
For Azure the primary backup target has to be Azure Blob, then you can copy to another (only object based) repository. I’m about sure that this is the same for AWS bot only with AWS S3 instead of Azure Blob.
I hope that gives you some input!
Best regards
Lukas
Hi
You could consider using Veeam Data Cloud (Software-as-a-Service) for M365, but this is not yet possible for AWS.
Keep in mind the following:
Veeam Backuo for M365 can be deployed within Azure (so as a VM that can be manually installed or deployed by Azure Marketplace) but you also can use the software within an on-prem VM.
Keep in mind that when you install the software on-prem, backups and restores (so the traffic) will be going through your primary internet connection (on-prem), I’m not quire sure if it makes sense or is technically possible to split the backup server for M365 and use proxies within Azure. And you have to consider using object storage as backup target due to immutability and flexibility - this can also be either on-prem (appliances like Cloudian or Scality) or cloud-based.
Also you have to calculate the effective costs of you on-prem environment, that is also something for a calculation to declace which one will be more cost-effective.
With Veeam Backup for AWS (and Azure) you have to unterstand that these are linux-based appliances that have to (!) run within the source cloud, there is no possibility to let them run on-prem.
For Azure the primary backup target has to be Azure Blob, then you can copy to another (only object based) repository. I’m about sure that this is the same for AWS bot only with AWS S3 instead of Azure Blob.
I hope that gives you some input!
Best regards
Lukas
Hi Lukas,
First, thank you so much for your response and the time you took to provide these insights. I really appreciate it! I have some questions:
Is it not possible to use an architecture where I have Veeam Backup & Replication on-premises and a Data Mover (Veeam Backup Proxy) in the cloud, integrated?
With Veeam Data Cloud, wouldn’t I face significant data-out traffic from my infrastructure to the Veeam repository? In case of EC2. Or you recommend backup of M365 some?
Thanks again for your help!
+10Hi
You’re welcome. :-)
Best regards!
Lukas
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
