Re: NFS vs I-NET

kgoozis@child.psy.miami.edu (Kleanthis Goozis) wrote: >The environment: One database server, 20 (diskfull) workstations. >The application: One (big) Informix application using one (big) Informix > database. Both the application and the database reside on the sever. > > >Which approach would you use (and why): > >1. Telnet to the server and run the application there. >2. Use I-NET to access the database and: > a. maintain a copy of the application on each of the workstations > b. use NFS mounting for the application >3. Use NFS mounting for both the database and the application. Hm. Not sure what you're trying to say with #3. If you want to share a data file with NFS and have several servers using it, DON'T!! Data will be inconsistent across the servers, with each thinking they have current data cached, when in reality the file was changed by another server. If the database is read-only, this may not be a problem, but be careful. If you're doing any updates from anywhere on the network without a distributed lock manager, all hell will most certainly break loose. If you feel you must try this, make good backups first and be prepared to restore them. Assuming this *is* what you meant by #3, #1 and #2 are your only options. If performance is acceptable with option 1, I'd do that. You'll probably find that option #2 is the best way to go however, and a) will be easier on your network and give better performance, while b) will be easier to administer and manage revisions on. -- Troy Casey -- tdc@ndcorp.com Programmer/Analyst Distributed Systems Engineering - National Data Corp.