On 10/2/21 2:52 AM, Shaligram Bhagat, Yateen (Nokia - IN/Bangalore) wrote:
Hi All,
We are using Bacula 9.4.4 with PostGreSQL for disk based backeup.
Disk space is available to Bacula storage daemon as an NFS mount from
a remote ZFS based filer that has RAID configured disks.
Recently one of the disk in the RAID array failed, degrading the
remote ZFS pool.
With NFS, file system caching is on the server hosting the ZFS
filesystem. Additionally, there is data and metadata caching on the
client. Data updates are asynchronous, but metadata updates are
synchronous. Due to the synchronous metadata updates, both data and
metadata updates persist across NFS client failure. However they do not
persist across NFS server failure, and that is what happened here, I
think, although it is not clear why a single disk failure in a RAID
array would cause an NFS failure.
In short, iSCSI will be less troublesome for use with Bacula SD, since
the Bacula SD machine will be the only client using the share anyway.
Later we observed the Bacula storage daemon in stopped state.
Question is : can the disturbance on the NFS mounted disk ( from the
remote ZFS based filer) make bacula-sd to stop?
If you mean bacula-sd crashed, then no, it should not crash if one of
its storage devices fails.
Thanks
Yateen
___
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