On 31 Jan 2015, at 17:29, Mathias Bräunling wrote:

Hi,

31/01/2015 17:20 - Ml Ml wrote: Hello,

we startet with otrs and Article attachments are stored in the DB until now. Of course the db is growing and growing we have about 10GB of DB and a backup takes ages ...

Can i now switch to FS based storage and keep the articles until now in the DB?

I have already tried to run the migration script from DB to FS. This fails with a few articles. Can i just skipp those and carry on?

So at the end the failed articles will remain in the DB and the rest will be FS?

yes, it will work like that. Some articles might not be switched over because of a number of reasons. However, you can still leave those in the DB and move the rest to FS using otrs.ArticleStorageSwitch.pl from the bin directory.

If you do this and use OTRS 4, also make sure to activate the "Check All Backends" option in SysConfig. Otherwise ith might be, that OTRS will not correctly display tickets with articles remaining in the DB.

Just two things to pay attention to… activating this option will generate tons of small files on the FS. This has cause 2 issues for us: 1. Running out of inodes on the partition (“df -i” to monitor this) - we’re using Linux. I don’t know if there can be a similar problem on Windows 2. The backup solution we were using was based on a file-level backup. It ended up choking with so many files -> we had to change our backup method for this specific server. OTRS AG could probably improve things significantly by changing their storage format (one .tar file for all the articles of a given ticket for instance), but I didn’t raise any ticket with them regarding this issue as it’s not really a bug (it’s definitely a potential problem for scalability though). otrs.ArticleStorageSwitch.pl is a bit limited as well (it’s lacking options to select the tickets you want to migrate), but well… Olivier