Am 18.10.19 um 11:00 schrieb Thierry Murgue ([email protected]): > Le 18/10/2019 à 10:13, Christian Mack ([email protected]) a > écrit : >> Am 17.10.19 um 23:36 schrieb Robert A Wooldridge >> ([email protected]): >>> I would like to migrate my current sogo config which is version 3 to a >>> new machine using v4. Any suggestions on the best way to approach this? >>> >> >> 1) setup empty V4 >> 2) get a complete Backup with sogo-tool on V3 >> 3) move backup data to V4 machine (rsync) >> 4) restore with sogo-tool >> >> See also: >> http://wiki.sogo.nu/backupRestore >> > > Should I do the same, if I just want to upgrade in-place a v3 install on > same server like : > 1) backup with sogo-tool > 2) backup sogo.conf > 3) delete v3 packages (purge SQL database) > 4) install v4 packages (create empty database) > 5) restore sogo.conf > 6) restore with sogo-tool? > > Is it the best way, the more secure one? >
You should always make a backup with sogo-tool before Upgrading a major release. But if you already were on 9 tables database layout in V3, and want to keep it, I would just use the upgrade script provided in V4. Else do it via sogo-tool restore. That way is a little bit cleaner, but the script will be a lot faster. With a little bit cleaner I mean, that it will store all recurring events with exceptions in the new format. The script will keep those the way they are, till you change them via SOGo webinterface or calDAV [or ActiveSync]. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
