2009-02-18 02:07 PM
Trying to configure VIBE to backup our VMware ESX 3.5 environment.
Everything is working fine, except that I can't seem to get the "--novmset" option to work. The documentation states that this options should be used to exclude certain VMs from the backup. I'm reading this to mean that no VMware snapshots should be made of the VMs listed with this option.
I'm using the option "--dsset" to specify a datastore containing (at the moment) three VMs. I'm trying to exclude one or more with "--novmset" but ALL the VMs in the datastore are getting snapshoted anyway.
No error messages in the log, everything works fine, except that the "novmset" seems to be ignored.
Anyone have any ideas?
Here's the relevant lines from the .cfg-file that is used.
# VIBE Backup Configuration File
Solved! SEE THE SOLUTION
2009-06-16 02:17 PM
I've finally have had the opportunity to test this again. I'd really appreciate a fix for this, as it is now I've had to create a separate NFS store for the VMs that I do not want to do a VMware snapshot of prior to taking the NetApp snapshot.
Attached are three logs.
log1.log: Verbose log when the "novmset" flag is NOT defined
log2.log: Verbose log when the "novmset" flag is defined as "novmset:STOPKIROOT"
log3.log: Same as log2 but with debug logging
2009-06-18 09:51 PM
Hi, all. I have a working fix for this that I plan to post to the ToolChest, but I'd like to get you to test it if you would before I release it to make sure it meets you needs. Please send me a private message and I'll get the test application/installer of VIBE over to you. Thanks,
2009-08-27 01:59 AM
I've got the same problem with VIBE but I can't get it fixed ! Is there any fix or a workaround available to solve this problem?
Thanks in advance for your help!!
2009-08-27 03:43 AM
Matt distributed a new version (1.0.12) that had the bug fixed so that novmset now works. The new version is not available yet on NOW what I can see (http://now.netapp.com/NOW/download/tools/vibe/).
If you send me an email I can send you the not official 1.0.12 version. I've benn running it in production several weeks.