Re: [SOGo] SOGo migration 2.2.17a to 5.0.0
Does anyone have an idea? Exported Backup from 2.2.17a via sogo-tool backup inserted into 5.0.0 via sogo-tool restore wont have the contacts and calendar entries show up. Am Freitag, den 25.09.2020, 11:21 +0200 schrieb Patrick Geschke: > Hey guys, > > it seems i've been using the wrong user. > I can now see the folders on > the import (5.0.0) side: > > > host:~/test# sogo-tool -v restore -l /root/test/ > > u...@host.de > > <0x0x55b1989f2a90[SOGoCache]> Cache cleanup interval set every > > 300.00 seconds > > <0x0x55b1989f2a90[SOGoCache]> Using host(s) '127.0.0.1' as > > server(s) > > 2020-09-24 12:58:18.221 sogo-tool[31583:31583] Restorable folders: > > 2020-09-24 12:58:18.222 sogo-tool[31583:31583] Calendar/personal > > (Persönlicher Kalender) > > 2020-09-24 12:58:18.222 sogo-tool[31583:31583] Contacts/personal > > (Persönliches Adressbuch) > > > > Restoring seems to have worked too: > > > host:~/test# sogo-tool -v restore -f ALL /root/test/ > > u...@host.de > > <0x0x558bc13d2ab0[SOGoCache]> Cache cleanup interval set every > > 300.00 seconds > > <0x0x558bc13d2ab0[SOGoCache]> Using host(s) '127.0.0.1' as > > server(s) > > 2020-09-24 13:02:07.071 sogo-tool[31679:31679] restoring record > > 'AE66-5F215500-B3-34415000.vcf' > > 2020-09-24 13:02:07.079 sogo-tool[31679:31679] restoring record > > 'B8E9-5F215500-117-62FC9C00.vcf' > > 2020-09-24 13:02:07.113 sogo-tool[31679:31679] restoring record > > 'B8E9-5F215500-11D-62FC9C00.ics' > > 2020-09-24 13:02:07.118 sogo-tool[31679:31679] restoring record > > 'E864-5F215580-3F-4DB88600.ics' > > 2020-09-24 13:02:07.123 sogo-tool[31679:31679] restoring record > > 'B8E9-5F215500-119-62FC9C00.ics' > > 2020-09-24 13:02:07.127 sogo-tool[31679:31679] restoring record > > 'E864-5F215580-43-4DB88600.ics' > > 2020-09-24 13:02:07.131 sogo-tool[31679:31679] restoring record > > 'E864-5F215580-4B-4DB88600.ics' > > 2020-09-24 13:02:07.134 sogo-tool[31679:31679] restoring record > > '2BD3-5F5EB080-7F-35D7CE00.ics' > > 2020-09-24 13:02:07.138 sogo-tool[31679:31679] restoring record > > '2BD4-5F5EB080-AD-23D10F00.ics' > > 2020-09-24 13:02:07.142 sogo-tool[31679:31679] restoring record > > '2BD3-5F5EB080-87-35D7CE00.ics' > > 2020-09-24 13:02:07.145 sogo-tool[31679:31679] restoring record > > '2BD4-5F5EB080-B5-23D10F00.ics' > > > > But the contacts (there are contacts in the export) and the calendar > entries do not appear in sogo 5.0.0. > > Anyone got an idea? > > Thanks, > Patrick > > Am Dienstag, den 22.09.2020, 08:15 +0200 schrieb Patrick Geschke: > > This would have been the ideal approach, but there are some > > problems: > > > > The old system is legacy and currently still in use, which means an > > in- > > place upgrade is out of the question. > > > > The migration of the old user database is also not an option, since > > the > > new side uses a Plesk + SOGo integration which creates the SOGo > > users > > via a hook that runs post-plesk user creation. > > > > > > > > Am Montag, den 21.09.2020, 14:43 -0400 schrieb Ludovic Marcotte: > > > On 2020-09-21 2:07 p.m., Janis Hamme (lists@hamme.info) > > > wrote: > > > > > > > Don't know if what you try is supposed to work, but it might be > > > > easier > > > > to migrate the entire database to your new system and then > > > > upgrade > > > > the > > > > database schema as described in the user manual for upgrading > > > > SOGo > > > > versions. > > > This is definitively the best approach. > > > > > > -- > > > Ludovic Marcotte > > > lmarco...@inverse.ca :: +1.514.755.3630 :: https://inverse.ca > > > Inverse inc. :: Leaders behind SOGo (https://sogo.nu), > > > PacketFence > > > ( > > > https://packetfence.org) and Fingerbank (https://fingerbank.org) > > > > -- > > Patrick Geschke > IT-Systems Engineer > > openroot GmbH > > // Ibbenbüren > Gildestraße 2 > 49477 Ibbenbüren > > Fon: +49 (0) 5451 560 915 - 0 > Fax: +49 (0) 5451 560 915 - 99 > > M: i...@openroot.de > W: www.openroot.de > > Geschäftsführer: Patrick Geschke > Amtsgericht Hamburg, HRB 142365 > Ust-ID: DE 308025519 > -- Patrick Geschke IT-Systems Engineer openroot GmbH // Ibbenbüren Gildestraße 2 49477 Ibbenbüren Fon: +49 (0) 5451 560 915 - 0 Fax: +49 (0) 5451 560 915 - 99 M: i...@openroot.de W: www.openroot.de Geschäftsführer: Patrick Geschke Amtsgericht Hamburg, HRB 142365 Ust-ID: DE 308025519 -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo migration 2.2.17a to 5.0.0
Hey guys, it seems i've been using the wrong user. I can now see the folders on the import (5.0.0) side: > host:~/test# sogo-tool -v restore -l /root/test/ > u...@host.de > <0x0x55b1989f2a90[SOGoCache]> Cache cleanup interval set every > 300.00 seconds > <0x0x55b1989f2a90[SOGoCache]> Using host(s) '127.0.0.1' as server(s) > 2020-09-24 12:58:18.221 sogo-tool[31583:31583] Restorable folders: > 2020-09-24 12:58:18.222 sogo-tool[31583:31583] Calendar/personal > (Persönlicher Kalender) > 2020-09-24 12:58:18.222 sogo-tool[31583:31583] Contacts/personal > (Persönliches Adressbuch) > Restoring seems to have worked too: > host:~/test# sogo-tool -v restore -f ALL /root/test/ > u...@host.de > <0x0x558bc13d2ab0[SOGoCache]> Cache cleanup interval set every > 300.00 seconds > <0x0x558bc13d2ab0[SOGoCache]> Using host(s) '127.0.0.1' as server(s) > 2020-09-24 13:02:07.071 sogo-tool[31679:31679] restoring record > 'AE66-5F215500-B3-34415000.vcf' > 2020-09-24 13:02:07.079 sogo-tool[31679:31679] restoring record > 'B8E9-5F215500-117-62FC9C00.vcf' > 2020-09-24 13:02:07.113 sogo-tool[31679:31679] restoring record > 'B8E9-5F215500-11D-62FC9C00.ics' > 2020-09-24 13:02:07.118 sogo-tool[31679:31679] restoring record > 'E864-5F215580-3F-4DB88600.ics' > 2020-09-24 13:02:07.123 sogo-tool[31679:31679] restoring record > 'B8E9-5F215500-119-62FC9C00.ics' > 2020-09-24 13:02:07.127 sogo-tool[31679:31679] restoring record > 'E864-5F215580-43-4DB88600.ics' > 2020-09-24 13:02:07.131 sogo-tool[31679:31679] restoring record > 'E864-5F215580-4B-4DB88600.ics' > 2020-09-24 13:02:07.134 sogo-tool[31679:31679] restoring record > '2BD3-5F5EB080-7F-35D7CE00.ics' > 2020-09-24 13:02:07.138 sogo-tool[31679:31679] restoring record > '2BD4-5F5EB080-AD-23D10F00.ics' > 2020-09-24 13:02:07.142 sogo-tool[31679:31679] restoring record > '2BD3-5F5EB080-87-35D7CE00.ics' > 2020-09-24 13:02:07.145 sogo-tool[31679:31679] restoring record > '2BD4-5F5EB080-B5-23D10F00.ics' > But the contacts (there are contacts in the export) and the calendar entries do not appear in sogo 5.0.0. Anyone got an idea? Thanks, Patrick Am Dienstag, den 22.09.2020, 08:15 +0200 schrieb Patrick Geschke: > This would have been the ideal approach, but there are some problems: > > The old system is legacy and currently still in use, which means an > in- > place upgrade is out of the question. > > The migration of the old user database is also not an option, since > the > new side uses a Plesk + SOGo integration which creates the SOGo users > via a hook that runs post-plesk user creation. > > > > Am Montag, den 21.09.2020, 14:43 -0400 schrieb Ludovic Marcotte: > > On 2020-09-21 2:07 p.m., Janis Hamme (lists@hamme.info) wrote: > > > > > Don't know if what you try is supposed to work, but it might be > > > easier > > > to migrate the entire database to your new system and then > > > upgrade > > > the > > > database schema as described in the user manual for upgrading > > > SOGo > > > versions. > > This is definitively the best approach. > > > > -- > > Ludovic Marcotte > > lmarco...@inverse.ca :: +1.514.755.3630 :: https://inverse.ca > > Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence > > ( > > https://packetfence.org) and Fingerbank (https://fingerbank.org) > > -- Patrick Geschke IT-Systems Engineer openroot GmbH // Ibbenbüren Gildestraße 2 49477 Ibbenbüren Fon: +49 (0) 5451 560 915 - 0 Fax: +49 (0) 5451 560 915 - 99 M: i...@openroot.de W: www.openroot.de Geschäftsführer: Patrick Geschke Amtsgericht Hamburg, HRB 142365 Ust-ID: DE 308025519 -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo migration 2.2.17a to 5.0.0
This would have been the ideal approach, but there are some problems: The old system is legacy and currently still in use, which means an in- place upgrade is out of the question. The migration of the old user database is also not an option, since the new side uses a Plesk + SOGo integration which creates the SOGo users via a hook that runs post-plesk user creation. Am Montag, den 21.09.2020, 14:43 -0400 schrieb Ludovic Marcotte: > On 2020-09-21 2:07 p.m., Janis Hamme (lists@hamme.info) wrote: > > > Don't know if what you try is supposed to work, but it might be > > easier > > to migrate the entire database to your new system and then upgrade > > the > > database schema as described in the user manual for upgrading SOGo > > versions. > This is definitively the best approach. > > -- > Ludovic Marcotte > lmarco...@inverse.ca :: +1.514.755.3630 :: https://inverse.ca > Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence ( > https://packetfence.org) and Fingerbank (https://fingerbank.org) > -- Patrick Geschke IT-Systems Engineer openroot GmbH // Ibbenbüren Gildestraße 2 49477 Ibbenbüren Fon: +49 (0) 5451 560 915 - 0 Fax: +49 (0) 5451 560 915 - 99 M: i...@openroot.de W: www.openroot.de Geschäftsführer: Patrick Geschke Amtsgericht Hamburg, HRB 142365 Ust-ID: DE 308025519 -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo migration 2.2.17a to 5.0.0
On 2020-09-21 2:07 p.m., Janis Hamme (lists@hamme.info) wrote: Don't know if what you try is supposed to work, but it might be easier to migrate the entire database to your new system and then upgrade the database schema as described in the user manual for upgrading SOGo versions. This is definitively the best approach. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: https://inverse.ca Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence (https://packetfence.org) and Fingerbank (https://fingerbank.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo migration 2.2.17a to 5.0.0
Don't know if what you try is supposed to work, but it might be easier to migrate the entire database to your new system and then upgrade the database schema as described in the user manual for upgrading SOGo versions. If you only need individual users you can use sogo-tool to export the users after the upgrade to 5.0 and import them into a clean database. Or just remove any users that you don't want to keep. Regards Janis Am 21.09.20 um 19:04 schrieb Patrick Geschke (patrick.gesc...@openroot.de): > Exactly this. > I have a 2.2.17a system where i dumped a demo account, > which previously was also created on the 5.0.0. system. > > Dumping on 2.2.17a with 2.2.17a sogo-tool and importing on the 5.0.0 > system with 5.0.0 sogo-tool failed with mentioned error. > > Am Montag, den 21.09.2020, 17:23 +0200 schrieb Christian Mack: >> Hello >> >> Am 21.09.20 um 14:24 schrieb Patrick Geschke ( >> patrick.gesc...@openroot.de): >>> Hey guys, >>> >>> im running 2 sogo installations. >>> >>> A) SOGo 2.2.17a >>> B) SOGo 5.0.0 >>> >>> And im trying to migrate between those two. >>> One of the major problems is >>> migrating the calendar and addressbook content. >>> When using sogo-tool backup and dumping accounts from the source >>> machine, sogo-tool restore will just show errors like >>> >>> sogo-tool[18746:18746] user backup (/path/to/backup) file could not >>> be >>> loaded >>> >>> Are those dumps incomptabile? What are my options? >>> Sidenote: The user accounts are already created on the target >>> machine. >>> >> You can create a new user on 5.0.0 and he/she can use it? >> You did dump with the sogo-tool from 2.2.17a? >> And you are restoring with sogo-tool from 5.0.0 into 5.0.0 System? >> And all users exist on the authentication source? >> You have setup a new database for SOGo 5.0.0? >> >> Then this should work. >> >> Kind regards, >> Christian Mack >> -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo migration 2.2.17a to 5.0.0
Exactly this. I have a 2.2.17a system where i dumped a demo account, which previously was also created on the 5.0.0. system. Dumping on 2.2.17a with 2.2.17a sogo-tool and importing on the 5.0.0 system with 5.0.0 sogo-tool failed with mentioned error. Am Montag, den 21.09.2020, 17:23 +0200 schrieb Christian Mack: > Hello > > Am 21.09.20 um 14:24 schrieb Patrick Geschke ( > patrick.gesc...@openroot.de): > > Hey guys, > > > > im running 2 sogo installations. > > > > A) SOGo 2.2.17a > > B) SOGo 5.0.0 > > > > And im trying to migrate between those two. > > One of the major problems is > > migrating the calendar and addressbook content. > > When using sogo-tool backup and dumping accounts from the source > > machine, sogo-tool restore will just show errors like > > > > sogo-tool[18746:18746] user backup (/path/to/backup) file could not > > be > > loaded > > > > Are those dumps incomptabile? What are my options? > > Sidenote: The user accounts are already created on the target > > machine. > > > > You can create a new user on 5.0.0 and he/she can use it? > You did dump with the sogo-tool from 2.2.17a? > And you are restoring with sogo-tool from 5.0.0 into 5.0.0 System? > And all users exist on the authentication source? > You have setup a new database for SOGo 5.0.0? > > Then this should work. > > Kind regards, > Christian Mack > -- Patrick Geschke IT-Systems Engineer openroot GmbH // Ibbenbüren Gildestraße 2 49477 Ibbenbüren Fon: +49 (0) 5451 560 915 - 0 Fax: +49 (0) 5451 560 915 - 99 M: i...@openroot.de W: www.openroot.de Geschäftsführer: Patrick Geschke Amtsgericht Hamburg, HRB 142365 Ust-ID: DE 308025519 -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo migration 2.2.17a to 5.0.0
Hello Am 21.09.20 um 14:24 schrieb Patrick Geschke (patrick.gesc...@openroot.de): > Hey guys, > > im running 2 sogo installations. > > A) SOGo 2.2.17a > B) SOGo 5.0.0 > > And im trying to migrate between those two. > One of the major problems is > migrating the calendar and addressbook content. > When using sogo-tool backup and dumping accounts from the source > machine, sogo-tool restore will just show errors like > > sogo-tool[18746:18746] user backup (/path/to/backup) file could not be > loaded > > Are those dumps incomptabile? What are my options? > Sidenote: The user accounts are already created on the target machine. > You can create a new user on 5.0.0 and he/she can use it? You did dump with the sogo-tool from 2.2.17a? And you are restoring with sogo-tool from 5.0.0 into 5.0.0 System? And all users exist on the authentication source? You have setup a new database for SOGo 5.0.0? Then this should work. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
[SOGo] SOGo migration 2.2.17a to 5.0.0
Hey guys, im running 2 sogo installations. A) SOGo 2.2.17a B) SOGo 5.0.0 And im trying to migrate between those two. One of the major problems is migrating the calendar and addressbook content. When using sogo-tool backup and dumping accounts from the source machine, sogo-tool restore will just show errors like sogo-tool[18746:18746] user backup (/path/to/backup) file could not be loaded Are those dumps incomptabile? What are my options? Sidenote: The user accounts are already created on the target machine. Thanks, Patrick -- users@sogo.nu https://inverse.ca/sogo/lists
