Re: HP TRIM 6.2.4 Electronic Document Store size (500 Views)
Reply
Advisor
RecordsSystems
Posts: 22
Registered: ‎06-01-2010
Message 1 of 6 (500 Views)

HP TRIM 6.2.4 Electronic Document Store size

Can the reading of the store within the TRIM client be trusted?

 

Within the client interface the store reads as 120gb with 30 used and 90gb remaining.

However at the server the reading is 120gb with 58gb used and only 62gb remaining.

 

I have conducted a store integrity check with no change to the reading within TRIM.

 

Which reading is the most accurate and why is there a difference?

Please use plain text.
Honored Contributor
Grundy
Posts: 2,845
Registered: ‎02-16-2009
Message 2 of 6 (500 Views)

Re: HP TRIM 6.2.4 Electronic Document Store size

It's possible that there is old data in the store from an unused document store, or some other old cause/problem.

The usage count reported in TRIM is based on TRIM checking all the files sizes on the documents it KNOWS are in the store and using the sum of these values as they are stored in the database.

 

If the store directory structure contains extra folder/documents from some other cause or issue, Windows will obviously count these extra files too.

 

You can log a support case with HP and a support staff member could check it out for you.

 

 - JG



::::::::::::::::::::::
NOT A HP EMPLOYEE
::::::::::::::::::::::

Kapish.com.au
Please use plain text.
Advisor
RecordsSystems
Posts: 22
Registered: ‎06-01-2010
Message 3 of 6 (500 Views)

Re: HP TRIM 6.2.4 Electronic Document Store size

Thank you. Will do.

Please use plain text.
Honored Contributor
Sander Hoogwerf
Posts: 377
Registered: ‎11-05-2008
Message 4 of 6 (500 Views)

Re: HP TRIM 6.2.4 Electronic Document Store size

Weekly we run a bi-directional integrity check (we developed ourselves). We often find documents that are in the store, but not referenced in TRIM. Those documents are often larger documents of a few hundred MB or larger.

 

That's caused by

  • users uploading those documents and this taking too long to their taste and thinking that the TRIM client hangs again, they use taskmanager to kill TRIM.
  • users starting a second TRIM session and try again. This way, the document store ends up with multiple copies of the document with only one of them referenced by TRIM.

 

On the workgroupserverever the (partially) transferred document is put in the docstore anyway, but since the oracle metadata didn't commit, TRIM has no knowledge of this.

 

We rescued multiple GB's this way and presented the documents to the users to decide wether to register it in TRIM again if it's not already.

 

We reported this to support in July 2009 (CRID 35221), but it's not yet solved.

(Any opinions expressed in this forum are my own personal opinion and should not be construed as an official statement by Hewlett Packard.)

Analytics & Data Management
Application & Business Services
HP Enterprise Services
Please use plain text.
Advisor
RecordsSystems
Posts: 22
Registered: ‎06-01-2010
Message 5 of 6 (500 Views)

Re: HP TRIM 6.2.4 Electronic Document Store size

What happens when a new store is created? We are using oracle. It has been suggested that oracle may place operating files within the store, could this be correct? One new store that is recording only 102mb used within TRIM is recording 3gb used space within the store at the server.  Another with only 615mb known to TRIM is recording 4gb used at the server? IS this all just user misuse or are there expected but hidden files which are needed by the store.

 

One of the oldest of the store is recording 46gb available at the TRIM client and only 6 available at the server. That I can see as having user interaction. How much do you charge for your bi-directional integrity check cos it sounds like a really great tool.

Please use plain text.
Honored Contributor
Sander Hoogwerf
Posts: 377
Registered: ‎11-05-2008
Message 6 of 6 (500 Views)

Re: HP TRIM 6.2.4 Electronic Document Store size

Some things to know and investigate.

  • Older versions of TRIM (5.x, so very old) used to only add file sizes to the store and when removing documents forget to reduce the size.
  • Are the number of files mentioned in TRIM the same as reported by Windows?
  • Have you done a manual check to see if file sizes reported for both TRIM and windows do match?
  • Do you have a acceptance/test/education environment that is pointing to your production store? If this is the case you should separate it immediately by separating networks and/or permissions.
  • Oracle doen's know anything about TRIM, so won't place files in TRIM folders unless you configure Oracle to put your datafiles or archive logs there. Wouldn't recommend configuring it this way.
  • All files in the store should be registered in the TRIM database. Anything else that resides in the store should be removed after thourogh analysis regarding the origin of the files.
  • Available store size in TRIM can only be trusted if the share is only used for 1 docstore. If you have configured multiple docstores (or even storage for other non-TRIM applications) to 1 share, they may count all when asking Windows giving you false impressions.

I would encourage you to contact HP support and work out what's going on and resolve any issues.

(Any opinions expressed in this forum are my own personal opinion and should not be construed as an official statement by Hewlett Packard.)

Analytics & Data Management
Application & Business Services
HP Enterprise Services
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation