Content Server Replication

Ray_Rickard · ‎07-28-2020

Are there any mechanisms available in MaxDB 7.9 to replicate data between Content Servers? We have the option of putting cache servers in our remote business locations, but my understanding is that check-ins of documents still come back to the primary Content Server. Our ideal scenario is to have Content Servers in those remote locations with replication keeping them in sync, so that any content would be available 'locally' to the user requesting it. That would not necessarily have to be real-time, just 'near-time'.

Without the possibility of replication, putting Content Servers in the remote locations seems like it would create silos of data; where local user data would both check in and out from their local Content Server, and that would require a Cache server in each other location to pull those files (on request).

I am curious to know how other customers are managing requirements such as these.

former_member1192876 · ‎08-31-2021

Hi Ray,

have you got an answer or have you come up with an alternative to your challenge?

We are too facing the problem right now and not finding anything other than the caching setup posibility.

best regards,

Ilyas

Ray_Rickard · ‎09-04-2020

Thanks for the information, our question is not specifically about simply replicating a MaxDB copy to other locations, but rather putting information stored in the MaxDB instances at the users fingertips. Example is we have Engineering teams across the globe, and ideally each team would have their own Content Server that they use to check documents in and out. Since the teams collaborate with one another, the ideal would be to have a document checked into one system replicate to the Content Servers in a reasonable amount of time. At present I do not see any means to do this, but it has been suggested to put a Content Cache server in the remote locations, but check ins of any work performed by the remote teams would still suffer the latency of checking that data into a remote Content Server. We are trying to address both the latency experienced by a remote user checking documents into and out of Content Server.