TRIM Integration with Data Protector

4
• One or more Document Stores
Document Stores contain the actual files linked to individual records. The physical locations of the
stores are defined in the corresponding Metadata Database.
For each Dataset, you can also instruct TRIM to maintain the following:
• A Document Content Index.
The index facilitates fast indexed searches. It can always be rebuilt from the Document Stores, but
this can take a considerable amount of time. The location of the index is held in the global
configuration file.
• Audit Logs.
The logs store information about every transaction made in TRIM. By default they are created on an
Event Server. All this information is specified in one global configuration file.
TRIM’s Architecture
Figure 2 illustrates how these data parts fit into TRIM’s architecture. A TRIM system is divided into
three Tiers: the Data Tier, the Server Tier and the Presentation Tier. The Datasets and associated
elements mainly belong to the Data Tier of TRIM’s architecture, while the configuration and Audit Logs
are stored within the Server Tier.
Figure 2: TRIMS's Architecture
Every block in this figure represents one or more servers (some of which are optional).
The global configuration file resides on all the servers in the server tier, so it is sufficient to back it up
only from one of the servers. While not mandatory, maintaining a backup of the configuration file
significantly eases the restoration procedure.
Implications for Backup
The Data Tier is the most important part from a backup perspective, and all its components should be
backed up regularly. In addition, it is highly recommended to back up the global configuration file
and the Audit Logs.
Presentation Tier
TRIM ‘Thick’ Client Interfaces TRIM ‘Thin’ Client Interfaces
Data Tier
Document Store
Meta Data
Database
Document Content
Index
Server Tier
Global Configuration
Web Service
Event Server
(with optional Audit Logs)
ICE Server Render Engine
Workgroup Server Workgroup Server Workgroup Server