AMASS Overview
| AMASS supports NFS by making its file system appear as a |
| mounted local file system to the NFS server. This allows the |
| AMASS file system to be exported in the same manner as the |
| standard local file system is exported. Thus, the AMASS file |
| system or its subdirectories can be mounted, across the network |
| to the client file system, making the AMASS resident files, |
| directories, and storage capacity available as though the |
| AMASS software and its storage devices were running on the |
| client. |
| The NFS interface to AMASS is both user- and |
| |
| NFS and AMASS systems work well together. But, because of |
| the inherent nature of a removable media device and the |
| stateless design of the NFS facility, you must |
| configuration parameters to obtain the best possible |
| performance for a given environment. |
| Delays, inherent in accessing files from a removable media |
| library, can cause the NFS system to retry operations that are |
| waiting for resources. While this will not cause the operations |
| to fail, it may temporarily prevent other NFS operations from |
| executing by using up the available NFS tasks or by causing |
| excessive network traffic during the retry cycles. |
| For specific information on providing NFS clients access to the |
| file system, refer to Installing AMASS. |
File Transfer | FTP allows users to transfer files easily from one machine to |
Protocol (FTP) | another over the network. To learn what functions can be |
| invoked from your server processor FTP utility, refer to your |
| server’s reference manual. |
Accessing the Storage Network |