BackupPC-users

Re: [BackupPC-users] Problems with hardlink-based backups...

2009-09-02 09:32:13
Subject: Re: [BackupPC-users] Problems with hardlink-based backups...
From: "Jeffrey J. Kosowsky" <backuppc AT kosowsky DOT org>
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Wed, 02 Sep 2009 08:27:39 -0400
Jim Leonard wrote at about 22:18:07 -0500 on Tuesday, September 1, 2009:
 > Jeffrey J. Kosowsky wrote:
 > >  > I read the docs before setting it up and it was very obvious to me that 
 > >  > planning was required.  Then again, I've been doing this for a while. 
 > >  > But it *was* in the documentation, if not in-your-face explicit.
 > > 
 > > OK - can you show me where in the documentation it mentions the issue
 > > with copying/moving BackupPC data and hence the recommendation for
 > > using a separate fs just for BackupPC? I certainly wouldn't have
 > > intuited this issue from a generic mention about careful "planning".
 > 
 > Well, I installed the beta.  In said documentation, it clearly states: 
 > "BackupPC uses hardlinks to pool files common to different backups. 
 > Therefore BackupPC's data store (/vault/backstor) must point to a single 
 > file system that supports hardlinks. You cannot split this file system 
 > with multiple mount points or using symbolic links to point a 
 > sub-directory to a different file system (it is ok to use a single 
 > symbolic link at the top-level directory (/vault/backstor) to point the 
 > entire data store somewhere else). You can of course use any kind of 
 > RAID system or logical volume manager that combines the capacity of 
 > multiple disks into a single, larger, file system. Such approaches have 
 > the advantage that the file system can be expanded without having to 
 > copy it."
 > 
 > So forget what I said about reading between the lines -- it was lines 
 > themselves :)

Oh really - please show me again which line talks about it being
difficult to move/copy/backup the BackupPC database? Or did you forget
to copy/paste that part? 

All that the above says is that it needs to be on a single filesystem
which we all now. It says LVM/RAID "have the advantage that the file
system can be expanded without having to copy it" but nothing about it
warning that it is *hard* to copy which is the WHOLE POINT of this
silly argument. The statement about LVM/RAID is generic and would be
true about any program that needs all its files on a single
filesystem. However, nowhere does it even *hint* that copying is
hard.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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/

<Prev in Thread] Current Thread [Next in Thread>