On 12/12/2015 7:38 AM, Richard Robbins wrote:
But I am able to access the share outside of Bacula with ease, so the NFS share is mounted.
From the VM, see if you can 'telnet bacula.itinker.net 9103'. If not, then check firewall and that bacula-dir.conf has the correct password for the SD.
Also from the VM, make sure the NFS share is accessible and writable by the user bacula:tape (or whatever user:group bacula-sd is running as). If not, check permissions, keeping in mind that Selinux is enabled by default in Centos 7.
On Sat, Dec 12, 2015 at 6:25 AM, Kern Sibbald <k...@sibbald.com <mailto:k...@sibbald.com>> wrote:Run the SD with debug level set to about 200. I suspect that the NFS share is not mounted, so when the SD attempts to open it, it is blocked by the OS, which is what happens when you try to access an NSF volume that is not mounted. Best regards, Kern On 04.12.2015 15:19, Richard Robbins wrote: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 <http://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 <http://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 ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net <mailto:Bacula-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/bacula-users------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
------------------------------------------------------------------------------
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
