My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_05-25_NetworkFileSystemUseInCRDSS
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_05-25_NetworkFileSystemUseInCRDSS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:53 AM
Creation date
5/30/2008 3:32:41 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.05-25 - Study of System Integration Issies System - Network File System Use in CRDSS
Description
This memorandum discusses the use of NFS software to allow CRDSS machines to transparently share hard disks.
Decision Support - Doc Type
Task Memorandum
Date
5/10/1994
DSS Category
DMI Utilities
DSS
Colorado River
Basin
Colorado Mainstem
Contract/PO #
C153658, C153727, C153752
Grant Type
Non-Reimbursable
Bill Number
SB92-87, HB93-1273, SB94-029, HB95-1155, SB96-153, HB97-008
Prepared By
Riverside Technology inc.
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
3
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Remote machines (e.g., the Briefing Room machine, an d the CRDSS machines at CSU) can also <br />access the disks on the CRDSS machines at RTi using NFS. This will allow those remote machines <br />to transparently access the main CRDSS files. However, because such access uses a relatively slow <br />Internet link, large file transfers may be slow. <br />NFS has limitations, one of which is that a slow network will lead to slower NFS file access speed. <br />This can be alleviated to a certain extent by placing copies of commonly used programs or data files <br />mosaic <br />on each machine. For example, could be placed in each machines' /usr/local/bin directory. If <br />this method is used, it is important that only one master copy of the file exists. Another limitation of <br />NFS is that if one machine goes down, then other machines may lose access to important files. <br />Unfortunately, any machine crash has harmful effects and will adversely affect the computing <br />environment in a network of machines, and a broken NFS chain is no worse. If an important <br />network machine does crash, important files can be loaded on another machine and the NFS <br />directory structure can be modified to use the new machine as a source for files. <br />3.0 CONCLUSIONS AND RECOMMENDATIONS <br />NFS will be used at RTi to share disk space between different CRDSS workstations. The following <br />recommendations are made: <br />All major software and data directories will be made available to each CRDSS machine at <br />? <br />RTi using NFS. The machine that has the tape drives will additionally have access to some <br />system directories on remote machines so that important system files can be backed up. <br />NFS will be implemented using a standard structure on each machine, in which an <br />? <br />/nfs <br />directory contains the mount points for machine-dependent directories. Symbolic links will <br />then be used to map common directories to the machine-dependent directories. <br />NFS limitations, such as slow access and network access problems due to a machine crash <br />? <br />will be addressed using standard UNIX system administration tactics. Such problems can <br />be present in any networked UNIX environment, and system configuration alternatives <br />exist for preventing and minimizing disruptions due to NFS problems. <br />3 <br />A275 05.10.94 1.05-25 Malers <br />
The URL can be used to link to this page
Your browser does not support the video tag.