Hello Am 17.08.2017 um 16:28 schrieb Zhang Huangbin ([email protected]): > >> On Aug 16, 2017, at 4:13 PM, Zhang Huangbin ([email protected]) >> <[email protected]> wrote: >> >>> On Aug 16, 2017, at 3:41 PM, Christian Mack >>> ([email protected]) <[email protected]> wrote: >>> >>> You have to backup and restore with sogo-tool then. >>> When restoring, you have to first restore all users and their folders, >>> then their preferences. >>> Afterwards you have to restore all preferences again. >> >> Did i understand correctly that the procedure is: >> >> sogo-tool restore -f ALL <backup-dir> <user> >> sogo-tool restore -p <backup-dir> <user> >> sogo-tool restore -p <backup-dir> <user> > > Cannot get it working, shared calendars are always empty, but i can see > there’re shared calendar related data in backup file (generated with > ‘sogo-tool backup’). >
for user in <all_user> do sogo-tool restore -f ALL <backup-dir> <user> sogo-tool restore -p <backup-dir> <user> done service memcached restart for user in <all_user> do sogo-tool restore -p <backup-dir> <user> done Hints: * All configuration files in /etc/sogo/ must be correct. * If you use SIEVE, then you have to use sogo-tool restore -p -c /etc/sogo/sieve.creds <backup-dir> <user> instead. > The backup files were generated with sogo-2.2.15, but SOGo on new server is > 3.2.10 (nightly build). Does it matter? > Yes, that does matter. You have to upgrade to at least 2.3.1 before being able to use the backup for restore on a 3.x.y version. This also means, you have to run the database script sql-update-2.2.17_to_2.3.0.sh or sql-update-2.2.17_to_2.3.0-mysql.sh depending on your dbms. 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
