Can you simply edit the config BlackoutPeriods value to block out all of
the time?
On Thu, 27 Oct 2022, Rob Sheldon wrote:
Hi,
I'm in a bit of a pickle. I've been migrating my v4 pool to some new
infrastructure for ... a while. It's taking much longer than expected, and now
I have a
I'm sure we all got it. I just don't have an answer.
When I did the same upgrade, I went through the whole config file and
merged over my changes - it looked to me like there was a lot of stuff
that changed, so I wasn't confident that simply using my old config file
would work.
Since you
Are you using rsync over ssh? If so, one thing I like to try is to ssh manually
using the backuppc user.
On July 10, 2022 6:23:58 AM EDT, Taste-Of-IT wrote:
>Hi all,
>
>i have latest BackupPC running on Debian 10. I upgraded one system to Debian
>11. Backup before running well and without
They are stored on the host, so "leapfrogging" is fine (probably best to
make sure they run at different times to not bog down the network/client).
On Sat, 14 May 2022, gregrwm wrote:
i have brought up backuppc4 on a new kvm guest, and still also have
backuppc3 on another kvm guest. but is
I'm using
3.1.3.0-3 of backuppc-rsync
3.2.3-4+deb of rsync
4.4.0-3 of backuppc
0.62-1+b1 of libbackuppc-xs-perl
successfully.
libfile-rsync-perl is not installed
Hope that helps.
On April 11, 2022 6:35:40 AM EDT, Matthew Pounsett wrote:
>I seem to have encountered the same problem described
On Thu, 7 Apr 2022, backu...@kosowsky.org wrote:
So, I think that proves that it is rsync-bpc that is causing
trouble, as `rsync -a Downloads d` works perfectly fine.
Nope. Just proves you don't know how rsync_bpc works...
True. :) It was described as a "drop-in replacement" for rsync on the
() which doesn't
seem to help much. Do I need rsync-bpc installed on each backup client as
well?
On Thu, 7 Apr 2022, Jon Daley via BackupPC-users wrote:
I recently upgraded backuppc to V4 and the bcp version of rsync, and I can't
get anything to work. The migration to V4 seems to have gone well
I recently upgraded backuppc to V4 and the bcp version of rsync, and I
can't get anything to work. The migration to V4 seems to have gone well -
it took 2-3 days to run through all of the hosts (15 hosts with 105
backups)
All backups get an error like this:
2022-04-07 03:02:37 incr backup
