TRIM Integration with Data Protector

2. In the Run Integrity Check dialog (see Figure 31) click OK to start the check.

Figure 31: Run Integrity Check dialog

Note that you can source documents from any document caches in the system (if available) and

simply copy them to the document store.

Scenario 2: All documents in the store but database recovered to a previous point in time

There is no reverse document store integrity check in TRIM but the documents with no metadata need

to be removed before normal operation can be resumed. The file names are generated by TRIM in

sequential order. To find out the last filename used by the database there are two different ways,

depending on the Dataset schema version of TRIM used (to get your version open TRIM Context and

select Help  Setup Information... and click on Network Connections):

•

Before schema 118

: The table TSNumbers was the key to generating estoreIDs, using the SQL

statement

SELECT nbrLastNumber FROM TSNUMBERS WHERE nbrType = ")

+ (long)TRIM::nt_elecStoreURIs

+ " AND nbrRef = " + storeUri;

•

After schema 118:

It is purely a query of the TSELECSTOR.esitems column.

This will provide you with a number, such as 1758. This means the last filename c00001cu.doc

stored would be worked out as follows:

• the initial c which indicates this is a TRIM document