> Modern storage systems claim that they have no single point of failure,
> BTW. Some of them even allows two or more servers to be attached.
I know, I have bought a couple of those systems in the past.
> But all this is pointless because Firebird server itself is a SPoF.
True, but that's a separate issue. This discussion was/started about running
FB using SMB v3 based storage/share, and the suitability of same.
If the underlying storage interface has issues which could lead to corruption
(which was certainly the case with SMB <v3) then talking about using it for FB
or any other IO critical application is a non-starter.
Your posts suggest that you have fundamental (almost philosophical) problems
with the idea of using SMB v3 storage for FB purposes.
My responses have tried to point out that SMB v3 is significantly different
from your experience/thinking and it is a real candidate for use with FB -- as
long as the necessary changes are made.
IMO, the ability to have FB server running in a VM and know that should there
be any host or storage hardware failure, that the FB will continue 'ticking
along' without any suggestion of a problem is a "very good thing". {all this
using off the shelf hardware components}
Sean
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
