To complete my setup, once I deployed all my virtual machines in the previous articles, I also need a S3 bucket to be later used in Veeam as an object storage. And obviously, I can also automated this part with Terraform.
Veeam Backup & Replication v12 is capable of writing backups directly to a Object storage. In my lab I use Scality Artesca as my S3-compatible object storage, so I created some new buckets to be used with Veeam. Let’s see how this can be done. The procedure can be useful also for people using different products.
In my previous post, I talked about Veeam N2WS Backup and Recovery (known previously as CPM) and how to configure it to protect different AWS accounts. Now that the configuration is ready, it’s time to protect the virtual machines, and to export them into S3 so that we can have an offsite copy using Veeam Backup & Replication.
Lately, I had to rebuild my personal lab after a major crash of the storage system I use, and even if I was able to restore everything, the procedure I had to use involved many manual rebuilding of the resources. This time, I decided that everything has to be protected in a way that it would be really easy to perform e restore of every component of the lab. I started with the basic infrastructure based on VMware vSphere, and I realized that, as much as it sounds something from the jurassic age, the best way to create backups of those resources was to use an FTP server!
Last week, another outage of a large cloud provider hit the news, and the many companies using their services were impacted. This time it was Amazon Web Services, as their S3 service in the US-East region has been down for almost 4 hours, impacting so many other cloud services that are relying on this object storage technology. What impacted me, however, had been the reactions of other IT people around and the couch architects all over the world.
S3 has been the first service Amazon Web Services division released in 2006, and is still the most used public storage service around. Many of you probably do not even know you are using it. Are you on Dropbox? Well, it runs on S3. Recently Amazon released a 2011 recap of…