Forum Discussion

eng_sysadmin's avatar
eng_sysadmin
Occasional Contributor
8 years ago
Solved

[Collaborator][Cache] How do I remove old files from the server cache for Collaborator 9.5.9501?

Our server cache is getting large and I'd like to archive the old reviews and remove their files from the server.  Archiving the old reviews is simple (Select the review and press "SAVE TO ZIP").  My...
  • eng_sysadmin's avatar
    eng_sysadmin
    8 years ago

    I wrote the attached Perl script that archives the cache files for the input review number.  It's smart enough to not remove files used by later reviews and will create a TGZ with all the files associated with the review.  If you want to execute against a range of review, replace the (@ARGV) of the foreach loop with (1..n) to archive reviews 1 through n.

eng_sysadmin's avatar
eng_sysadmin
Occasional Contributor
8 years ago

The SQL statement was just to identify the files associated with a given review.  I have no intention of making changes to the database.  I just want someone to confirm if my statement does indeed identify the correct files.  Once confirmed, I plan to create a script that queries the database and then moves the files from the cache directory to an archive directory within the file system.

 

I already saw the article you link to.  It describes a brute force archive method.  There is no way to know which review will be archived and which will not be archive.  Worse yet, it is very likely the method will end up archiving some, but not all the files for a review if its time frame overlaps the randomly chosen timestamp.  This method also requires a lot of manual traversing of the cache directory structure in order to identify the files that can be archived.  Finally, there is the statement "If you are doing document reviews, we don't recommend you archive any of the files in the content cache."

  • eng_sysadmin's avatar
    eng_sysadmin
    Occasional Contributor
    8 years ago

    I wrote the attached Perl script that archives the cache files for the input review number.  It's smart enough to not remove files used by later reviews and will create a TGZ with all the files associated with the review.  If you want to execute against a range of review, replace the (@ARGV) of the foreach loop with (1..n) to archive reviews 1 through n.