News:

Buffalo provides Data Recovery services. Read about it here.

Main Menu

LinkStation Pro Quad suitablity for use as a quorum disk device in a Red Hat High Availblity cluster

Started by ukoda, May 11, 2013, 09:48:45 PM

Previous topic - Next topic

ukoda

I run servers for my self as a embedded systems developer and for my family.  I'm trying to increase the long term reliability by moving from a master/slave pair of Cent OS servers to a High Availability cluster of 4 servers.  For storage I was considering a pair of Link Station Pro Quad NAS.  They appear to be built on a good platform and have a reasonable price.  There is only mention of support for Windows and Apple clients.  Given the underlying OS on them is Linux I was hoping they would also support Linux.  NFS is often offered to do that but it looks like the "quorum disk device" I need is more specific than that.  To quote from the Red Hat's documentation:

 

A quorum disk device should be a shared block device with concurrent read/write access by all nodes in a cluster. The minimum size of the block device is 10 Megabytes. Examples of shared block devices that can be used by qdiskd are a multi-port SCSI RAID array, a Fibre Channel RAID SAN, or a RAID-configured iSCSI target.

 

My experience with block devices is they are locally mounted drives where as NAS unit present a higher level access.  Has anyone experience with working such a configuration?  Can this be done with a Link Station Pro Quad NAS or will have to build my own NAS from scratch?


Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 109 (show)
Files included: 35 - 1354KB. (show)
Memory used: 924KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]