Backup

As more services go live on my Kubernetes clusters and more people start relying on them, I get nervous. For the most part, I try and keep my applications and configurations stateless - relying on ConfigMaps for example to store application configuration. This means with a handful of YAML files in my Git repository I can restore everything to working order. Sometimes though, there’s no choice but to use a PersistentVolume to provide some data persistance where you can’t capture it in a config file. This is where a backup of the cluster - and specifically the PersistentVolume is really important.

I was recently sent a copy of Christian Mohn’s new book “Learning Veeam Backup and Replication for VMware vSphere” to review, and as ever this is my honest opinion of this book. I am not receiving anything other than the copy of the book for this review. I don’t work for a vendor, so I have no axe to grind!

Content

The book starts of with explanations of basic backup strategies and explains principals like Grandfather-Father-Son media rotation and RPO/RTOs. From there it dives into the architecture of Veeam BR and its components. The remainder of chapter 1 covers a walk through of the installation of the product.

In my previous post Backing up ESXi 5.5 host configurations with vCenter Orchestrator (vCO) – Workflow design walkthrough I showed how to create a workflow to back up host configurations, but it was limited to one host at a time. For this post I’m going to show how to create a new workflow that calls the previous one on multiple hosts using a ForEach loop to run it against each one. This was actually easier than I had anticipated (having read posts on previous versions of vCO that involved created the loops manually).

As a little learning project, I thought I’d take on Simon’s previous post about backing up ESXi configurations and extend it to vCenter Orchestrator (vCO), and document how I go about building up a workflow. I’m learning more and more about vCO all the time, but I found it has a really steep entry point, and finding use cases is hard if you haven’t explored capabilities.

Why should a home user backup? Most don’t, most people just have their photos, music and video collection on a single hard drive, maybe an external drive or even a USB key. Unfortunately, no-one ever thinks about what they’d do if their drive were to fail, losing all their precious holiday snaps, their slightly embarrassing music collection, or perhaps their family finances. But stop and think for a second – can you really replace those holiday snaps? What about your music collection – do you want to spend 3 days importing all your CDs or DVDs? Or maybe your personal finance app – is that something you could afford to lose?