TRIM Integration with Data Protector

29
• the file extension (here, “.doc”), which indicates the type of document and is the same as the
original document that is registered.
• the part of the file name between the leading c and the file extension is a unique base 36 number,
used by the database in the reSID column of the TSRECELEC table to associate the document with its
record.
Figure 32
shows how the base 36 number and the decimal number relate to each other.
Figure 32: Conversion between base 36 number and decimal number
There are a few tools on the web to do decimal to any radix base number conversions, for example,
at the time of writing, at
http://www.easysurf.cc/cnver17.htm#b10toba
.
You need to remove all documents after this in the sequence. However if there are audit logs
available, you may be able to re-catalogue them back into TRIM using the standard interfaces.
Scenario 3: All documents and metadata recovered but content index out of date.
Document Content Indexes within TRIM can be separated physically into chains which logically
operate as one index. In the event of a recovery only the updatable chains need to be reindexed.
Read-only chains will be able to be recovered as they are.
The fastest way to reindex the updatable chains is as a batch process using the TRIM Enterprise Studio
tool as shown in Figure 33. To open this dialog, right-click on the Dataset in TRIM Enterprise Studio
and select Content Index  Reindex. This tool allows you to reindex a selection of documents, such as
those updated in the last 7 days. The Event Processor must not be running against these indexes while
the manual reindex is in progress.