Engine ‘Clean Up’

[Bevan Richards]

I am in the process of getting ready to upgrade to 5.7 and in going through the current engine I have found the ‘revisions’ folder on each site. I would like to know how long others leave these files (monitor and config views) out there?

I have never done anything with these and some of the files go back several years.

Topic

[Steve Carter]

We had the same dilema a while back.  I decided to purge them based on maintaining a minimum of 10 revisions regardless of age.  If there are more than 10 revisions, a minimum of 7 days is kept regardless of count.

We actually move the ‘purged’ revisions to a holding area that we will purge again at a later time.  It’s outside of the application’s file system so we don’t have to be concerned with space.

Hope this helps.

Steve

[Bevan Richards]

Thanks, that gives me something to work with.

[Bob Richardson]

Greetings,

We keep the revisions directories for a month then purge them permanently.   There is no auto purge (archiving) function in Cloverleaf.

We use the AIX Unix cron facility to manage all of our multiple sites revisions directories (a find exec rm combo).

They do come in handy at times when “accidental” deletions or modifications have been made especially in our production engine.

BobR

[Kevin Crist]

We clean out our revisions montlhy (using CL 5.4.1) but leave at least the lastest backup regardless of how old just in case.

[Robert Kersemakers]

We clean up our revisions directory daily through cron, where we delete everything older than 100 days.

I agree with BobR: revisions are very useful when you accidentally or too quickly changed something in a translation or network configuration. For the major changes we keep copies of the network configuration and all translations. These are cleaned manually once every year or so.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Author]

Replies