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
1-10 Online Archiving with AMASS 6-00026-01 Rev A
• Prioritizing reads-from-volumes over writes-to-volumes
Configurable Cache The cache size can be configured to take advantage of both the
application being used and the system environment where
AMASS is installed.
Applications running database tables in the library, may need a
larger cache configuration to optimize the number of cache hits
and allow updates to table headers to be predominantly cache
IO.
The cache parameters are configured during installation. For
information on sizing the cache, refer to Installing AMASS.
Virtually
Unlimited File
System Size
Although every attempt is made to keep files under a specific
directory on one volume, files can span media. Consequently, a
directory can reside on more than one volume.
Regardless of the physical size, all the volumes appear as a
single logical device, of admittedly large capacity. AMASS
supports a maximum of 65,000 volumes.
UNIX Server
WRITES are written to cache.
READS are cached the same way.
UNIX Server where
AMASS is installed.
Cache is on the hard disk.
From cache, WRITES
are written to volumes
in the storage device.