Sorry I wasn't clear. What I meant was to use VMWare's snapshot
functionality to solve Timo's problem (being able to restore the
pre-upgrade version of the VM), and not use bacula at all for this purpose.
You are right, of course, that the VMWare snapshot functionality
couldn't be used for a ba
If it's VMWare server, that wouldn't necessarily work - a snapshot opens
a new file which stores a binary delta of all changes since the snapshot
was taken and this file is being constantly written to. Backing it up
without taking account of this causes all sorts of fun.
I'm doing something simil
If you are thinking of doing it just before application upgrades or the
like, how about using VMWare's own snapshot functionality? They
implemented it for that exact purpose.
Timo Neuvonen wrote:
> "Kevin Keane" <[EMAIL PROTECTED]> kirjoitti viestissä
> news:[EMAIL PROTECTED]
>
>> Backing up
"Kevin Keane" <[EMAIL PROTECTED]> kirjoitti viestissä
news:[EMAIL PROTECTED]
> Backing up virtual machines while powered on is probably not a great
> idea, but there are good alternatives:
>
> - In your ClientRunBeforeJob script, power down the VM, and power it
> back up after the backup is done.
Backing up virtual machines while powered on is probably not a great
idea, but there are good alternatives:
- In your ClientRunBeforeJob script, power down the VM, and power it
back up after the backup is done. Alternatively, suspend and resume the VM.
I used to take this approach in my pre-bac
This isn't excatly a Bacula-related issue, but has anyone experiences how
consistent bacups can be achieved if I back up a linux host running a VMware
Server with some of the virtual machines "powered on"? Will the result be
something total garbage, or something that can reasonably succesfully be
r
