Re: [Duplicity-talk] Direct backup of LVM snapshot partitions?

[edgar . soldin]

On 12.12.2012 17:09, T. Prost wrote:
> Am Mittwoch, den 12.12.2012, 14:59 +0100 schrieb address@hidden: 
>> On 12.12.2012 14:32, T. Prost wrote:
>>> Am Mittwoch, den 12.12.2012, 11:42 +0100 schrieb address@hidden: 
>>>> On 12.12.2012 11:37, T. Prost wrote: > Am Dienstag, den 11.12.2012,
>>>> 17:02 +0100 schrieb address@hidden: >> On 11.12.2012 15:26, T.
>>>> Prost wrote: >>> Am Montag, den 10.12.2012, 19:01 +0100 schrieb GDR!: 
>>>>>>>> On 12/10/2012 01:16 PM, George MacKerron wrote: > Thanks Edgar.
>>>> Yes, >>>> I'm already using LVM snapshots. I just wanted to then back
>>>> up the raw >>>> volume data, rather than mount the snapshot and back up
>>>> the files it >>>> contains. >>>> >>>> Just to justify what he's doing
>>>> and point that "just mount it" is not a >>>> good answer: he might want
>>>> to back up a Windows partition that he's >>> >>> BTW: Are there known
>>>> Problems when backing up a Windows partition with >>> duplicity ? >>>
>>>>>>>> like how? with cygwin duplicity? under linux mounted or via
>>>> device dump? > > mount in linux > backup to local external disk > > If
>>>> problems aren't known as duplicityy-specific, can there be general >
>>>> problems backing up or even reading a windows volume in this config and
>>>>> environment ?
>>>>
>>>> using ntfs-3g you should be quite safe. of course there is ntfs
>>>> specific meta-data that will not/cannot be backed up by duplicity. but
>>>> if you are concerned for your data, simply watch out for bugs in
>>>> ntfs-3g, otherwise you should be fine.
>>>
>>> ... forgot to mention it was an FAT volume :-|
>>>
>>> And as far as I can see, I see success in recovering the SNAPSHOT
>>> directory, but reassembling the files in the multivol seems to produce
>>> anything but the original files :-(
>>>
>>> Sorry ...
>>>
>>
>> you're aware the discussion started with LVM snapshots, right?
>>
>> no clue what you mean by "recovering the SNAPSHOT directory" or 
>> "reassembling the files in the multivol".
> 
> Sorry, I became attentive to the discussion because of the idea, someone
> "might want to back up a Windows partition" - what I had done earlier
> and now running into problems with the recovery :-(
> 
> But you're right. I expressed that in a really bad manner :-(
> 
> The recovery created two directories: multivol_snapshot and snapshot,
> where I can read the files in "snapshot" but can't reassemble those in
> the multivol.
> 

there is no recovery in duplicity.. what recovery do you mean? ..ede