[Borgbackup] Can different error codes of individual files be mapped to different results?

Thorsten Schöning tschoening at am-soft.de
Mon Sep 6 13:19:12 EDT 2021


Hi everyone,

I'm backing things up using SSHFS and ran into two different, but
as well related problems:

# Dial-up DSL

Sometimes SSHFS is hosted by some dial-up DSL internet connection and
that connection might simply reconnect during the time a backup is
executed. SSHFS simply disappears in those cases. When this happens,
it seems that BORG only recognizes missing files and considers that a
warning instead of an error.

> [2021-09-03 01:53:32,906] INFO: /mnt/[...]/root_and_some_zfs/root/vmlinuz.old: stat: [Errno 2] No such file or directory: '/mnt/[...]/root_and_some_zfs/root/vmlinuz.old'
> [2021-09-03 01:53:32,906] INFO: E /mnt/[...]/root_and_some_zfs/root/vmlinuz.old
> [...]
> [2021-09-03 01:53:33,575] INFO: security: saving state for [...] to /home/ams_d_bak_borg/.config/borg/security/[...]
> [2021-09-03 01:53:34,918] INFO: security: current location   ssh://[...]
> [2021-09-03 01:53:34,918] INFO: security: key type           0
> [2021-09-03 01:53:34,918] INFO: security: manifest timestamp 2021-09-02T23:53:32.947038
> [2021-09-03 01:53:34,919] INFO: RemoteRepository: 3.22 MB bytes sent, 3.21 kB bytes received, 116 messages sent
> [2021-09-03 01:53:34,948] INFO: terminating with warning status, rc 1
> [2021-09-03 01:53:34,984] INFO: [...]: Running consistency checks

# Expected missing files

I'm backing up using SSHFS from different devices, like some NAS. That
NAS stores backups from some Linux hosts and those backups contain
symlinks using absolute paths as well. Those symlinks can't be
properly resolved on the NAS of course, so it answers with missing
files. Compared to the former problem this time missing files are OK,
because I know things can't work differently and therefore BORG
aborting with errors wouldn't make too much sense.

> [2021-08-25 09:17:45,430] INFO: /mnt/[...]/root/cdrom: readlink: [Errno 2] No such file or directory: '/mnt/[...]/root/cdrom'
> [2021-08-25 09:17:45,430] INFO: E /mnt/[...]/root/cdrom

# BORGMATIC

I'm using BORGMATIC for individual backups, which allows me to easily
maintain individual settings for BORG and forward additional options.
If BORG would support some kind of switch to influence when missing
files are an error and when not, I would easiyl be able to distinguish
both use-cases above. In most cases I won't have any missing files.

# Error code mapping?

So, is there some error code mapping of individual files or alike?
Something to tell BORG when to exit with a warning compared to an
error? Is there any option I can change what BORG considers to be an
error under whcih circumstances?

Thanks!

Mit freundlichen Grüßen

Thorsten Schöning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   05151-  9468- 0
Tel:   05151-  9468-55
Fax:   05151-  9468-88
Mobil:  0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Geschäftsführer: Janine Galonska






More information about the Borgbackup mailing list