Veeam: AWS workloads now protected thanks to the Veeam’s acquisition of N2W Software (N2WS)

Greetings friends, probably you have heard the news that told us how Veeam had acquired N2WS, a company that is dedicated to the protection of environments in Cloud on Amazon Web Services.

Why did Veeam acquire N2WS?

N2WS is a leader in Infrastructure as a Service (IaaS) data protection, providing a native cloud backup solution specifically designed for AWS workloads, enabling organizations to back up data and applications as often as needed and recover them in seconds. As Veeam customers seek to move more workloads into the cloud, especially towards AWS, protection and availability of their data is a primary concern for Veeam. Veeam's goal is to give its customers the confidence that Veeam ensures that their information is protected no matter where it resides, and this acquisition gives us the #1 solution we need for data and application protection at AWS.

Amazon Web Services at a glance

For those of you who are not up to date on Amazon Web Services, we have several elements in the Computing and Storage part. At the moment of storage of the Instances we have:
  • Block: Storage the block provided by Amazon EBS that is persistent and Amazon EC2 Instance that is ephemeral and is destroyed when the Instance is destroyed.
  • File: Amazon offers us Amazon EFS that we can connect to our instances and launch files there.
  • Object: The already known Amazon S3 for access to non-continuously used items and Glacier for very cheap storage that we access only for archiving.

Veeam: Integration of AWS Storage Gateway with Veeam – Backups and backup copy in Cloud

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

AWS 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.
We can store the information in three different types of Amazon storage:
  • 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.
This is how our Veeam Backup and Replication Infrastructure with AWS Storage Gateway would look like.