VMWare documentation on vcbSnapAll is lacking. Anyone have any examples of how they use this to snap to a local partition? I keep getting I want to backup all guests to a SMB mount /mnt/backups.
vcbSnapAll uses the same command line options as vcbMounter. Just type vcbSnapAll and it states this fact.
An example of snaping to a local partition is:
vcbSnapAll -a poweronstate:on -r /tmp/backup (local ext3)
vcbSnapAll -a poweronstate:on -r /vmfs/volumes/storage1/backup (local vmfs)
subdirectories based on the virtual machine name will be created under the ./backup directory for each vm, for example
i got a little extra question.. four our backup strategy we want to use the SnapAll command to backup to a location...
this seems to work the first time. but the second time it fails with the message directory already exits.. is there a paramters where i can say 'overwrite' ?
(or edit the SnapAll (vcbMounter) scripts so they will check if the folder exits and if so continue?
Did you look in the /var/log/vmware/vcbSnapAll-nnnn/machinename-failed (or -ok)
Should tell you more about the failure if you have anything in the log. If you dont you still have a problem with the command, though it looks good to me. If all your vm's were powered off you still should get status info showing 0 machines with matched.
I think from what I am seeing you probably have a issue with your backuptools.conf, post an example and maybe we can fix. Otherwise there are some good posts regarding the VCHOST and other parameters which tripped me up. I resorted to VCHOST=localhost and using root account & pw to get working for testing.
I had the same problem and have not yet tried to resolve as still testing. There is a way to deal with this on the vcbRestore utility by using -b prompt|overwrite|keep|abort that you might try. Otherwise you will want to add something in the script to deal with it, not sure if you care about the directory existing if you are just going to overwrite. I would suggest a clean up process prior to running if the -b switch doesnt work. If it does please post so I will know!
No info in /var/log/vmware/vcbSnapAll-XXX logs at all.
\# Configuration file for all the vcb* wrapper scripts.
\# You can override the settings in this file using command line
\# Also, all vcb utilities can be pointed to a different config file
\# by setting the VCB_CONFIG_FILE environment variable.
\# URL for the VC SDK instance to connect to. The format is
\# Example: NAS share labelled "esxnas42" mounted on "/mnt/nas/42":
\# \[esxnas42]= /mnt/nas/42
\## Default settings for importing legacy VMs that have been backed up
\## with "vmsnap.pl" on ESX 2.5.x.
\# Datastore path and directory under which the VM is going to be
\# restored. You can use %VMNAME% to indicate the legacy VM's name
\# in the path
\# DSPATH="\[vol0] %VMNAME%"
\# The host the virtual machine is going to be associated with.
\# The default setting associates the VM with the host the restore
\# is being run on.
\# Resource pool the VM is part of. You can use %VMHOST% to specify the
\# host name the VM is going to be associated with.
\# You can use the "resourcepools" command of "vcbUtil" to get a list of
\# all known resource pools on the VC/ESX server.
\# VC folder in which the virtual machine is going to be placed in.
\# User permissions are associated with folders.
\# You can use the "vmfolders" command of "vcbUtil" to get a list of
\# all folders that can hold virtual machines.
The only thing I see that doesnt match mine is the following:
whereas I have:
which I am sure is the default. Try changing this back and see what happens, otherwise the only thing I can think of is that you make sure the password is correct (I am sure it is but something to doublecheck)
Seems to be working now...
I did the following:
1. Changed TEMPDIR=/tmp to /backups/tmp
2. Tried to run a vcbSnapAll and it failed.
3. Changed back to TEMPDIR=/tmp
4. Tried to run a vcbSnapAll it worked like a champ!
5. Slammed my head on the desk.
Did you ever get this issue worked out? I have the same issue and can't come up with a solution.
i got a little extra question.. four our backup strategy we want to use the
SnapAll command to backup to a location...
this seems to work the first time. but the second time it fails with the
message directory already exits.. is there a paramters where i can say
(or edit the SnapAll (vcbMounter) scripts so they will check if the folder
exits and if so continue?[/i]
here is the script I use to run a backup this way. It runs nightly via cron
rm -rf /mnt/backups/backupdsk/ESX1/*
/usr/sbin/vcbSnapAll -a powerstate:on -r /mnt/backups/backupdsk/ESX1 #> /dev/null 2>&1