Clustering vs Multiple CS

A) For Documentum 6.5 Content Server, is there any particular advantage to using clustering of the Content Server vis-a-vis configuring multiple docbrokers, content servers for the same docbase ? Any difference in failover switching times ?

Anyone done CS clustering on HP-UX platform ? (The documentation only mentions Microsoft cluster services ).

C) Will DFC sessions be maintained when the cluster switches over ? Will workflows that were executing auto-activities at the point of node failure continue executing when the node switches over ?

Best Regards
GN

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Pie

I've not done clustering with the Content Server. I have found it much easier to create multiple Content Servers beacuse I can always have an Active-Active configuration and can scale it beyond 2 servers. For some information on how it can be setup, see the discussion onDocumentum High Availability on AIX.

-Pie

All comments

Pie

-Pie

gijunair

Thanks Laurence,

Even I was wondering if multiple CS is so easy, why would someone go for a solution using Cluster Services. ?

Pie

Simple, it didn't use to be easy, so clustering was the "easy" way out. It is also a little challenging to us this method to install multiple repositoriess on the second content server.

To top that off, it isn't clearly documented now, as the Support Note indicates, so awareness is low.

-Pie