Hi,
For now I have decided to downgrade to rsync-bpc-3.1.2.0-2.el7.x86_64 from
EPEL. I was unable to reproduce the problem after downgrading rsync-bpc.
Note: I could reproduce the issue on other machines after updating to
rsync-bpc-3.1.3.0-1.el7.x86_64. It seems to me there is a bug in 3.1.3.
Hi Craig,
> On 9 Nov 2020, at 18:00, Craig Barratt via BackupPC-users
> wrote:
>
> Yes, it's perfectly fine to downgrade to rsync-bpc-3.1.2.0-2.el7. It's fully
> compatible with BackupPC 4.4.0. It would be good to know whether it behaves
> differently.
>
> What are your settings for
Yes, it's perfectly fine to downgrade to rsync-bpc-3.1.2.0-2.el7. It's
fully compatible with BackupPC 4.4.0. It would be good to know whether it
behaves differently.
What are your settings for $Conf{RsyncArgs} and $Conf{RsyncArgsExtra}?
Craig
On Mon, Nov 9, 2020 at 1:33 AM Pim Rupert
Hi all,
Since we updated to BackupPC-4.4.0-1.el7.x86_64 and
rsync-bpc-3.1.3.0-1.el7.x86_64 we see a potential memory bug in rsync_bpc.
Some rsync_bpc processes suddenly (within seconds) spike to 30-64 GB of RSS
memory usage. It only happens for 1-2 % of our backup processes, and we have
seen
