Nils Breunese (Lemonbit lemonbit.nl> writes:
> The $TopDir relocation after installing a packaged version is
> discussed pretty regularly on this list (every week?). The easier
> solution is to mount your backup drive/array on the location used by
> the packager (/var/lib/backuppc in the cas
the $TopDIR must be on the same volume as the backup files. so if $TopDIR
is /var/lib/backuppc and /var is a 500GB drive then your pc directory needs
to be somewhere in /var. What I do and what is common to do is to mount up
the target drive somewhere temporarily and `cp -Rp /var/lib/backuppc
/ta
Kimball Larsen wrote:
> Ok, I finally found and tracked down my problem.
>
> I'm using BackupPC on Ubuntu 7.10, which installs BackupPC 3.0.0.
> Turns out, changing the TopDir location does NOT change the location
> of the pool files - they are hardcoded to live in /var/lib/backuppc.
>
> Acco
Ok, I finally found and tracked down my problem.
I'm using BackupPC on Ubuntu 7.10, which installs BackupPC 3.0.0.
Turns out, changing the TopDir location does NOT change the location
of the pool files - they are hardcoded to live in /var/lib/backuppc.
According to here:
http://backuppc.wi
Kimball Larsen wrote:
> Ok, I found the problem. Looks like my cpool is in the wrong place,
> apparently:
>
> ln: creating hard link `/var/lib/backuppc/cpool/b/7/6/
> b763efe12301fe7645e82fb46d53b4e3' to `/mnt/plump/backuppc/pc/
> 192.168.0.8/10/attrib': Invalid cross-device link
>
> It look
Ok, I freely admit that I'm in over my head here... I am NOT a perl
programmer. However, here is the method that is puking when trying to
create the links:
sub MakeFileLink
{
my($bpc, $name, $d, $newFile, $compress) = @_;
my($i, $rawFile);
return -1 if ( !-f $name );
for ( $
Ok, I found the problem. Looks like my cpool is in the wrong place,
apparently:
ln: creating hard link `/var/lib/backuppc/cpool/b/7/6/
b763efe12301fe7645e82fb46d53b4e3' to `/mnt/plump/backuppc/pc/
192.168.0.8/10/attrib': Invalid cross-device link
It looks like my cpool is in /var/lib/backupp
Kimball Larsen wrote:
>
>>> Pool is used if you don't have compression enabled, cpool if you do.
>>> Whichever is used must be on the same filesystem as the pc directory
>>> tree so that hardlinks work between them. If you are getting errors
>>> making the links, check that you have space (df)
On Feb 27, 2008, at 1:36 PM, Kimball Larsen wrote:
On Feb 27, 2008, at 1:33 PM, Les Mikesell wrote:
Kimball Larsen wrote:
Actually, I may have answered my own question somewhat:
It appears (based on my reading of a message here:
http://www.mail-archive.com/backuppc-users@lists.sourceforge.ne
On Feb 27, 2008, at 1:33 PM, Les Mikesell wrote:
Kimball Larsen wrote:
Actually, I may have answered my own question somewhat:
It appears (based on my reading of a message here:
http://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg09017.html
) that my pool is hosed.
Specifically,
Kimball Larsen wrote:
> Actually, I may have answered my own question somewhat:
>
> It appears (based on my reading of a message here:
> http://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg09017.html
> ) that my pool is hosed.
>
> Specifically, my cpool directory has several gigs
Actually, I may have answered my own question somewhat:
It appears (based on my reading of a message here:
http://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg09017.html
) that my pool is hosed.
Specifically, my cpool directory has several gigs of data in it, but
my "pool" direc
On Feb 27, 2008, at 1:11 PM, Les Mikesell wrote:
> Kimball Larsen wrote:
I notice that the cpool directory is owned by root. Should it
be owned by the backuppc user instead?
>>> Yes, it must be writable by the backuppc user. Your logs are
>>> probably full of "unable to link" e
Kimball Larsen schrieb:
> On Feb 27, 2008, at 11:49 AM, Les Mikesell wrote:
>> Kimball Larsen wrote:
>>> I've recently had to move my backuppc filesystem from one machine
>>> to another. My machines are all backing up just fine, I'm able to
>>> see all my old backups and restore files from t
Kimball Larsen wrote:
>
>>> I notice that the cpool directory is owned by root. Should it be
>>> owned by the backuppc user instead?
>> Yes, it must be writable by the backuppc user. Your logs are
>> probably full of "unable to link" errors.
>>
>
> Yeah, I've been getting stuff like this:
On Feb 27, 2008, at 11:49 AM, Les Mikesell wrote:
> Kimball Larsen wrote:
>> I've recently had to move my backuppc filesystem from one machine
>> to another. My machines are all backing up just fine, I'm able to
>> see all my old backups and restore files from them with no
>> problem.. h
Kimball Larsen wrote:
> I've recently had to move my backuppc filesystem from one machine to
> another. My machines are all backing up just fine, I'm able to see
> all my old backups and restore files from them with no problem..
> however, my pool size is reporting as 0MB. I checked the fil
I've recently had to move my backuppc filesystem from one machine to
another. My machines are all backing up just fine, I'm able to see
all my old backups and restore files from them with no problem..
however, my pool size is reporting as 0MB. I checked the filesystem,
and the size of the
18 matches
Mail list logo
