Rodrigo Ventura schrieb:
? gtar: ./mnt/cdrom: Cannot savedir: No such file or directory
? gtar: ./mnt/cdrom/: Warning: Cannot stat: No such file or directory
? gtar: ./mnt/cdrw: Cannot savedir: No such file or directory
? gtar: ./mnt/cdrw/: Warning: Cannot stat: No such file or directory
[...]
?
Steven Kurylo wrote:
Correct. But as I understand, snapshots in VMware work similar to
transaction logs in databases. The virtual disk file is locked
in its current state and further changes are temporarily written
to separate files until the snapshot is comitted or rolled back.
Yes.
So if
That's not obvious enough for me. Stepping outside the VMware world for
a moment, what the user is proposing is totally normal. We do it in the
virtualized storage world all the time. Stop the app, snap the image,
start the app, then back it up. I don't want to leave the app down the
entire tim
Correct. But as I understand, snapshots in VMware work similar to
transaction logs in databases. The virtual disk file is locked
in its current state and further changes are temporarily written
to separate files until the snapshot is comitted or rolled back.
Yes.
So if you want to backup/co
Stefan G. Weichinger schrieb:
> [EMAIL PROTECTED] schrieb:
>> There is a (moderately good) howto by me and an excellent one by Paul
>> Bijnens at this location : http://www.amanda.org/docs/howto-wrapper.html
Attached you find my current draft of handle_vms.sh, which I use with
amgtar to handle the
Curtis Preston wrote:
Unless you're coordinating with the OS, then taking a VMware snapshot
and copying it is equivalent to pulling the power plug on a server.
Will it power back up without corruption? 99.9% of the time, yes. Has
anyone who has been in the biz for a while had a scenario where
p
> Does anyone know the reason why you cannot snapshot
powered off machines?
I have learned that backups of VMware Windows-XP guests
under Linux are easy, and seem reliable, without starting or
restarting VMware or the VM. The method we use requires
that the Windows NTFS filesystem be set up
Patrick M. Hausen schrieb:
> So if you want to backup/copy an entire VM with the guarantee of
> consistent hard disk state, you need to shut it down. Copying
> a multi gigabyte virtal disk file is bound to take quite some time.
>
> So you need to power down your virtual machine for what can amoun
Hello,
On Wed, Feb 27, 2008 at 07:40:26PM +, Rodrigo Ventura wrote:
> On Feb 27, 2008, at 7:00 PM, Patrick M. Hausen wrote:
>
>> Does anyone know the reason why you cannot snapshot powered off
>> machines?
>
>
> Hum, only the obvious answer pops to mind: because there is no state to
> snap
On Feb 27, 2008, at 7:00 PM, Patrick M. Hausen wrote:
Does anyone know the reason why you cannot snapshot powered off
machines?
Hum, only the obvious answer pops to mind: because there is no state
to snapshot at all! A powered-off machine has no state, besides the
contents of the harddri
Hi, all,
On Wed, Feb 27, 2008 at 01:27:11PM -0500, Curtis Preston wrote:
> Unless you're coordinating with the OS, then taking a VMware snapshot
> and copying it is equivalent to pulling the power plug on a server.
> Will it power back up without corruption? 99.9% of the time, yes. Has
> anyone
Unless you're coordinating with the OS, then taking a VMware snapshot
and copying it is equivalent to pulling the power plug on a server.
Will it power back up without corruption? 99.9% of the time, yes. Has
anyone who has been in the biz for a while had a scenario where
powercycling a box caused
On Feb 27, 2008, at 4:12 PM, Jean-Louis Martineau wrote:
What's in the "FAILED AND STRANGE DUMP DETAILS" section of the
email report?
I found out, following a previous reply suggestion, errors like these:
/-- omni / lev 1 FAILED [dump (16333) /usr/bin/tar returned 2]
sendbackup: start [omn
Stefan G. Weichinger wrote:
Because we are fearing problems?
We do a vm snapshot to a backup server. Amanda backs up the snapshot
from the backup server.
And it is reliable?
We've never had a problem restoring machines. We often take a snapshot
of a production machine and turn i
What's in the "FAILED AND STRANGE DUMP DETAILS" section of the email report?
Which amanda release?
Which tar release?
Did you upgraded something on the system?
Jean-Louis
Rodrigo Ventura wrote:
Hello,
I'm getting sporadically errors like this:
FAILURE AND STRANGE DUMP SUMMARY:
omni/
On 2008-02-27 15:56, Rodrigo Ventura wrote:
Hello,
I'm getting sporadically errors like this:
FAILURE AND STRANGE DUMP SUMMARY:
omni/ lev 1 FAILED [dump (30447) /usr/bin/tar
returned 2]
and I don't have a clue on what's going on. I grepped /tmp/amanda and
found no refere
Hello,
I'm getting sporadically errors like this:
FAILURE AND STRANGE DUMP SUMMARY:
omni/ lev 1 FAILED [dump (30447) /usr/bin/tar
returned 2]
and I don't have a clue on what's going on. I grepped /tmp/amanda and
found no reference to this. Any clues?
Cheers,
Rodrigo
17 matches
Mail list logo
