On 3/16/07, Danie <[EMAIL PROTECTED]> wrote:
I think I may have explained myself incorrectly , we actually want to move the data off from the production system , in other words remove the actual entries in the database as well as the articles on the local filesystem and insert them into the archive server database.
Making a copy of the database and the OTRS install to another machine is still valid. Then, once your archive copy is working properly, setup a GenericAgent task that deletes all tickets older than whatever date you specify from your active setup. I have one that I use if you need an example, it deletes messages in the Spam queue that are over 2 months old and have a status of Closed Unsuccessful. If you want to do this on a very regular basis it doesn't work so well, and you'll need a more integrated process to "move" tickets between installs, but if you just want to clean things out once a year or so it could work fine. Also, obviously you can't search between the installs, which could be an issue. Personally, I'd look at optimizing things so the whole database can run in one place. Just deleting spam for us drastically reduces the size of the database and filesystem article storage. Note that the delete task may have to run several times before all the old tickets/articles are purged. I think there's a timeout that limits it to only running for a certain length of time (but that is speculation). Thanks, Bryan _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support orr consulting for your OTRS system? => http://www.otrs.com/
