Upgrading Documentum Content Server to support high availability

Dears,

I will install the Content Server and Indexing Server on one node for each, i.e doesn't support the high availability, and in the future I want to upgrade my environment to support the high availability environment, so my question is, is the upgrade to high availability environment will damage the repository, i.e I have to delete the repository and create a new one to support the high availability environment, or I can upgrade without problems, if yes, then how?

your fast response will be haighly appreciated.

Thanks in advance.

Find more posts tagged with

Comments

ukdavo

No - introducing HA does not damage your data. The Distributed Configuration Guide describes how to set up additional content servers, etc. I assume that your content already resides on fault tolerant storage such as a SAN. If not, you should think about doing this. You should also consider load-balancing (and possibly clustering) your app servers as well.

Regards

Mark

AhmadAsfour

Thanks for the replu Ukdavo,

But please notice that that the content storage is not in the SAN, it is localy at the Content Server, so is it possible to move it to SAN once it is ready? and when move it to SAN, is this will affect the repository, or we have to reconfigure it to use the shared storage SAN?

And for now, as we have not a HA environment and SAN, how we can backup the content along with the indexes on daily basis?

Thanks in advance...

Haroon_A

If you want to configure additional instances of the content server, and intent do do it on a separate host, then your 'data' directory has to be located on a shared location, and be visible/accessible by your other instances of content server. If you change your 'data' directory, after repository creation/configuration, then you also need to make necessary changes to your repository to find the new location, i.e. server config object/location object, etc...

On another note: You mentioned that you'll intent to install FullText index and content server on the same host. I'd suggest to reconsider this, and try to dedicate a separate host for your fulltext index server. Because the FT Index server is very much CPU/IO intensive, and it'll degrade your content server performance.