It's important to realize that a mixed V3/V4 installation will use more
inodes than just V3 or V4 alone. If you migrate an existing V3
installation to V4 (using BackupPC_migrateV3toV4), the inode usage to store
the backup trees will double, while the inode usage to store the pool files
will be the
On Fri, 14 Jul 2017 15:11:36 +0300
Tapio Lehtonen wrote:
> Running BackupPC 3 on Debian Wheezy. Ran out of inodes on 250 GB
> filesystem, max inodes was 15 million.
Use the force, change to a better FS: XFS (w/ the inode64 switch on)
eg: laptop 500GB HD filled @ 80% with many small pictures and
I was hoping someone would have answered you by now...
I think the long term answer is to update to 4.x where it won't be a
problem anymore but I have a feeling trying to upgrade while you're already
out of inodes would be a disaster.
Any chance you could install a parallel 4.x server with new st
Dear Kenneth Porter
On 15.07.2017 10:23, Kenneth Porter wrote:
>
> Does --one-file-system work with rsyncd (daemonized rsync)?
No, at least there is no such parameter documented for rsyncd.conf. You
may be able to provide a --one-file-system parameter upon startup,
though (untested).
With kind
On Sat, 15 Jul 2017 16:20:32 +1000
Adam Goryachev wrote:
> Actually, I think you will find that /proc, /dev, /sys, etc are
> actually different filesystems, and so will automatically be excluded
> by --one-file-system.
On 2nd thought, that looks logical from a FS point of vue, and good to
know.
Adam Goryachev wrote:
>
>
> On 15/7/17 13:00, Paul Fox wrote:
> > i didn't say i don't also have some excludes. i exclude /proc and
> > /sys. /dev is a separate filesystem. /tmp, believe it or not, i do
> > back up, to help with the morning-after regret of having lost a file i
> > thoug
Dear Bob Katz
On 15.07.2017 00:22, Bob Katz wrote:
>
> I have root as the user for backuppc for all my other hosts and it
> works. And it's also currently set up as root for backing up the server.
> I did try "backuppc" as the user before and it failed, maybe for
> different reasons. Anyway, I'm
On 7/14/2017 7:45 AM, Bob Katz wrote:
But is there a point to running sudo rsync if the object is to
use systemctl to run the daemon? Is that for a test or permanent? Yes,
I'm confused :-) And systemctl has already been initiated.
According to the man page, --foreground should be --no
On 7/14/2017 11:20 PM, Adam Goryachev wrote:
Actually, I think you will find that /proc, /dev, /sys, etc are
actually different filesystems, and so will automatically be excluded
by --one-file-system.
Does --one-file-system work with rsyncd (daemonized rsync)? I thought it
only applied when u