Skip to main content

Simple VCB: a tool For Vmware Consolidated Backup

I have written and would like to share with the world a groovy script that can be used to drive VCB backups without additional third party software.
One of the most common gripes with VCB is that it doesn't integrate naturally into the VMWare management solution. Of course one can always buy a license for the integration module of his backup software, but that costs additional money.

Some people then resort to script VCB so that additional licenses are not necessary but that, of course, requires scripting skills. Which also means reinventing the wheel just another time.

This has happened to me too recently and I decided that ok, I would reinvent the damn wheel, but this time I would also make sure that the blueprint goes public!

So I wrote this groovy script which I creatively named Simple VCB which does some nice things like:
  • handles more than one esx, vcenter or vsphere server so that you don't have to split your configuration and schedules in more than one script (the vcb host must then be able to mount all the volumes used by these servers)
  • allows you to specify the list of vms to be backed up for each server
  • allow you to specify backup interval and/or protection per server or per single vm
    • interval: is the number of days after which a new backup must be done. I.e. 1 means every day, while 7 means after one week since last backup. In this way you can still take frequent backups for vms that change often and conserve resources usage by widening backup cycles for those that are mostly static (a proxy server, a dns, a reverse proxy)
    • protection: the number of backup copies that should be kept online. Older backups with an index higher than protection are deleted. Protection, like interval, can be set per single vm to allow for finer tuning
The backups are kept in a tidily organized folder structure where the root is defined in the configuration file and can be anything. I currently use a CIFS folder shared by a DataDomain 630 which will online dedupe the vm images.
Each vm then gets its own folder where all backups are stored, with each backup in its own subfolder with a human-readable timestamped name so that restore operations can be readily performed by whatever mean you like. The timestamps are then used to calculate the next backup interval and whether protection has expired and the folder should be automatically removed.

You can get the script on my GitHub page.

This is the configuration file that ships with the software which I believe should quite be self-explanatory.

Comments

Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post.
Btw: the recovery, depending on db size and disk speed, is going to take long.

The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux.

The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking.

Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd into the mirth home. …