In my home lab I did the usual mistake of forgetting to enable EVC mode before adding my second NUC to the VSAN cluster. I got stuck for a day trying to find a solution for it, but I finally managed to solve it. Here’s how.
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.
For a new project I started last week I needed a DNS server in my home office. Usually, my router is my dns resolver, but it doesn’t allow to create authoritative zones. Windows 10 running on my laptop doesn’t have a DNS server either, and I don’t have an hypervisor in my home office to build a virtual machine; and it wouldn’t even be useful to spend so much time doing it for then using the DNS just a couple of hours.
So, I looked around and I found this tiny cool project called MaraDNS, that was perfect for my use case.
Since we released Veeam Backup for Google Cloud Platform (can we call it VB4GCP from now on, do you mind?) a few weeks ago, many users have immediately started to use it. The use case of a single user protecting his resources is very easy to understand and configure, but today I’ve been asked by one of our service providers how could we configure the software to protect different customers from the same installation. Let’s test this in the lab!