@Doctrg You should be able to go straight from 1.3.5 to 1.5.4 I think. Make a full DB dump on the old server, install mysql on the new one by hand (yum install mysql mysql-server), import DB dump and then start the FOG 1.5.4 installer. When it asks you to open the web interface go ahead and it should upgrade your database structure - usually does without an issue.
Not saying there can’t be anything going wrong but mostly this is going fine. As you still have the old server (or at least a full backup of machine and DB), you can always give it a try. Shouldn’t hurt.
@Tom-Elliott Store them in the database and have a daily cron job that cleans out logs older than N days (user defined). If FOG were to switch to MariaDB 10.3, the TokuDB engine would be available for use. TokuDB has in-engine compression. The compression savings is pretty staggering compared to InnoDB. TokuDB does not support foreign constraints - and because the FOG db doesn’t use them, we are A-OK there.
@Sebastian-Roth Yes.
I deployed, before update the version 1.5.2 to 1.5.4, without problems one partition using a multicast tasks, but with 1.5.4 doesn’t deploy well.
With unicast d1p3.img --> /dev/sda3
With multicast d1p1.img --> /dev/sda3
