Is raspiBackup checking if CIFS network share is correctly mounted

[cmonty14]

Hi,
I have successfully deployed and setup raspiBackup.
The tool is writing daily backups to a CIFS network share (hosted on my FRITZ!Box).

# findmnt -t cifs
TARGET  SOURCE                                                 FSTYPE OPTIONS
/backup //192.168.178.1/fb6690/sandisk16g/raspi/loxberry/backup cifs   rw,relatime,vers=3.0,cache=strict,username=smb,uid=0,nof

Question:
Does raspiBackup perform a check if this network share is correctly mounted to /backup before starting backup process?
If yes, could you please advise where I find this check in source code?

[framps]

A static mount has to be OK. If the mount is not OK the first time the backup path is accessed raspiBackup will fail or just hang depending on the root cause of the failure. That's why I provide a helper script which first checks if the mount succeeds.

Later on I added the dynamic mount option which is the suggested way to mount nfs or cifs backup directories.

See here for dynamic mount. If the mount fails raspiBackup fails.

[cmonty14]

Many thanks for your valuable feedback.
However, I'm not sure if your implementation of mounting backup directory /backup is working with my setup, that is: automount with systemd

This means, /backup is mounted once it gets accessed.
I typically verify this with this command: findmnt --target /backup

[framps]

Please keep in mind a Fritzbox has a simple stripped down smb server which doesn't have all the capabilities of a normal smb server. I have raspiBackup users who successfully use their FB to keep the backups. But I also had users who had trouble because of the reduced functionality of the FB smb server.

Maybe you describe in detail what's your issue. Maybe I have an idea how to fix this other than to exclude the FB smb share from automount.

Since you use a FB you're probably German. If you feel much more comfortable to have this conversation in German just switch to German 😉

[cmonty14]

To move forward with this issue I have executed the following steps:

1. Stop systemd-mount service of backup-device: systemctl stop backup.automount backup.mount
2. Start raspiBackup service: systemctl start raspibackup.service

The backup failed as expected with the expected cause; here's the relevant backup log:

--- RBK0009I: loxberry: raspiBackup.sh V0.6.9.1 - 2024-06-17 (77f6bf8) Di 8. Okt 07:13:41 CEST 2024 gestartet.
--- RBK0151I: Backuppfad /backup mit Partitionstyp wird benutzt.
??? RBK0027E: Kein externes Gerät an /backup verbunden. Die root Partition würde für das Backup benutzt werden.
--- RBK0033I: Bitte warten bis aufgeräumt wurde.
--- RBK0043I: Unvollständiges Backup in /backup/loxberry/loxberry-tgz-backup-20241008-071339 wird gelöscht. Das kann etwas dauern. Bitte Geduld.
??? RBK0005E: Backup fehlerhaft beendet. Siehe vorhergehende Fehlermeldungen.
--- RBK0010I: loxberry: raspiBackup.sh V0.6.9.1 - 2024-06-17 (77f6bf8) Di 8. Okt 07:13:45 CEST 2024 beendet mit Returncode 102.

In my opinion raspiBackup works as expected.

There's just 1 thing I noticed.
raspiBackup creates directory /backup/loxberry (where loxberry is the hostname), but it does not cleanup of this directory after failure.

[framps]

Thank you for sharing your experience.

raspiBackup creates directory /backup/loxberry (where loxberry is the hostname), but it does not cleanup of this directory after failure.

That's a known issue and will be fixed in next release ;-)