User's Manual
Table Of Contents
- Preface
- Online Archiving with AMASS 1
- Accessing the Storage Network 2
- Technical Support 3
- Preface
- Online Archiving with AMASS
- Accessing the Storage Network
- Technical Support
- Glossary
- AMASS®
- API
- appended files
- archive
- backup
- bar code
- BFS
- bitfile
- bitfile ID
- cache
- cleaning group
- client
- DAS™
- DataClass group
- DataMgr™
- dead space
- DLT™
- DMFS
- drive pool
- drives
- Ethernet
- FCB
- FDDI
- file
- file import
- file replication
- FileServ™
- file system
- File System Database
- GUI
- HSM
- inode
- IP address
- IPI
- Journal
- jukebox
- label
- library
- mailbox
- media
- metadata
- migration
- multi-tier migration
- NFS
- NIS
- nonresident file
- optical
- Offline Media Manager
- RAID
- resident file
- RPC
- scattered writes
- SCSI Fast/Wide
- server
- SLD
- slot
- SMP
- space pool
- SSD
- standalone drives
- Storage Area Network
- storage policy
- striping
- stub file
- TCP/IP
- thrashing
- truncate
- UNIX™
- VBS
- volume
- volume group
- volume number
- VolServ™
- Windows NT™
- XDI
- Index

AMASS Overview
2-4 Accessing the Storage Network 6-00026-01 Rev A
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
application-transparent; and, under normal traffic patterns, the
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 fine-tune the NFS
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
Protocol (FTP)
FTP allows users to transfer files easily from one machine to
another over the network. To learn what functions can be
invoked from your server processor FTP utility, refer to your
server’s reference manual.