NetApp SnapManager for Virtual Infrastructure and VIBE

0 Comments Backup & Recovery, NetApp, Storage

So, I’ve already had a couple posts including some shell scripts that I wrote that will quiesce your Virtual Machines then initiate a NetApp level snapshot.  Some have noted (including myself) how they are not the best tools for getting the job done….mind you, they worked for me and my purpose, but they were lacking.  I’m not going to get into what they were lacking, but lets just leave it at that (definietly not a commercial product). Luckily for us, NetApp has released a new product called SnapManager for Virtual Infrastructure (SMVI) which a lot of people have already discussed in the blogging world.  This is another tool of the SnapManager series which automates the snapshot process for your application, including system quiescing (VM snapshots) and also integration with SnapMirror (if your using it).  Tons of information on SMVI can be found on the links at the bottom of this blog.

OK — so lets take it a step further, say you don’t want to fork out the money for SMVI, what can you do?  Well, NetApp released on its NOW ToolChest (support subscription required) a tool called VIBE, Virtual Infrastructure Backup Engine.

VIBE is a free tool which operates exactly as SMVI, the only catch is that you do not get the pretty GUI that SMVI gives you.  VIBE is completely text based via either Perl or compiled EXE (Perl for Linux or EXE for Windows), and I’m actually running it on my vCenter server nightly at Midnight.  VIBE interacts with vCenter to grab all of your datastore and VM information and to actually kick off the VM level snapshot.  VIBE then interacts with your NetApp FAS to kick off the NetApp level snapshot and any SnapMirror syncs.

Initial configuration is a little tricky, all of the commands can be seen by running vibe –help. I first ran it manually from the command line, then I took all of my configuration options and put them into a config file. You can specify a config file to use by running _vibe –config _.  This makes it extremely easy to automate.

vibe-help.png– Screenshot of VIBE –help

Here are some screenshots on how I am using it.  I’ve been using it for about a week now without one problem.  I must warn though, VIBE is not directly supported by NetApp, it is only supported via Professional Services.  With this said, once you get it working there should be no reason why you need support.

vibe-schedule-1.png– Here is my Scheduled Task to run my VIBE Batch Job

vibe-schedule-2.png– As you can see I am running it nightly at 12:05AM

vibe-batch.png– The Batch job is nothing more than kicking off the VIBE executable and specifying a config file to us for the settings. Also note that I am not specifying a path to VIBE, this is because the user running this task has the VIBE path in its environment

vibe-config.png– Here is the config file, nothing more than the vCenter user and password, along with the NetApp FAS login and password and the datastore names I want to backup. VIBE does all the hard work in finding the volume names and VM locations

vibe-snaps.png– Here is my final product, FAS level snapshots complete with VM
quiescing because VIBE integrates with vCenter. If you noticed the names are different it is because I changed them

Alright, thats pretty much it.  Easy to implement and use, and best of all – it is FREE :)

ref: discussion on SMVI

ref: VM /ETC discussion on SMVI