Hi,

Kazuhiro Takenaka wrote:
> Hi Jean-Pierre,
>
>    
>> What is the purpose of Procedure3 ?
>>      
> The reason I want to backup by a file unit is to do
> incrementtal backup.
>
> There are two methods to do incremental backup a filesystem.
>
> Method1:
>      At first time, Make backup data that consist of one object.
>      The object is a full dump of the target filesystem.
>      "full" means that the dump contains all files on the target filesytem.
>
>      After second time, Pickup and archive the files changed from the
>      previous backup.
>
> Method2:
>      At first time, Make backup data that consist of two objects.
>
>      The first object is a empty dump of the target filesystem.
>      "empty" means that the dump contains no file. It contains
>      only the structure of the contarget filesytem.
>
>      The second object is an archive file that consists of all
>      files of the target filesystem.
>
>      After second time, Pickup and archive the files changed from the
>      previous backup.
>
> I prefer Method2 rather than Meshod1. Because it decouples structure
> and data better than the other. And I thought I could get an empty
> dump from an empty NTFS filesystem. So I thougt those procedures.
>
> But I cannot think those procedures are smart. I am planning to
> investigate what ntfsinfo provides.
>    

You will get roughly the same results with both
methods. With both of them you will have to restore
to a partition of the same size as the original.

ntfsinfo will not be very useful for restoring the
attributes.

>> The above procedure will restore the full partition
>> to a new partition of the same size. If you want to
>> do a partial restore (eg a subdirectory only), with all
>> the NTFS parameters, you have to design a specific
>> tool. In
>> http://pagesperso-orange.fr/b.andre/tools.zip
>> there is ntfscp.c which is an example of how you
>> can do that.
>>      
> You pointed me out another difficulty in my attempt.
> Archiving and Restoring files on NTFS filesystems need special commands
> for it. Because existing archive commands on Linux systems , such like
> tar, cpio and so on, can't keep NTFS specific file attributes.
> I will give a look to ntfscp.c.
>    

ntfs.c can only copy to NTFS. If you want to save
to non-NTFS you will have to define how you store
the attributes.

By the way I have just added the copy of object ids
to ntfscp, but you need to use the beta test version
of advanced ntfs-3g to benefit from object id copying.

Regards

Jean-Pierre




------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel

Reply via email to