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 Corvotempesta <gandalf.corvotempe...@gmail.com>: > 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 backup. > > Why? I've aborted an incremental, refCnt was already executed on the > full backup when I did that some days ago. Why BPC is still running > refCnt ? ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/