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
Hello Richard: avoid NFS for protocol performance issues. Go for iscsi.
Regards,
===
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified
Administrator II
Do you need Bacula training? http://bacula.us/video
--On Friday, December 04, 2015 08:19:00 AM -0600 Richard Robbins
wrote:
> 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
That's right!
Beside, I already get error and many troubles when decide use NFS to host
huge VM files...
I think this issues also apply it for backup.
Today, I prefer GlusterFS rater NFS
GlusterFS can work like NFS as well and are more reliable than NFS, even
version 4
I highly recommend av
Thank you Devin.
What you say makes great sense.
Oddly, as soon as I switched to an iSCSI mount instead of an NFS mount
things worked.
Perhaps I configured the NFS mount incorrectly, but it worked just fine
outside of Bacula.
On Fri, Dec 4, 2015 at 6:42 PM, Devin Reade wrote:
> --On Friday,
Hello all,
2015-12-04 16:03 GMT+01:00 Heitor Faria :
> Hello Richard: avoid NFS for protocol performance issues. Go for iscsi.
>
NFS is not as bad as it sounds. I have no problem saturating 1Gbit/s
ethernet connection with NFS as a storage for Bacula SD. Additionally when
using Bacula Enterprise
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
But I am able to access the share outside of Bacula with ease, so the NFS
share is mounted.
On Sat, Dec 12, 2015 at 6:25 AM, Kern Sibbald 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
>
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.
Might be reaching a bit, but do you have the NFS share configured such that
the root user on a remote system can access it? Normally that capability is
disabled by default (see no_root_squash option.)
Matt
On Sat, Dec 12, 2015 at 7:38 AM, Richard Robbins
wrote:
> But I am able to access the sha
The 'ERR=Connection refused' message means that the storage daemon
itself isn't accepting connections. This could be due to firewall rules
or due to mismatched passwords between the storage daemon and the other
components. I don't believe it is being caused by or is related to your
NFS mount i
On Wed, Dec 16, 2015 at 9:58 AM, Bryn Hughes wrote:
> The 'ERR=Connection refused' message means that the storage daemon itself
> isn't accepting connections. This could be due to firewall rules or due to
> mismatched passwords between the storage daemon and the other components.
This can also
On 12/16/2015 07:54 PM, Greg Woods
wrote:
On Wed, Dec 16, 2015 at 9:58 AM, Bryn
Hughes
wrote:
The
'ERR=Connection refused' message means that the storage
daemon it
13 matches
Mail list logo