Use the BackupPC $Conf{DumpPreUserCmd} to suspend the VM before dumping
and the $Conf{DumpPostUserCmd} to start it back up afterwards.
Something like:
$Conf{DumpPreUserCmd} = '$sshPath -q -x -l root your-vmware-server-name
vmware-cmd /path/to/your/vm.vmx suspend'
$Conf{DumpPostUserCmd} = '$sshPath -q -x -l root your-vmware-server-name
vmware-cmd /path/to/your/vm.vmx start'
Les Mikesell wrote:
> Stephen Zemlicka wrote:
>
>> I like the idea of backing up the vmware image. That way you have very
>> little restore time. Just copy and you're up and running. No reconfig
>> necessary. If you use rsync, shouldn't it just copy the changed data? I
>> understand files on the image might move around but majority should stay the
>> same and therefore the data wouldn't have to be copied for each backup.
>>
>
> If you can shut down the virtual machine for the duration of the rsync,
> the scheme should work, however the files may be huge and they don't
> mesh very will with backuppc's pooling concept since each change will
> result in a new full copy taking file space even though only the
> differences would be transferred.
>
>
--
Puryear Information Technology, LLC
Baton Rouge, LA * 225-706-8414
http://www.puryear-it.com
Visit http://www.puryear-it.com/pubs/ebooks/ to download your free
copies of:
"Best Practices for Managing Linux and UNIX Servers"
"Spam Fighting and Email Security in the 21st Century"
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
