On 12/16/2010 2:54 AM, Pascal Gienger wrote:
Just a little tip:
When deploying a SOGo installation where the database server will not
reside on the same host as the SOGo instances, be careful to select a
(virtual) hostname which will NOT change for the lifetime of your
installation. Use an DNS alias and use entries in /etc/hosts. Do not
use an IP address as database host name.
Why?
In case you want/have to change your database host (ip renumbering,
infrastructure change, ...) just change the IP entry for that virtual
database host name (either in /etc/hosts or DNS). Otherwise...
you're cooked.
In sogo_folder_info, SOGo stores the URL to the actual storage tables
(data, index (quick) and ACL (acl)) for each calendar and contact
ressource.
Example:
540 | /Users/testuser/Calendar/personal |
Users | testuser | Calendar | personal |
Persönlicher Kalender |
postgresql://sogo:s...@ha-postgres:5432/sogo/sogotestuser0013182468c |
postgresql://sogo:s...@ha-postgres:5432/sogo/sogotestuser0013182468c_quick
|
postgresql://sogo:s...@ha-postgres:5432/sogo/sogotestuser0013182468c_acl
| Appointment
As you can see, it stores links like
postgresql://sogo:s...@ha-postgres:5432/sogo/sogopop211530013182468c_quick
So if you change
- the database host name
- the database user
- the database password
- the database server port number
then you'll have to ALTER ALL ENTRIES in sogo_folder_info.
Pascal
That is actually very interesting. We were about to start moving various
services to different machines, MySQL being one of them. Maybe I need to
rethink that in light of this. That or just do a fresh install since it
is not deployed throughout the agency as of yet.
Donny B.
--
[email protected]
https://inverse.ca/sogo/lists
