WilliamLam.com

Magikmon MKBackup for ghettoVCB

by // 1 Comment

I was contacted awhile back ago by Alain Spineux, about his MKBackup utility and he was in the very early stages of integrating the software with my ghettoVCB script. Per Alain's website:

MKBackup is a free front-end for common backup tools like MS Windows ntbackup, and it successor wbadmin, Un*x tools like tar, but also popular ghettoVCB to backup Virtual Machine on VMware ESX(i) host.

MKBackup is developed in Python and is available for Microsoft Windows, for Linux and other Un*x systems.

MKBackup is driven by a CLI and jobs are defined in an INI file. Its main feature is to send an email report including log files and all hints that could help the user to estimate the real status of the backup.

It looks like Alain has done some more work and the recently released version 0.9.3. You can get a better overview of the tool at his website and there is also a dedicated support forum.

I have personally not used MKBackup, but it could be very useful and compliment ghettoVCB. Not only can you schedule backups on a Windows or UNIX/Linux host using MKBackup, but it also generates backup reports based on the output from ghettoVCB logs. The reports can then be monitored using a soon to be released utility called MagiKmon which can provide email alerts on successful or failed backups.
 
Here are a few screenshots that Alain has kindly provided with the use of the latest version of ghettoVCB:

Categories // Uncategorized Tags //

Script: Updated ghettoVCB and ghettoVCBg2 to Support vSphere 4.1

by // 21 Comments

Check out the latest update to both ghettoVCB and ghettoVCBg2, which now supports vSphere 4.1! There are no new features introduced with these updates but ghettoVCB does include additional logging and debugging functionality to help identify issues that may arise. Unfortunately, with ghettoVCBg2 I had to perform some additional code changes due to undocumented changes in vMA's vi-fastpass Perl library. This initially caused the script to break and the reason was deprecated methods that were removed in the latest release of vMA 4.1. Luckily the fix was not too bad and I had to spend a few hours looking at the new methods that were implemented.

Hopefully everyone enjoys these two releases and if you run into any troubles, please post in respective script's forum.