reverse logs filtering

ProfessorX

We have a lot of Websphere logs that our developers need from the production systems. OD reverse has been working great.

Well now we have run in to a snag in a sense that these logs are big and taking up a lot of space on CMS. I cut it down by half by using the filter ".*\.logs?$" so only *.log(s) are being downloaded...great...but I'm still getting a lot of old logs.
This takes up space a cuases the Deployment to be a little slower.
I.E
SystemErr_04.03.19_11.32.44.log
SystemErr_04.03.19_15.25.43.log
SystemErr_04.03.19_23.56.56.log
SystemErr_04.03.20_15.57.32.log
SystemErr_04.03.22_06.26.12.log

What I would like is to maybe to get anything that has been modified in the past 5 days.
Any Idea's or suggestion?

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

Adam Stoller

I don't remember, but in OD5.6 is it possible to run a dnrDeploymentJob script on the source-side (in this case the Receiver) that will generate a filelist that can be used by the deployment itself?

If so - that's one approach - have the script determine which logs fit your objectives and generate a filelist that would then be used by the deployment process.

Another approach, which might be cleaner all around - is to have a log rotation script running on the Websphere server that gzips log files that are older than N days and removes gzip'd log files that are older than M days (remember that the gzip file will have the timestamp of when it was compressed, not the original timestamp of the logfile).

If you do that - then the list of logfiles that meet your regex for the deployment is always a subset of the logfiles available on that server because the other ones are compressed and end with ".gz".

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com