On 8/20/2015 1:19 PM, Hartmut Raithel wrote:
Am 20.08.2015 um 13:48 schrieb Ludovic Marcotte:
If you're moving entirely to a new server - I would suggest to
backup/restore the SQL database itself. If you need to, you can
adjust the "location" values from the sogo_folder_info. Using
sogo-tool backup/restore will modify the c_lastmodified for all
entries, which means the collection tag will change for every single
addressbook and calendar. That means the CUA will usually force a
full refresh of each collection. For 4,000 users, that might put some
stress on your server.
Hi Ludovic,
ok, I'll try it with sql backup and restore. Regarding modification of
the location tables in sogo_folder_info: Do you mean to change the
servername in the values? So there ist 127.0.0.1 in my sogo.conf and
the postgresql db is still on local machine, i asume there is nothing
to modify. Isn't it? For example:
postgresql://<user>:<password>@127.0.0.1:5432/sogo/sogohraithel0011d7a000d
- nothing to change, from my point of view.
Regarding stress on my server, we have vacation time at moment, and
all our systems are bored...
...but on 1st of October, semester startup, i'm sure all red lights
will raise - as usual. ;-)
I can imagine many scenario where a user wishes to migrate from an old
server to a new server.
A migrator script that "just works" and migrates sogo fully
automatically, would be very cool !
--
[email protected]
https://inverse.ca/sogo/lists
