Re: [BackupPC-users] RefCntFsck

2017-09-19 Thread Gandalf Corvotempesta
Ok, so this is expected. Thank you. 2017-09-19 14:39 GMT+02:00 Craig Barratt via BackupPC-users : > If a backup fails or is aborted, BackupPC_refCntUpdate is run on the last > two backups, independent of the $Conf{RefCntFsck} setting. > > Craig > > > On

Re: [BackupPC-users] RefCntFsck

2017-09-19 Thread Craig Barratt via BackupPC-users
If a backup fails or is aborted, BackupPC_refCntUpdate is run on the last two backups, independent of the $Conf{RefCntFsck} setting. Craig On Tuesday, September 19, 2017, Gandalf Corvotempesta < gandalf.corvotempe...@gmail.com> wrote: > refCnt is also run on backup #1 (that in my case is the

Re: [BackupPC-users] RefCntFsck

2017-09-19 Thread Gandalf Corvotempesta
refCnt is also run on backup #1 (that in my case is the incremental that i've aborted). is this correct ? I had a similiar issue with the alpha version, where an fsck was always executed, but AFAIK this bug was fixed when BPC 4 was released as stable. 2017-09-19 14:11 GMT+02:00 Gandalf

[BackupPC-users] RefCntFsck

2017-09-19 Thread Gandalf Corvotempesta
Can someone explain me the meaning of $Conf{RefCntFsck} = 1; ? If I understood properly, based on docs, $Conf{RefCntFsck} = 1 will run a refCnt process if the latest backup is full. In my case, I have a single full backup and i've aborted an incremental one, then refCnt is run on the full