Hi André,
Thanks for the response. Essentially I want to have separate sogo
servers, each one holding data for and serving a different set of users.
At the same time, I would like calendar and contact sharing to work
between the users of the different servers.
This is what I am trying to achieve. I was thinking sharing the
sogo_folder_info among all the sogo servers would help me achieve this.
What do you think?
Regards,
Rahul.
On Thursday 21 April 2011 07:22 PM, André Schild wrote:
Hello Raul,
Am 21.04.2011 09:16, schrieb Rahul Amaram:
I was looking at the mysql tables. And I found that the location for
each of the users data is stored in the sogo_folder_info table. I was
thinking that an architecture as below would scale up.
Master Database located at the data center would contain the table
sogo_folder_info (OCSFolderInfoURL). This database would be replicated
across the geographically distributed offices.
Local Databases at each of the offices would contain the
sogo_sessions_folder (OCSSessionsFolderURL), sogo_user_profile
(SOGoProfileURL) and OCSEMailAlarmsFolderURL. These databases would
NOT be replicated.
Would such an architecture scale up? Is this the reason why these
parameter options have been provided in SOGo configuration file? Or am
I breaking any SOGo functionality by having such a setup?
Does this means that you wish to have ths setup:
- One central database for the master data
- NO central Sogo server
Then at each location:
- A db server with it's "own" users
- A sogo server responsible for it's own users
I think it has not been designed for this, but perhaps it actually works...
André
--
users@sogo.nu
https://inverse.ca/sogo/lists
