Amazon cloud storage, particularly S3 and Glacier, are popular options for offsite data storage, and Veeam is a leading solution for VM backups. You can integrate the two, but the question is: should you? The answer depends on several factors.
Veeam and AWS Integration
Integrating Veeam Backup & Replication with Amazon storage is done through an AWS Storage Gateway—an appliance that connects your Veeam server to the AWS Cloud. You can configure the gateway as a file server, direct attached storage, or as a Virtual Tape Library (VTL).
- File Server/Direct Attached Storage: In this setup, you can back up directly from Veeam to the AWS storage gateway. While incremental backups are supported, you’ll need to periodically perform full backups to avoid the risks associated with long backup chains.Although synthetic operations are possible, without an AWS-side proxy, the entire process becomes cumbersome. Veeam would need to download the full backup and incrementals from AWS, perform the synthetic operation locally, and then re-upload the new synthetic data. This leads to extremely long processing times and is generally not recommended.
Virtual Tape Library (VTL)
Using AWS as a virtual tape library allows you to present the storage gateway to Veeam as a tape server, which lets you create tape backups in AWS.
- While Veeam tape backups support incremental backups, periodic full backups are still required, especially when new tapes are created.
- The maximum tape size for AWS is 2.5TB, meaning that for larger datasets, you may need new tapes frequently.
- Restoring from archived tapes can take up to 24 hours for retrieval, and there’s a cost associated with making tapes available again.
Veeam Cloud Connect: A Simpler Option
Alternatively, Veeam offers Cloud Connect, an offsite backup method built into its platform. Cloud Connect partners—third-party Veeam service providers—offer storage and compute resources specifically tailored for offsite backups. Users simply input their provider’s credentials into Veeam and can start sending backups to the Cloud Repository.
- Incremental Forever Backups: Unlike AWS, Cloud Connect allows for forever incremental backups with periodic synthetic fulls. Because the service provider is also running Veeam, synthetic operations (full backups and merges) are performed locally at the remote site, significantly reducing backup windows.
- Pre-Configured Appliance: You can also configure your own Cloud Connect server in Azure using a pre-configured appliance from Veeam. However, this adds complexity, as it requires managing Azure storage, compute resources, and additional Veeam licensing costs.
For most businesses, a Cloud Connect partner offers a simpler, more cost-effective solution, allowing true incremental forever backups without the hassle of setting up your own infrastructure.
When to Use AWS for Offsite Backups
Using AWS for offsite backups with Veeam can work, but regular full backups are required. This option might only be suitable if:
- You have less than 1TB of data to back up.
- Your backups are infrequent and you can tolerate long backup windows.
- You have ample bandwidth to transfer data to and from Amazon storage servers.
Conclusion
While AWS can be used for offsite Veeam backups, it’s generally not the most efficient or cost-effective option for larger datasets or frequent backups. A Veeam Cloud Connect partner provides a better solution for:
- Nightly incremental backups
- Regular synthetic fulls performed on remote repositories
- Reduced backup windows
Choosing a Cloud Connect provider often leads to simpler management, lower costs, and faster backups, making it a more feasible choice for most businesses.
