WARNING: . . . .failed verification -- update discarded (will try again).

Mac User FR macuserfr at free.fr
Fri Jun 5 06:36:02 GMT 2009

Here is the mail from henri.
Best regards,


Début du message réexpédié :

> De : henri <henri at stmargarets.school.nz>
> Date : 4 juin 2009 00:30:32 HAEC
> À : Mac User FR <macuserfr at free.fr>
> Objet : Rép : WARNING: . . . .failed verification -- update  
> discarded (will		try again).
> I was going to write a daemon to manage suspend and resume of VM  
> images during backups. After designing the system (on paper - not in  
> code) I realized that this system was probably not required for  
> dealing with VM backups.
> The reason I came to this conclusion was because I realized I could  
> just enable auto-protect (automated snapshots of the VM) and then  
> backup the live VM. Is this not the case?
> Any information or experiences would be very helpful. I would be  
> particularly interested to know if anyone backed up running VM and  
> then had issues rolling back to a known good snap-shot?
> Maybe the design (still in my draw) will actually be of some use?
> Thanks.

Le 5 juin 09 à 00:42, JW a écrit :

> On Thursday 04 June 2009 03:29:49 you wrote:
>> r you can use snapshots as suggested by
>> henri. I don't know what would exactly a snapshot do. A snapshot by
>> the virtualization program or by the filesystem? I think if the
>> snapshot is made by the virtualization program it may be safe for ram
>> recovering issues, but filesystem snapshot is not. You will still  
>> need
>> to save regularly open files from the guest OS.
> Thank you for taking the time to answer. As an aside, I did not  
> receive any
> emails from "henri" and i don't see any on the list - what did he  
> say? I'm
> sure he's talking about VM snapshots, not FS. I am aware of the  
> issues you
> raised and I do, in fact, backup the internal contents of the Guest  
> OS. But I
> also backup the actual VM disk-image-files because recreating VMs from
> scratch is not fun - I can usually use the backup, and then "restore"
> whatever data might be missing "inside" the VM guest OS. At least  
> the main
> system setup is preserved.
> In other words, it's a third-level backup just to save me  time in  
> the event
> of catastrophic failure. I also have an original copy of the VM from  
> when it
> was first created (and that backup was made with the VM  guest  
> powered off).
>> I have absolutely no idea about the "will try again" part. Maybe  
>> Wayne
>> or Matt could give you the answer.
> Carlos' answer was pretty good. Thank you.
> 	JW
> -- 
> ----------------------
> System Administrator - Cedar Creek Software
> http://www.cedarcreeksoftware.com

More information about the rsync mailing list