Greetings friends, the first strong post of September, today I bring you a very entertaining post about Veeam Backup and Replication on a Repository based on AWS Storage Gateway, and as it has stayed a little long I want to leave here the menu to move you faster:
- AWS Storage Gateway - quick overview
- Deploying the AWS Storage Gateway Virtual Appliance on vSphere
- Configuring AWS Storage Gateway
- How to create a File Share on Amazon S3
- How to create a Repository on Veeam Backup and Replication
- Backup Copy job - quick overview
- Backup job - quick overview
- How to monitoring with Cloud Watch
AWS Storage Gateway - quick overviewAWS Storage Gateway allows us to consume certain Amazon Web Services resources locally through a virtual appliance that we deploy in our Infrastructure, so our VMs view the resources as if they were local, while the information is replicated in an encrypted and compressed way to the Amazon Cloud. AWS Storage Gateway allows us to create different resources:
- File Share: Which is nothing more or less than an NFS where we can connect computers that will see a traditional network drive and store files there.
- Volumes: Where we can consume by iSCSI, volumes that we can connect to Windows, Linux, etc., and that will be replicated later.
- Tapes: Virtual tape drives with which we can launch backups with Veeam for example, as if a real tape was involved, and thus get a more durable storage such as tapes, but in Cloud.
- Amazon S3, recommended for files or volumes that we use frequently.
- Amazon Glacier, if what we are saving is not accessed frequently.
- Amazon EBS Snapshots.