<html>Wolfgang,<br /><br />If you don't mind, I'd like to know if when you upgraded backend servers from 2.4 version to 2.5 version you have an increase, in metadata size.Here we had 30% around of increase<br /><br />Thanks one more time<br /><br />Greetings<br />--<br /><br /><font size="3"><b>Miguel Moreira</b></font><br /><font size="3">DTE/SRE/GRE - Gerência de Redes<br />+55(31)3339-1401<br />PRODEMGE - Companhia de Tecnologia da Informação do Estado de Minas Gerais</font><br /><br /><br /><font size="2">Aviso: Esta mensagem é destinada exclusivamente para a(s) pessoa(s) a quem é dirigida, podendo conter informação sigilosa e legalmente protegida. O uso impróprio será tratado conforme as normas da empresa e a legislação em vigor. Caso não seja o destinatário, favor notificar o remetente, ficando proibidas a utilização, divulgação, cópia e distribuição.</font> Em Terça, Junho 09, 2020 10:39 -03, Wolfgang Breyha <wbreyha@gmx.net> escreveu:<blockquote type="cite" cite="40e951d9-111a-e811-2a51-073413633d52@gmx.net">Hi!<br /><br />On 09/06/2020 14:56, Miguel Mucio Santos Moreira wrote:<br />> Dear Wolfgang,<br />><br />> Firstly thanks for your answer, secondly I have one more doubt, during this<br />> time where the new Mupdate Master is receiving mailboxes information from<br />> backend servers, is necessary stopping comunications between frontend<br />> servers and mupdate master or none action is necessary besides that one<br />> you've mentioned before?<br />> We're concerned if frontend servers will connect to Mupdate Master and<br />> receive from it an information which there's no mailboxes anymore until the<br />> backend push entirely mailboxes information and this situation to cause any<br />> trouble.<br /><br />I recommend the follow steps:<br />*) check that your currently running setup has no conflicts in mailboxes.db<br />by running "ctl_mboxlist -mw". It is possible that you see output if<br />somebody changes his mailboxes while you run the command, but it should<br />not appear again if you run the command a second time. If everything is<br />fine...<br /><br />*) shut down all running cyrus<br />frontends first, then backends and mupdate last<br />*) backup your mailboxes.db on mupdate server<br />*) replace/update mupdate and start it with empty/removed mailboxes.db.<br />*) backup your mailboxes.db on the backends<br />*) do the ctl_mboxlist -m by hand on the backends (only one at the same<br />time) you can check if everything went ok with "-mw" at any time<br />afterwards.<br />*) start cyrus on backends<br /><br />In our setup the frontends have mupdate running as well. I can't currently<br />remember if this is mandatory. If this is true in your setup then:<br />*) remove or rename the mailboxes.db database on the frontends and start<br />them. They will fetch the database immediately from the mupdate server.<br />This is visible in syslog as well and takes about 30 seconds in our<br />setup (~250MB mailboxes.db).<br />otherwise<br />*) start the frontends<br /><br />At this point everything should be up and running again.<br /><br />Watching syslog output all the time usually helps.<br /><br />IIRC we updated the mupdate server to 2.5 first. Then we had a mix of 2.4<br />and 2.5 backends for some time. The 2.5 backends had some capabilities<br />suppressed. Frontends had 2.4 until all backends had 2.5. Last but not<br />least we upgraded to 2.5 on the frontends.<br /><br />If you need more info/details feel free to ask.<br /><br />Greetings, Wolfgang<br />--<br />Wolfgang Breyha <wbreyha@gmx.net> | https://www.blafasel.at/<br />Vienna University Computer Center | Austria</blockquote></html>