> On Aug 18, 2017, at 6:09 PM, Christian Mack ([email protected]) > <[email protected]> wrote: > > for user in <all_user> > do
This helps. Thank you very much. >> 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. This is what i did, it’s fully working with SOGo-2.3.22 (the latest 2.x), but NOT fully working with SOGo-3.2.10: 1) On OLD server, it runs SOGo-2.2.15. Take backup with 'sogo-tool backup’. 2) Setup a new (1st) VM with SOGo-2.3.22 (latest nightly build), drop sogo database, re-create the database and restart SOGo. SOGo creates required SQL tables automatically. Note: since it’s already 2.3.x with new SQL structure, i didn’t run the database script "sql-update-2.2.17_to_2.3.0-mysql.sh”. 3) Restore SOGo backup data (toke on step 1) with ‘sogo-tool restore’. Everything is fine, personal calendars/contacts and shared calendars are all present. 4) Now take a backup on this new (1st) VM with SOGo-2.3.22 (sogo-tool backup). 5) Setup 2nd VM with SOGO-3.2.10 (latest nightly build), drop sogo database, re-create the database and restart SOGo. SOGo creates required SQL tables automatically. Restore the backup token on 1st VM (step 4) with ’sogo-tool restore'. Personal calendars/contacts are all present, but no shared calendars. Was any step wrong while restoring with SOGo-3.x? How can i correctly restore shared calendars? Thank you very much for helping. ---- Zhang Huangbin, founder of iRedMail project: http://www.iredmail.org/ Time zone: GMT+8 (China/Beijing). Available on Telegram: https://t.me/iredmail -- [email protected] https://inverse.ca/sogo/lists
