Well seen Guillermo ! All thanks !
Fred
Le 16/09/2022 à 12:46, Guillermo Rozas a écrit :
I'm not in the computer to check now, but there is an option in rsync
that controls wether it crosses or not filesystem boundaries
(--one-filesystem??). I think this is enabled by default in V4. If the
fo
I'm not in the computer to check now, but there is an option in rsync that
controls wether it crosses or not filesystem boundaries
(--one-filesystem??). I think this is enabled by default in V4. If the
folders you're missing are mounted as a sub-directory of a folder you
backup, they won't be backu
A v3 / v4 pool issue?
I never looked into that, but maybe can be your problem...
Il giorno ven 16 set 2022 alle ore 12:20 Frédéric Mathy <
frede...@famillemathy.fr> ha scritto:
> Thanks.
> I changed the exclude directories but the problem is the same.
> Backup is empty for [boot] directory on /d
Thanks.
I changed the exclude directories but the problem is the same.
Backup is empty for [boot] directory on /dev/mmcblk0p2 and incomplete
for data on /dev/sda2.
The backup is correct for /dev/sda1.
I don't understand why. All was ok on backuppc 3...
Fred
Hello, in my experience I avoid gl
Le 16/09/2022 à 00:33, Frédéric Mathy a écrit :
Hi,
A few months ago on debian bullseye, I updated backuppc to 4.4.0-3
(rsync_bcp 3.1.3.0)
Everything seemed to be fine with the rsync method via SSH on port 2022.
After several months, I discover that some directories remain empty and
others ar
