BackupPC-users

Re: [BackupPC-users] how to make a backup available as a backup basis for another client?

2009-01-26 19:33:23
Subject: Re: [BackupPC-users] how to make a backup available as a backup basis for another client?
From: Les Mikesell <les AT futuresource DOT com>
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Mon, 26 Jan 2009 18:31:36 -0600
Matthias Meyer wrote:

>>
>>>> you have x number of remote hosts, all running the same OS and
>>>> presumably have almost identical files (size, permissions etc)? and you
>>>> want back one up and then clone that backup for each of the other
>>>> machines to avoid transfering the data numerous times?
>>>>
>>>> you should add the -H flag to cp or rsync to take hardlinks with:
>>>>
>>>> rsync -aH /var/lib/backuppc/pc/host1/0 /var/lib/backuppc/pc/host2/0
>>>> cp -aH /var/lib/backuppc/pc/host1/0 /var/lib/backuppc/pc/host2/0
>>> Since he is only copying one backup run there probably won't be any hard
>>> links within the run and cp/rsync won't know or care about links to the
>>> pool.  What you really need here is to make a tree of hardlinks instead
>>> of a copy but I don't think any standard tools do that.
>>> cp --help
>> [...]
>>   -l, --link                   link files instead of copying
>>
>> So a cp -rl /var/lib/backuppc/pc/host1/0 /var/lib/backuppc/pc/host2/0
>> should do the trick.
>>
>> Then you can trigger a full backup - the rsync will only transfer
>> changed files.
>>
>>> But, you are going to remove the extra copy as soon as a new full run
>>> completes so the space probably doesn't matter. The only place I think
>>> it might go wrong is if backuppc hard-links matching files in the next
>>> run to the copy from the previous instead of the hash match in the
>>> pool.  If that's the case you will end up with files that persist
>>> under each PC's directories but never end up linked to the pool and
>>> thus to each other.
>> The base backup host1/0 should be complete (e.g. BackupPC_link should
>> have been run).
>>
>> HTH,
>>
>> Tino.
>>
> That didn't seems to work, The files have different inode numbers:
> FileServer:~# ls -li /var/lib/backuppc/pc/vista-test/0/fC
>  4644195 -rw-r-----  3 backuppc backuppc  144 2009-01-22 07:55 attrib
>  4661809 drwxr-x--- 26 backuppc backuppc 4096 2009-01-22 06:53 fBoot
> 16778620 -rw-r-----  4 backuppc backuppc 2752 2008-12-26 09:21 fBOOTSECT.BAK
>  4840358 drwxr-x---  2 backuppc backuppc 4096 2009-01-22 06:53 fConfig.Msi
>  4840370 drwxr-x--- 11 backuppc backuppc 4096 2009-01-22 07:43 fDocuments
> and Settings
>  4825126 drwxr-x---  3 backuppc backuppc 4096 2009-01-22 07:55 fDokumente
> und Einstellungen
> 
> FileServer:~# ls -li /var/lib/backuppc/pc/vistabase/0/fC
>  4644195 -rw-r-----  3 backuppc backuppc  144 2009-01-22 07:55 attrib
> 17202565 drwxr-x--- 26 backuppc backuppc 4096 2009-01-26 22:39 fBoot
> 16778620 -rw-r-----  4 backuppc backuppc 2752 2008-12-26 09:21 fBOOTSECT.BAK
> 17202564 drwxr-x---  2 backuppc backuppc 4096 2009-01-26 22:39 fConfig.Msi
>  3451763 drwxr-x--- 11 backuppc backuppc 4096 2009-01-26 22:39 fDocuments
> and Settings
> 17202590 drwxr-x---  3 backuppc backuppc 4096 2009-01-26 22:39 fDokumente
> und Einstellungen


You get new directories and attrib files in each run.  The only plain 
file in the list does have the same inode number - and a count of 4 links.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com




------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/