Messages

1

MP Server / Re: Migration Document stored in CACHE to TSM

« on: February 07, 2021, 07:26:42 AM »

Hi Alessandro,

This is an old thread but it might be connected to my actual problem.
I checked the method you described above and I'm wondering if the same could be used to migrate all entries from a cache only storage node to Azure Blob storage?
We are on CMOD 10.1 (Windows 2016) and have tons of reports but we only have cache only storage set defined (no TSM at all) and would like to upgrade to 10.5 and use Azure Blob storage for the report to save cost. Export and import all reports is painful and would take years to complete...
Any suggestions are welcome...

Thanks in advance

2

MP Server / Re: Slow arsdoc get for PDF reports

« on: February 07, 2021, 05:40:15 AM »

Thank you Justin, I'm going to try to extract using the latest CMOD 10.5.0.1 as the client.
Could you please give some hints/directions about the better way? (the current storage set is cache only with cache only node)   

3

MP Server / Slow arsdoc get for PDF reports

« on: February 04, 2021, 09:47:38 AM »

Hi,

We are using Windows 2016 and CMOD 10.1 with DB2 and local cache only storage and I've experienced a huge slowness with the arsdoc get.
When I use arsdoc get to extract large PDF reports (which contains many PDF documents) the extraction time is really long (I'm using the -c -a -g -N parameters and -X with the loadID provided).
For example, a PDF report which contains ~4200 documents took almost 9 minutes to extract (this is the best case).
We would like to upgrade to CMOD 10.5 and setup Azure BLOB storage so AFAIK there is no other way to just export everything and reimport everything, so we have to use this method in the migration process.
But with this speed, it takes years to complete this (there are millions of reports). Does any of you know any other way to achieve the same result faster?

Some experience with the above:
During "arsdoc get" there is high CPU usage on CMOD server and the SYSTEM process consumes 36-40% of the CPU (I don't exactly know what it is doing, but only hit the CPU when I start the "arsdoc get").
Also, using process explorer I can see that it calls the arspdump.exe for each and every document (also don't know the reason, because there is no need to have the indexes for the PDF documents for exporting them)
And (as an extra) I loaded the exported PDF with the generic indexer and after that, I extracted it again with arsdoc get (the same way I described above), and it was blazing fast. 7 seconds instead of 9 minutes. So I only experience this behavior with the PDFs loaded using PDF indexer (and this is the case for all existing PDF in the system).

Any suggestions are welcome...

Thanks in advance