Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

comp.arch.storage FAQ 2/2
Section - [3.7] AMASS

( Part1 - Part2 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Counties ]


Top Document: comp.arch.storage FAQ 2/2
Previous Document: [3.6] R-Squared Infinity IFS 2 {Brief}
Next Document: [3.8] Tracer XFS {None}
See reader questions & answers on this topic! - Help others by sharing your knowledge
From: Hierarchical Storage Management

From Advanced Archival Products. Supports a huge range of devices,
autochangers, and operating systems. Block-based movement of data
between the hard disk cache and tape or optical tertiary storage.
Systems run from a few gigabytes up to at least 12 TB, with prices
dependent on capacity. New versions allow multiple cache disks. Slips
right in to the VFS layer and looks like a normal Unix file system,
with the plusses and minuses that entails. No file versioning or
multiple copies yet. File creation is an Achilles' heel on
performance. Since it's block based, files can be larger than a piece
of media. Separate product DataMgr will migrate files from client
machines to the AMASS server automatically (with FS changes, of
course).

AMASS is now owned by EMASS, and you can find info at
http://www.emass.com/Products/Software_Products/AMASS/AMASS_Top.html.
(rdv, 1996/3/27)

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Top Document: comp.arch.storage FAQ 2/2
Previous Document: [3.6] R-Squared Infinity IFS 2 {Brief}
Next Document: [3.8] Tracer XFS {None}

Part1 - Part2 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
rdv@alumni.caltech.edu (Rodney D. Van Meter)





Last Update March 27 2014 @ 02:11 PM