Q

NAS and NFS

Mr. Farley: Why did a vendor suggest Network Attached Storage for a relational database like Oracle? These files are open all the time. NFS v3 transport is UDP/2049, a connectionless protocol. How can a DB commit be guaranteed? Is NFS WRITE+COMMIT enough? So, write validation is a file system application layer function? Seems like too much protocol overhead to perform like SCSI over Fibre.
Well, this gets right into the sticky wicket. There are potential problems with UDP and relational databases as you describe. The question is how can a stateless protocol like UDP work with statefull processes like relational databases have? It seems to me like it's a little bit more than just a "mileage may vary" answer. I have not heard of anybody's database blowing up from using NAS and NFS, but that doesn't mean it can't happen. It's also one of the main reasons Network Appliance, for instance, is developing DAFS, so they can get guaranteed, in-order delivery of relational database file-level I/O.
This was last published in April 2001

Dig Deeper on NAS management

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchSolidStateStorage

SearchConvergedInfrastructure

SearchCloudStorage

SearchDisasterRecovery

SearchDataBackup

Close