Hi, I have a production server running Debian Squeeze with Dovecot 1.2 I would like to upgrade everything to Jessie, running 2.2
Last time I did something similiar, but from Lenny to Squeeze, the whole dovecot installation broke.
Any suggestion on how to upgrade everything ? Can I test our current configuration with a newer dovecot version to be sure that everything would be converted properly with "doveconf -n -c /etc/dovecot/dovecot.conf > dovecot-2.conf" ?
Thank you
On 15.02.2017 11:47, Gandalf Corvotempesta wrote:
Hi, I have a production server running Debian Squeeze with Dovecot 1.2 I would like to upgrade everything to Jessie, running 2.2
Last time I did something similiar, but from Lenny to Squeeze, the whole dovecot installation broke.
Any suggestion on how to upgrade everything ? Can I test our current configuration with a newer dovecot version to be sure that everything would be converted properly with "doveconf -n -c /etc/dovecot/dovecot.conf > dovecot-2.conf" ?
Thank you
Hi!
For good pointers, see http://wiki.dovecot.org/Upgrading
it's not complete, but it should give you some idea.
Aki
2017-02-15 13:27 GMT+01:00 Aki Tuomi <aki.tuomi@dovecot.fi>:
For good pointers, see http://wiki.dovecot.org/Upgrading
it's not complete, but it should give you some idea.
I've already read that, and as wrote previously, everything broke down. dovecont -n wasn't able to convert the configuration file and dovecot wasn't started properly. The only way to fix was to downgrade.
As this is a production server, I would like to avoid this kind of issue.....
On Qua, 15 Fev 2017, Gandalf Corvotempesta wrote:
2017-02-15 13:27 GMT+01:00 Aki Tuomi <aki.tuomi@dovecot.fi>:
For good pointers, see http://wiki.dovecot.org/Upgrading
it's not complete, but it should give you some idea.
I've already read that, and as wrote previously, everything broke down. dovecont -n wasn't able to convert the configuration file and dovecot wasn't started properly. The only way to fix was to downgrade.
As this is a production server, I would like to avoid this kind of issue.....
Set up a server replicating exactly the configuration you have at
present. Doesn't need to be anything fancy, a virtual machine is
enough. Actually, a virtual machine is a great tool if you can make
snapshots and then rollback to known states if any attempt at a change
fails.
Do your upgrade work in this new server. Take note of the problems and
the solutions. If you have concrete issues, you can ask help in this
mailing list.
Once you get your test server working, you can then upgrade the real
server using what you've learned from the test server.
-- Eduardo M KALINOWSKI eduardo@kalinowski.com.br
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 15 Feb 2017, Gandalf Corvotempesta wrote:
Any suggestion on how to upgrade everything ? Can I test our current configuration with a newer dovecot version to be sure that everything would be converted properly with "doveconf -n -c /etc/dovecot/dovecot.conf > dovecot-2.conf" ?
actually, you answer your question yourself:
"Can I test"
yes: you can and *should* test, but it's a major upgrade.
I did it so:
- checked out the automated conversation,
- each change I made to the conf of Dovecot v1, I read, what to do in v2 and applied the change to the default configuration manually with hints from the step above
- once all in place, I started a test system with a bunch of accounts that used all features: sieve, sharing, ... .
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEVAwUBWKRMH3z1H7kL/d9rAQIbBgf/YUDU2IQbb8Uhif9q52y2Rk0eJWZJ0j6X LYEEEyHBFgxQA8YRRrgRwkShRPLXzUKIEmMGGsdyCcxwqZvnufcjWuS76EObs1xw Mg5NWbiwgtx0QrCLGoPt2KAC8h2a27AEETgoiF+WzlNteG/uiI7Yz2nKNXMU2Cc0 8rB9BGs16PAukBE0Zkgs2NLMaFt9JqiRPbHxtGaMrecKPDxx8BusK6zpxq69zUDQ Rzdw21+t7eZhSuSbSbf9N/aZRYtJ8b/2RC4FXNuNDTV6vvVngRkxLJSwwfSMB3hu GheseYUKmq9vQWy+lWL1R9tT5gZgTO1s2kmg4uAhQ0KsQ3k0+aDMEw== =rXtr -----END PGP SIGNATURE-----
On 15.02.2017 14:39, Steffen Kaiser wrote:
On Wed, 15 Feb 2017, Gandalf Corvotempesta wrote:
Any suggestion on how to upgrade everything ? Can I test our current configuration with a newer dovecot version to be sure that everything would be converted properly with "doveconf -n -c /etc/dovecot/dovecot.conf > dovecot-2.conf" ?
actually, you answer your question yourself:
"Can I test"
yes: you can and *should* test, but it's a major upgrade.
I did it so:
- checked out the automated conversation,
- each change I made to the conf of Dovecot v1, I read, what to do in v2 and applied the change to the default configuration manually with hints from the step above
- once all in place, I started a test system with a bunch of accounts that used all features: sieve, sharing, ... .
-- Steffen Kaiser
Btw, I think the most safe option would be to make *new* server (advantage to upgrade the platform here too) and migrate users to the new server instead of upgrading. Just my 2c.
Aki
participants (4)
-
Aki Tuomi
-
Eduardo M KALINOWSKI
-
Gandalf Corvotempesta
-
Steffen Kaiser