we have several use-cases where VMC on AWS is the right solution. In order to backup that environment do you have some suggestions? If I have a Veeam Proxy on VMC on AWS where can I place the Backups? Veeam as far as I know does not support to backup directly to an S3 bucket
Where to place backups depends on your requirements for RTO, backups accessibility etc. I would recommend looking through these links to explore all available and recommended options:
In general there are many options. But storing the backups on the same SDDC would be a bad idea. Usually the first backup goes to a EC2 Server with EBS ST1 volumes on AWS through ENI as documented in the above mentioned KB2414.
Hi!
first of all thanks for your reply! I think a scenario like this one https://d1.awsstatic.com/architecture-d ... on-aws.pdf would be a nice solution. So I can create a scaleout-repo with the EBS volumes (ST1) as performance tier and the S3 Bucket as Capacity Tier. Please allow me 2 additional questions:
1. Can I use also the S3 lifecycle policies to move the storage from the (for example) S3 OneZone IA to Glacier?
2. In my case I have 150VMs on-premise in an old VMware Infrastructure we want to eliminate. 50 VMs remain active and they will be migrated to VMC on AWS the other 100 ones will be shut down and I need to archive them in order to be able to restore them in case of need. So what are your suggestions? Migrate all to VMC and then back them up by using the scenarios described by you or do you have other tips & tricks? My problem is that on-premise I do no have enough amount of storage to create a scale-out repo with the performance-tier on-prem and an S3 bucket as capacity tier
1. This is a feature set announced for Backup & Replication v11 (later this year). The cost model around AWS Glacier dictate that this will be only used for long term backup (backup once never touch).
2. I would potentially replicate those with Veeam VM Replication to the Cloud (don´t use _Replica in the target names) and then Failover permanently. Then create a Veeam ZIP on the new Repository (you can Archive them forever or with for some time with autodelete) before you remove the VM. I suggest to create at least 2 backup copies ans best practices dictate.
thanks for you suggestions. By looking at the PDF suggested by Vitaliy S. https://d1.awsstatic.com/architecture-d ... on-aws.pdf
here we use a linux Ec2 instance with an EBS volume attached as a backup repository. So if this is supported in order to use it this EC2 with EBS needs to be a backup repository and if it's a backup repository in theory I can use it for any backup job and so use it to back-up vms indirectly to AWS. What do you think?
Correct, you can use EC2-instance with EBS volumes as a primary backup repository - even though it's not a direct backup to Amazon S3 mentioned in your original post.
You seem to have mentioned the best approach already - Scale-Out Backup Repository consisting of Performance (EC2-instance with EBS volumes) and Capacity (S3 bucket) Tiers.
I think a scenario like this one