I am new to Bacula and would like to run the Bacula
director on a CentOS 7 virtual machine with the FQDN of
bacula.itinker.net
and use a NAS device as my storage repository. For now, my NAS
is a somewhat dated Netgear ReadyNAS device that I'm going to
replace with a new Synology box in the not-too-distant future.
I've got Version 7.0.5 of the Bacula components runnning on
the Centos machine and can backup and restore to a local
directory without difficulty. I'm struggling to get the NAS
into the mix.
In my all local configuration I backup to /bacula/backup
and restore to /bacula/restore.
I had hoped that I could tweak the system so that I mount
an NFS v3 share at /bacula/backup.
The OS mounts the NFS share at that point and I'm able to
read and write files without difficulty but when I fire up
Bacula the program hangs with accompanying warning messages
"Warning: bsock.c:112 Could not connect to Storage daemon on
bacula.itinker.net:9103.
ERR=Connection refused.
Since I'm able to read and write the NFS share outside of
Bacula I'm stumped as to what's getting the way when Bacula
runs.
In a perfect world I suppose I'd run the director and SD on
the NAS itself, but I'm not up to attempting to build the
current Bacula system on my older NAS. Maybe I should try to
compile the storage daemon but not the director on the NAS and
then point the director on my VM to a daemon running on the
NAS. But that too is more work than just mounting the NFS
share as I am doing at the moment.
Another approach would be to create an iSCSI target and
pass that to my VM as a virtual disc which would just be
embedded in the virtual hardware prior to system boot time,
but I'd like to avoid that if possible.
Your thoughts and guidance will be greatly appreciated.
-- Rich
