Re: [BackupPC-users] Disk space used far higher than reported pool size

Subject:

From:

Timothy J Massey <tmassey AT obscorp DOT com>

To:

"General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>

Date:

Thu, 31 Oct 2013 12:01:06 -0400

Holger Parplies <wbppc AT parplies DOT de> wrote on 10/30/2013 10:24:05 PM: > as I understand it, the backups from before the change from smb to rsyncd are > linked into the pool. Since the change, some or all are not. Whether the > change of XferMethod has anything to do with the problem or whether it > coincidentally happened at about the same point in time remains to be seen. > I still suspect the link to $topDir as cause, and BackupPC_link is independent > of the XferMethod used (so a change in XferMethod shouldn't have any > influence).

To add my anecdote, I use a symbolic link for all of my BackupPC hosts: a couple dozen? And they all work fine. It's been my standard procedure for almost as long as I've been using BackupPC.

Example:
ls -l /var/lib
lrwxrwxrwx. 1 root root 22 Apr 22 2013 BackupPC -> /data/BackupPC/TopDir/

mount
/dev/sda1 on /data type ext4 (rw)

I understand phobias from earlier problems (see my earlier e-mail about my thoughts on NFS and backups...) but I do not think this one is an issue.

> If the log files show nothing, we're back to finding the problem, but I doubt > that. You can't "break pooling" by copying, as was suggested. Yes, you get > independent copies of files, and they might stay independent, but changed > files should get pooled again, and your file system usage wouldn't continue > growing in such a way as it seems to be. If pooling is currently "broken", > there's a reason for that, and there should be log messages indicating > problems.

You are 100% correct; but it depends on how you define "break". Making a copy of a backup will absolutely break pooling--for the copy you just made! :)

It won't prevent *future* copies from pooling, certainly. But it sure can fill up a drive: even if pooling *is* working correctly for new copies, they can still fill up the drive *and* BackupPC_nightly won't do a thing about it.
Tim Massey


Out of the Box Solutions, Inc. Creative IT Solutions Made Simple! http://www.OutOfTheBoxSolutions.com tmassey AT obscorp DOT com		22108 Harper Ave. St. Clair Shores, MI 48080 Office: (800)750-4OBS (4627) Cell: (586)945-8796

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk

_______________________________________________
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>

Previous by Date:

Re: [BackupPC-users] Disk space used far higher than reported pool size, Timothy J Massey

Next by Date:

Re: [BackupPC-users] Disk space used far higher than reported pool size, Marcel Meckel

Previous by Thread:

Re: [BackupPC-users] Disk space used far higher than reported pool size, backuppc

Next by Thread:

Re: [BackupPC-users] Disk space used far higher than reported pool size, Marcel Meckel

Indexes:

[Date] [Thread] [Top] [All Lists]