BackupPC-users

Re: [BackupPC-users] cpool always empty?

2011-11-21 15:47:30
Subject: Re: [BackupPC-users] cpool always empty?
From: Bob Proulx <bob AT proulx DOT com>
To: backuppc-users AT lists.sourceforge DOT net
Date: Mon, 21 Nov 2011 13:45:53 -0700
Les Mikesell wrote:
> Bob Proulx wrote:
> > Further investigation shows that BackupPC is throwing errors during
> > the link run.  Seeing many of these in the log file.  (It would be
> > great if errors like this were emailed to the admin as part of the
> > email notification from BackupPC.  I had not noticed them.)
> 
> The usual causes for this are that you ... changed the TopDir
> location after installation (which doesn't work in versions before
> 3.2).

You have identified the problem!

Sorry for neglecting to provide a complete context.  I am running
version 3.1.0 from Debian Stable Squeeze.  All filesystems are ext3.
I installed it and the default installation placed the files in a new
directory at /var/lib/backuppc.  But then to have sufficient space on
its own dedicated filesystem I created a new lvm partition and moved
it to /srv/backuppc afterward.  I edited the configuration file and
changed to "$Conf{TopDir} = '/srv/backuppc';" which I thought would
have been sufficient.  I did this before performing any backups so
that all data would be stored in the new location.  Obviously I left
some remnant behind which is causing the problem.

I followed the docs on the topic "Copying the pool" which recommend
this process.  Unfortunately that section of the docs were a little
sparse on details.  I didn't see an equivalent topic page on the wiki
for this.

Update: I just now found this page that I had not found previously
even though I had looked for that type of page.  It doesn't seem to be
very well linked into the upper documentation.

  
http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=Change_archive_directory

I am reading it in detail now and digging into what detail I missed
previously.

> If you can't update to 3.2, the best approach is to mount your
> archive in the expected location or symlink it so it appears there.

Obviously due to the advantages of a long term operating system
release I would prefer to remain on the Debian Stable release.  If
this is simply a misconfiguration on my part then I should be able to
correct it.  Now that you have pointed me to the area of the problem I
am sure I can debug it further and determine my problem.

Thanks!
Bob

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
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/