Hi all
I am losing touch with Veeam as we don't really use it anymore. However, we are needing to move our OnPrem Veeam servers to AWS, for historical restore purposes, as all our servers are in AWS now, but the business wants to retain all old backups.
Currently all of our Veeam backups are stored in several LUNs attached at the hypervisor level to 2 Veeam servers in 2 sites.
The LUNS vary in size from 5TB to 50TB.
In total we have just about 100TB of space across both servers.
We currently don't use any object storage like S3 etc and don't use any tapes.
We have a scale out repo that does our daily backups and keeps them for 2 weeks, then everything else goes to a GFS repo via BackupCopy job. So most of the backups we want to take to AWS are NOT in a scale-out-repo.
The question I have is, what is the best way to get the backups and server to AWS EC2? The AWS migration agent's won't work because some of the volumes are over 16TiB, which is the AWS migration agent limit apparently. We don't have all the backups in a scale out repo at the moment, so we can't just add a 'capacity' tier in S3 and let it offload it for us, as far as I can see?
I see there is now a 'copy backups' function in v12: https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Would this do what we want? We are on v11 at the moment, but we should have the license to update to v12
If guess we would:
1. Create an S3 repo
2. Copy the backups from the large LUNs (or all) to the S3 repo
3. Remove the additional large LUNs (or all) from the Veeam config
4. Use AWS migration agent to migrate the Veeam servers to AWS, but NOT replicate the additional LUNS that are too large (or all)
"or all" references copying all backups to S3, or doing only the large LUNs that can't be done with AWS migration agent and doing the rest with the migration agent.
Additional info:
Veeam version 11
The Veeam servers are not domain joined.
The storage permissions are configured with local accounts, not domain accounts. So whilst using something like AWS DataSync or even just RoboCopy is potentially possible, we would have to re-do the permissions before we did so.
Any thoughts appreciated!
Thanks
I am losing touch with Veeam as we don't really use it anymore. However, we are needing to move our OnPrem Veeam servers to AWS, for historical restore purposes, as all our servers are in AWS now, but the business wants to retain all old backups.
Currently all of our Veeam backups are stored in several LUNs attached at the hypervisor level to 2 Veeam servers in 2 sites.
The LUNS vary in size from 5TB to 50TB.
In total we have just about 100TB of space across both servers.
We currently don't use any object storage like S3 etc and don't use any tapes.
We have a scale out repo that does our daily backups and keeps them for 2 weeks, then everything else goes to a GFS repo via BackupCopy job. So most of the backups we want to take to AWS are NOT in a scale-out-repo.
The question I have is, what is the best way to get the backups and server to AWS EC2? The AWS migration agent's won't work because some of the volumes are over 16TiB, which is the AWS migration agent limit apparently. We don't have all the backups in a scale out repo at the moment, so we can't just add a 'capacity' tier in S3 and let it offload it for us, as far as I can see?
I see there is now a 'copy backups' function in v12: https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Would this do what we want? We are on v11 at the moment, but we should have the license to update to v12
If guess we would:
1. Create an S3 repo
2. Copy the backups from the large LUNs (or all) to the S3 repo
3. Remove the additional large LUNs (or all) from the Veeam config
4. Use AWS migration agent to migrate the Veeam servers to AWS, but NOT replicate the additional LUNS that are too large (or all)
"or all" references copying all backups to S3, or doing only the large LUNs that can't be done with AWS migration agent and doing the rest with the migration agent.
Additional info:
Veeam version 11
The Veeam servers are not domain joined.
The storage permissions are configured with local accounts, not domain accounts. So whilst using something like AWS DataSync or even just RoboCopy is potentially possible, we would have to re-do the permissions before we did so.
Any thoughts appreciated!
Thanks
Statistics: Posted by ChrisGundry — Jan 26, 2024 10:57 am
