Best Practices for Archiving and Attachments.

Danielc1234

Hi, I am trying to find a document that shows best practices for archiving tickets and attachments and what would be the optimal setup for this. Our osticket system (upgraded to 1.14) handles all our voicemails that automatically create a ticket with an attachment. Our database is over 6GB and I need a way to maintain size and keep a history of around 6 months if possible. I have tickets dating back to 2015 which I have been trying to delete by hand. It will take forever to try and get those older tickets deleted.

So I guess my question is, is there a standard method of how one would set this up? I have found little pieces of the puzzle here and there on the forum, but I want to make sure I am doing this correctly.

Any suggestions?
Thanks Daniel

ntozier

I do not believe that there is an "official" best practice for this.
Let me reach out to the devs and ask if they have one.

Personally we have tickets dating back to 2009. We obv dont have as many attachments as you do because your database is 10x ours.

Danielc1234

ntozier
I see there is a plugin for 'Attachments on the filesystem' which I had tried to install. For some reason, when I activate this plugin, I am no longer able to delete certain tickets, etc.
I thought maybe the plugin is no longer compatible with version 1.14?

It would be nice to be able to store the attachments in a directory like the plugin is saying it does.

If we did not have all the attachments stored in the database, I think we'd be fine with how many tickets we have.

acbs-it

I would like to send a direct message to ntozier about a discussion that was locked. I don't think this is accurate information but why is it locked? https://forum.osticket.com/d/96963-error-trying-to-use-ldap-authentication-using-tls-port-636

ntozier

@Danielc1234 The plugin Attachments on the filesystem is compatible with 1.14.x. You also need to set the default storage in osTicket at Admin panel -> Settings -> System -> Store Attachments: to use it.

@acbs-it the Poster solved their issue so the thread was closed. Please do not hijack other peoples threads. If you have an issue please start your own thread. after reading the posting guidelines located in this thread: Please read before requesting assistance

acbs-it

ntozier
Ugh, I have the same issue and his solution isn't valid unless he has a magical version of OSTicket. Why is the thread locked?

ntozier

@acbs-it As I have already said: If you have an issue please start your own thread after reading the posting guidelines located in this thread: Please read before requesting assistance

ntozier

@Danielc1234 I spoke to the devs about this and their response was:

until we implement some kind of archiving system, the only way is to create an advanced search and select all + delete until they’re are all gone or write an sql query to delete all past a certain date or matching certain criteria, etc.

Danielc1234

@ntozier
That sounds above my knowledge without screwing something up I'm sure.
Would you happen to know if there are any working scripts out there that would work for my situation?

ntozier

There is a 3rd party Archiver plugin.
https://github.com/clonemeagain/osticket-plugin-archiver

I have honestly never used it.

acbs-it

OK, so it's cool with you to have bad information floating around in the support forums. Got it.

ntozier

@acbs-it As I have already said: Please do not hijack other peoples threads. If you have an issue please start your own thread after reading the posting guidelines located in this thread: Please read before requesting assistance. Thank you.

acbs-it

As I have already said: you are closing issue threads that have incorrect solutions in them and leaving them on the site makes you look bad and frustrates users more than this hijacked thread.

ntozier

@Danielc1234 I'm sorry that someone has such a flagrant disregard for your thread topic. If you have any further questions please let us know.

@acbs-it That is your opinion. You are welcome to your opinion. That being said the poster said that their solution worked for them. Since they are in a better position to judge if something is working for them, and you are not privy to their setup or environment I have to trust that they know if it worked for them.

Please do not hijack other peoples threads. If you have an issue please start your own thread. after reading the posting guidelines located in this thread: Please read before requesting assistance. Thank you.

You will not receive any further responses from me on this thread and further posting by you on this thread will result in the post(s) being deleted.