On Feb 7, 2008, at 4:51 PM, Buice, David R wrote:
Hello,
We are running OTRS on a Windows box with a 9 Gb of space. We recently ran into an issue with disk space being near capacity. We saw that one of the data files, article_attachment.MYD, was over 4 Gb in size.
article_attachment.myd is a mysql table. you could run "OPTIMIZE" but its not going to clear up space. the only way to clean that up is to literally DELETE tickets, and you better do it with the UI (otrs generic agent can do this but CAVEAT EMPTOR - you lose a lot of statistical data when you do this and that may upset the beancounters). since you are running windows maybe you should just switch OTRS to use FS storage (stores tickets/attachments on filesystem rather than LOB's in mysql) and compress the filesystem where they are stored.
This file is found in <OTRS disk drive>:\mysql\data\otrs. We moved this file off the machine in desperation only to discover that the attachments were no longer accompanying the messages being sent from OTRS....duh!
yeah and you also broke mysql.. nice!
So my question is: Since apparently we'll have to bring back article_attachment.MYD, is there any way to edit this file and bring it down to a reasonable size. Or is there a windows "cron" equivalent that could reduce the size of the file on a nightly basis?
just look at the super power of the generic agent.
Any help understanding this (and other huge MYD files) and how to manage them would be extremely helpful.
check out the Manual for OTRS and you can find information on these topics. HTH, Andy Lubel
Thank you,
David Buice ITIL Foundations Certified EDS - PSIC 7000 Chicago Road Warren, MI 48092
( Phone:+1-586-575-4525 + mailto:david.buice@eds.com cell: 248-249-9122