Hello
Thanks for your response.
Indeed the most recent migration involved the activation of the
sogo_store data channel and for this we did a full baqckup of all users
and then a restore.
The reason why we didn't create a new database is because we migrated
this instance rather "quick and dirty" from a CentOS to a Debian machine
when CentOS was discontinued last year.
Greetings
Daniel
On 3/24/25 16:38, Christian Mack ([email protected]) wrote:
Hello
How did you "migrate"?
If you only changed the settings in sogo.conf and restarted sogo, then
your users data are still in those tables.
If you backuped that data with the old configuration and restored it
with the new configuration, you can delete those tables.
Just out of curiosity, why didn't you create a new database for the
new structure?
Kind regards,
Christian Mack
Am 21.03.25 um 16:34 schrieb Daniel Kollmer ([email protected]):
Hello all
In out SOGo installation we have successively migrated stuff from
per- user tables to the separate collective tables so we now have
tables like this:
sogo_acl
sogo_admin
sogo_cache_folder
sogo_folder_info
sogo_quick_appointment
sogo_quick_contact
sogo_sessions_folder
sogo_store
sogo_user_profile
Does that mean that we can delete all tables which have the format
sogo[username[[alphanumeric-string] as well as the
sogo[username[[alphanumeric-string]_quick and
sogo[username[[alphanumeric-string]_acl tables without loss of data?
Greetings;
--
D. Kollmer
Computer Technology Group
NIKHEF - Dutch National Institute for Sub-atomic Physics
