Migrate server with more than 100,000 tickets

Technical assistance
1

Used Zammad version: 5.0.x
Used Zammad installation type: (source, package, docker-compose, …) Package
Operating system: Debian 11
Browser + version: Chrome 96.0.4664.110 (Official Build) (64-bit)
Expected behavior:
I have a server configured to use an nfs resource as storage, this resource already occupies more than 600 Gb with more than 100,000 tickets, and searches by ticket number are failing, not finding any. We are considering migrating to a new server leaving the tickets closed on the old server as a historical record, any recommendations or better ideas? Can you help me?
Actual behavior:
Failing searches by ticket number, none found

Thanks & Regards,

2

Our documentation has a very clear how to migration:
https://docs.zammad.org/en/latest/appendix/backup-and-restore/index.html

Also, Zammad 5.x is extremely outdated. You may want to keep it up to date much better. You’ll have to upgrade to a more current version before migration.

1 Like
3

Thank you for your reply, my question is whether to continue with this server, if I do I should follow the procedure you indicate, would it affect storage? permissions on all objects? it is a very critical environment for me.
Is there any alternative to maintaining this server?

4

I cannot answer infrastructural questions for you, that is something you have to be able to answer yourself, sorry.

Apart from that, NFS storage is always a bottle neck. Especially as Zammad attachments (given they’re in the file system) are dozen little files which kills all block storage performance.