Thanks for your response Michael, some comments inline
Le 2019-04-04
23:22, Michael Stowe a écrit :
> On 2019-04-03 05:02, Daniel Berteaud
wrote:
>
> First, as soon as there's a single error (most common are
"file has
> vanished"), BackupPC reports 3 errors.
>
> Often, the
backup reports an error count of 2, with these kind of
> errors :
>
> [
213 lignes sautées ]
> rsync_bpc: stat
"/.config/google-chrome/CertificateRevocation/5022"
> failed: No such
file or directory (2)
> rsync_bpc: stat
>
"/.config/google-chrome/CertificateRevocation/5022/_metadata" failed:
>
No such file or directory (2)
> rsync_bpc: stat
"/.config/google-chrome/CertificateRevocation/5023"
> failed: No such
file or directory (2)
> rsync_bpc: stat
>
"/.config/google-chrome/CertificateRevocation/5023/_metadata" failed:
>
No such file or directory (2)
These files seem likely to have been
updated or removed during the backup run. That directory contains
bookmarks, cookies, extensions, and all kinds of things one might expect
to change.
My log snippets are just examples. I know this directory
contains moving parts, I just try to understand why I do get this error
while the mentionned dirs exist both on the source, and in the backup.
To me this makes no sense. Either the dir doesn't exist during the scan,
and rsync won't try to transfert it, or the dir exists and rsync
transfert it, or the dir exists during the scan, but disapears before
rsync transfert it. In this last case, I expect this kind of errors in
the logs, but the directory should not exists in the backup.
> The
symptoms here and the directory in question matches the behavior that is
expected when backing up a Samba share used by Windows systems with
access to a recycle bin. Windows will rename a file into the recycle
bin, so you'll see this when you back up the original file -and- the
recycle bin. I can't imagine why one would normally want to back up a
recycle bin, since presumably one would have already backed up the file
before it was deleted, so it's probably simplest just to exclude the bin
from the backups. Alternatively, one can remove the bin (or access to
it) so that Windows clients delete the original files, though that also
makes backup of the recycle bin somewhat pointless.
This was also just
the first occurence of the error I found in my logs, I have the same
errors for other files. Besides that, in this case, from BackupPC's POV,
it doesn't matter if the directory is used a Recycle Bin for samba. It's
just a directory where files which were previously elswhere have been
moved. It could have been done by a human intervention in a FooBar
directory.
I'm just trying to understand what the error means
--
Daniel Berteaud
FIREWALL-SERVICES SAS, La sécurité des réseaux
Société de Services en Logiciels Libres
Tel/Fax : +33.5 56 64 15 32
Mail : dan...@firewall-services.com
Web : https://www.firewall-services.com
_______________________________________________
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/
