Core upgrade from 8.5.3 to 8.5.8 - How long does kopano-dbadmi take to run to fix K-1216 error

Can someone tell me how long it will take to run the K-1216 fix?

I tried to upgrade this weekend, giving myself a 2 hours outage window. But after 4 hours! I needed to revert back to backups and bring the system back online…

I want to upgrade, but I need to give my users a realistic outage window.

Thanks
Bob

It took mine about 1 hour but then it completed.

@mcostan Any idea how big your DB is?

a du -h /var/lib/mysql on the database server sayd 35GB

Mine says 453GB. Assuming a linear progression, it would take 13 hours!!!

I’m wondering if a developer could confirm this!

I run my database on a virtual machine (albeit on SSD disks) and not such a powerful disk, so I don’t think you can extrapolate my numbers. It’s not a particularly fast machine.

@robertwbrandt said in Core upgrade from 8.5.3 to 8.5.8 - How long does kopano-dbadmi take to run to fix K-1216 error:

Mine says 453GB. Assuming a linear progression, it would take 13 hours!!!
I’m wondering if a developer could confirm this!

Hi @robertwbrandt ,

I would recommend to get in contact with our support on this. They have an overview on reported database sizes and conversion time. This btw. also depends largely not only on total database size, but also cpu speed, i/o, etc.

This post is deleted!

My test for our ~500GB database took 16 hours. I’m waiting for the updates to allow us to index the tags online which is 90% of the time.

@deisenlord - My test for our ~500GB database took 16 hours.

I’m performing my upgrade this weeeknd, I will let everyone know how long it takes. (But I’m now planning on 16+ hours)

Thanks
Bob

@robertwbrandt just wondering how long it took for you? my db is 320GB it took 25h for me and then it started on defrag and says that finishing time is 20 DAYS!! :O

I actually haven’t done it yet. I need to wait for a long Bank Holiday weekend where the business is completely off before I even start!

I was told by support that I could start the DB migration/fix and if I needed to, I could run kopano-server with the --ignore-db-(something) switch. But I would get that from support yourself just to be sure.

Always watch out for index creation failure. If you did not provide enough disk space for the SQL indexes, you’re paying with time instead. (dbadm will tell you so!)

i have created an ticket about this, as I did an apt-get update; apt-get upgrade and saw it as an minor update of the software and continued with the installation and after that had to set up alternate ways for communication for 25h, now it has failed with the defrag a couple of times, hoping to get an answer soon from support though.

@jengelh said in Core upgrade from 8.5.3 to 8.5.8 - How long does kopano-dbadmi take to run to fix K-1216 error:

Always watch out for index creation failure. If you did not provide enough disk space for the SQL indexes, you’re paying with time instead. (dbadm will tell you so!)

you think i need more than 1.2TB of disk space for the indexes?