This Guidance demonstrates how to send long-term Veeam backups to AWS Cloud storage. The tools provided automate the creation of the cloud resources needed to store Veeam backups. You can use your existing backup infrastructure and reduce risk of data loss, increase backup recovery time, and lower cost with AWS Cloud storage.
Architecture Diagram
Step 1
Veeam Backup & Replication server is responsible for coordinating, controlling, and managing backup infrastructure, settings, jobs, recovery tasks, and other processes.
Step 2
Veeam uses the scale-out backup repository to tier data automatically between local (performance tier) and Amazon Simple Storage Service (Amazon S3) object storage (capacity and archive tiers).
Step 3
Veeam supports connections to AWS accounts through HTTPS or using AWS Direct Connect.
Step 4
The scale-out backup repository consists of one or more backup repositories that provide fast access to data. The repository can be expanded with Amazon S3 object storage repositories for long-term storage.
Step 5
Veeam launches an Amazon Elastic Compute Cloud (Amazon EC2) instance to support proxying data from capacity tiers to archive tiers.
Step 6
Backups can be archived to Amazon S3 Glacier for longer term storage and reduced costs.
Step 1
Veeam Backup & Replication server is responsible for coordinating, controlling, and managing backup infrastructure, settings, jobs, recovery tasks, and other processes.
Step 2
Veeam uses the scale-out backup repository to tier data automatically between local (performance tier) and Amazon Simple Storage Service (Amazon S3) object storage (capacity and archive tiers).
Step 3
Veeam supports connections to AWS accounts through HTTPS or using AWS Direct Connect.
Step 4
The scale-out backup repository consists of one or more backup repositories that provide fast access to data. The repository can be expanded with Amazon S3 object storage repositories for long-term storage.
Step 5
Veeam launches an Amazon Elastic Compute Cloud (Amazon EC2) instance to support proxying data from capacity tiers to archive tiers.
Step 6
Backups can be archived to Amazon S3 Glacier for longer term storage and reduced costs.
Well-Architected Pillars
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
-
Operational ExcellenceRead the Operational Excellence whitepaper
This Guidance helps you enable long-term object storage for Veeam Backup & Replication on AWS. It includes sample AWS CloudFormation code that allows object storage backup using Amazon S3, extending the functionality of Veeam Backup & Replication.
-
SecurityRead the Security whitepaper
This Guidance uses AWS Identity and Access Management (IAM) to centrally manage users, security credentials, and permissions.
Backup data is stored in Amazon S3 buckets. Access to the buckets is restricted through IAM and all public access is blocked in these buckets. The data is encrypted at rest by default.
-
ReliabilityRead the Reliability whitepaper
Veeam Backup & Replication can help with disaster recovery. This software protects data from logical errors such as system failures, application errors, or accidental deletion.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
Veeam Backup & Replication helps many small and medium-sized businesses protect on-premises infrastructure. These businesses want to reduce the amount of physical backup infrastructure that is needed to purchase and maintain, while ensuring that backups reside in highly durable, cost-effective storage. AWS storage services such as Amazon S3, AWS Storage Gateway, and AWS Snowball Edge seamlessly integrate with Veeam Backup & Replication to meet these needs.
-
Cost OptimizationRead the Cost Optimization whitepaper
Cost is based on the amount of data or infrastructure that is backed up to AWS through Veeam. Amazon S3 offers a pay by use pricing model with tiered pricing based on the storage class (storage classes in this Guidance include Standard, Glacier, and Glacier Deep Archive). Data transfer to Amazon S3 from the internet or Direct Connect is not charged. Data transferred out of Amazon S3 is charged by the gigabyte (GB).
-
SustainabilityRead the Sustainability whitepaper
This Guidance demonstrates how you can choose the type of storage you want based on the cost, resiliency, and data access requirements of your backup and archived data. Options to store data in Amazon S3 Infrequent Access (IA) or Amazon S3 Glacier provide you with a cost optimized and computationally efficient solution to back up and archive data.
Implementation Resources
A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.
The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.
Related Content
Veeam Backup & Replication
Veeam Backup & Replication
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.