On 9/15/26 11:26 AM, Stefan G. Weichinger via Bacula-users wrote:

I am perfectly aware that mounting NFS via Wireguard VPN is out of scope here!

But I'd like to ask how to configure the Storage device in Bacula(ris) to at least get rid of errors there, maybe.

As far as I understand Bacula-SD is able to trigger the mounting of a filesystem before accessing the storage device.

Yes, if it is told to do so.


So I assume this relates to the "user" option of nfs filesystems in fstab ?

Yes, but do you really want to do that? It allows ANY user to mount the NFS share. It might be safer to use autofs, which can be configured to set a specific uid:gid when automounted. In bacula-sd.conf, you would just use /net/10.1.0.24/Volume1/BaculaBackup as the Archive Device. Then the automount daemon would handle the mount and umount automatically.



My issue: I see loads of this in my logs:

nfs: server 10.1.0.24 not responding, still trying

Check the firewall on both sides. Maybe NFSv4 file locking daemon is being blocked, etc.


and the mount hangs.

I fiddle with options, soft vs hard mount, timeouts, packet sizes etc

(didn't yet touch the wireguard site to site vpn because it works for many other uses very well)

Right now I try:

## fstab

10.1.0.24:/volume1/BaculaBackup /mnt/nas_office nfs defaults,user,noatime,rw,_netdev,timeo=100,user,rsize=1024,wsize=1024,tcp 0 0

It mounts, I have permissions.

In bacula-sd.conf:

Device {
  Name = "FileStorage_NAS_Office"
  Description = "storage auf NAS in Office"
  MediaType = "File1"
  ArchiveDevice = "/mnt/nas_office"
  RemovableMedia = no
  RandomAccess = yes
  AutomaticMount = yes
  LabelMedia = yes
  RequiresMount = no # maybe "yes" to actually mount it (again)
  ReadOnly = no
  MaximumConcurrentJobs = 5
  SpoolDirectory = "/srv/bacula-spool"
  MaximumSpoolSize = 16000000000
  MaximumJobSpoolSize = 10000000000
}


Bacula is able to create volumes there, starts writing but hangs somehow etc etc

Does anyone of you bacula-users do something similar, with success? ;-)

Any obvious mistakes in my config above?

The kernel also tells me:

INFO: task bacula-sd:2295 blocked for more than 120 seconds.

The nfs-mount seems to hang, this blocks the bacula-sd .. etc

Maybe nfs isn't the right protocol here.

Thanks for any pointers!




_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users



_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to