We are running RT 2.0.15 for our Technical Support
center and it handles anywhere from a few hundred to
several thousand incoming emails a day, each
generating an RT ticket.
The RT database is currently 2.4G and has 105,000
tickets. We do a weekly mysqldump to back up the
database, but because of the size of the DB, if causes
the machine to become unresponsive for about 10
minutes.
We would like to purge all tickets in a resolved state
that have not been updated for 30+ days, as that would
remove about 85,000 tickets and make the RT database
and the mysqldumps much more manageable.
We know that tickets are not normally erased from the
database, but what does everyone else do when they get
hit with several thousand SPAM emails or when the RT
database getto an unruly size?
Does anyone have any other options?
DA> database, but because of the size of the DB, if causes
DA> the machine to become unresponsive for about 10
DA> minutes.
use postgres instead
DA> We would like to purge all tickets in a resolved state
DA> that have not been updated for 30+ days, as that would
DA> remove about 85,000 tickets and make the RT database
Well, if you can do an update in sql directly to set the status of the
tickets to ‘dead’ then you can use the remove dead tickets scripts
(posted here several times) to actually remove them from the
database. In postgres, I just set up foreign keys to cascade the
delete automatically, so I don’t need such a script.
use postgres instead