Hello group members!
I turn to you with that question that we want to change the save location of the tickets' attachment. Currently, to my knowledge, attachments are saved in the OTRS database.
Because I'm not sure this so please help me where I can look that this is indeed the case.
We would like to replace this with that it writes the file or attachment to a file on the server and only the path is stored in the database.
Can this be done from System Configuration or do I need to rewrite a parameter at code level or is there some add-on that might help?
Thank you also in advance for your answers!
Hi.
[Solved]How do I save my tickets' attachment into a file?
Moderator: crythias
[Solved]How do I save my tickets' attachment into a file?
Last edited by kkgigiioo on 07 Oct 2019, 12:29, edited 1 time in total.
Re: How do I save my tickets' attachment into a file?
According to the manual
There are two different backend modules for the article storage of phone, email and internal
articles (configured via Ticket::Article::Backend::MIMEBase::ArticleStorage):
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB
This default module will store attachments in the database.
Note
Don't use it with large setups.
Pro: works with multiple front end servers.
Con: requires much storage space in the database.
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageFS
Use this module to store attachments on the local file system.
Note
Recommended for large setups.
Pro: It is fast!
Con: If you have multiple front end servers, you must make sure the file system is
shared between the servers. Place it on an NFS share or preferably a SAN or similar
solution.
Note
You can switch from one back-end to the other on the fly. You can switch the backend
in the SysConfig, and then run the command line utility bin/otrs.Console.pl
Admin::Article::StorageSwitch to put the articles from the database onto the
filesystem or the other way around. You can use the --target option to specify the
target backend. Please note that the entire process can take considerable time to
run, depending on the number of articles you have and the available CPU power
and/or network capacity.
There are two different backend modules for the article storage of phone, email and internal
articles (configured via Ticket::Article::Backend::MIMEBase::ArticleStorage):
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB
This default module will store attachments in the database.
Note
Don't use it with large setups.
Pro: works with multiple front end servers.
Con: requires much storage space in the database.
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageFS
Use this module to store attachments on the local file system.
Note
Recommended for large setups.
Pro: It is fast!
Con: If you have multiple front end servers, you must make sure the file system is
shared between the servers. Place it on an NFS share or preferably a SAN or similar
solution.
Note
You can switch from one back-end to the other on the fly. You can switch the backend
in the SysConfig, and then run the command line utility bin/otrs.Console.pl
Admin::Article::StorageSwitch to put the articles from the database onto the
filesystem or the other way around. You can use the --target option to specify the
target backend. Please note that the entire process can take considerable time to
run, depending on the number of articles you have and the available CPU power
and/or network capacity.
Re: How do I save my tickets' attachment into a file?
Thank you very much for your reply fcasal, I found the setup option. I set this up.
This will be a new system for the company, so it is in the test phase. Maybe I guess this change won't be a problem.
kkgigiioo
This will be a new system for the company, so it is in the test phase. Maybe I guess this change won't be a problem.
kkgigiioo