The OS receives a number of updates over the life of a Retain server, so that should be provisioned for.
The Retain program is updated often as well. This is often placed on the same volume as the OS.
The Archive contains the item bodies and attachments. This is generally the largest percentage of the storage requirements on a Retain server. The bodies and attachments are stored as BLOB (Binary Large OBject) files in a folder structure that starts with /00/00/00 and grows to /FF/FF/FF for 16.7 million directories. BLOB files are stored only once, Retain implements a single-instance storage system, only a single copy of identical items is stored. BLOB files never change, they are only created or removed.
The files are accessed when a message is opened in the Retain Search Message interface or downloaded by Retain Publisher.
The indexes allow for fast search of the data in Retain. When searching for items in Retain the indexes are used to return the results.
For best search performance, the indexes should be placed on a fast disk and optimized regularly.
The Index requires periodic optimization. This is set under Server Configuration | Maintenance. The Indexer requires as much free disk space as currently used index space for optimization. It requires three times as much if optimizing during an archive job.
During index migration from Retain 3.x to Retain 4.x, storage requirements for the indexes are the most complex and are described below.
The database contains the header information for each item. For example: Sender, recipient, date received, and so on as well as pointers to the message body and attached files stored in the archive. Each item may be quite small but may be replicated many times in the database if there are many recipients.
When browsing messages, the items in the database is being viewed. On larger systems, the database is often placed on a dedicated database server.
The logs track the actions that Retain takes. They can become quite large but are compressed at the end of each day and removed after 10 days, by default. This can be changed under Server Configuration | Logging. Logs can be moved to another volume as described below.