Question

Rio Enterprise Implementation

How To Laserfiche Ideas License Manager Distributed Computing Cluster

Updated August 10, 2016

asked on August 10, 2016 • Show version history

Hi Everyone,

we would to know how possible Rio get working on the following:

Environment sites:

Primary site contains (2) DC replicating each other (DC-1 & DC2) on VM mode on NetApp storages at OS level
DR site contains the failover environment on OS level
DBs level Oracle is managed by Oracle RAC (
DBs level MSSQL managed by MSSQL on both DC-1, DC-2 & DR

Clustering : Clustering Environment running VMs between DC-1 & DC-2

DR scenario : Case DC-1 goes down then DC-2 will takeoff & if DC-1 & DC-2 goes down DR will takeoff

Required to know the following:

The LF directory server to be installed on primary site at DC-1 or DC-2 or can it be clustered on between DC-1 & DC-2 with LF DCC or not
We know that directory server will be down still LF servers will work 7 days but in this case how we can cluster the LF directory server
All modules to be installed on DC-1 & DC-2 then apply LF-DCC on them as scheduler & or worker or both (I know the DCC Scheduler & worker will be utilized for load balancing such WF & other modules)
Failover will be managed by LF directory server with option of failover types (redirect nodes, etc…)
Expecting add more organization on the future utilizing the same but LF directory server will be managed by H.Q.

Appreciate feedback on above if anyone came across such implementations before,

B.R.

Hisham

0 0

Answer

APPROVED ANSWER

replied on August 10, 2016 • Show version history

Failover clustering is supported in Laserfiche Directory Server 10, though it is not related to the separate product, Laserfiche Distributed Computing Cluster. It uses the Windows Failover Clustering feature.

For information on configuring Directory Server failover clustering, please read KB1013718.

Failover clustering is a clustering model that brings up a new machine when the current instance goes down. This is in contrast to the Distributed Computing Cluster product, which is a load balancing cluster that distributes the load of OCR to multiple machines.

For example, if you have Directory Server installed on Machine1, and the Service for Directory Server goes down, a correctly configured failover cluster will bring up Machine2 in your cluster with Directory Server, pointing to the same licensing database.

Furthermore, if configured correctly, they will be reachable through the same name so that no relicensing is necessary.

4 0

Replies

replied on August 10, 2016

Thanks for the answer, So it's only the directory server failover clustering to be used, can it be as much as cluster nodes required or there's limitations for clustered node ?

0 0

replied on August 10, 2016 • Show version history

Directory Server does not enforce a limit, but the Windows feature itself does. I think it supports up to 64 nodes for Windows Server 2012, so it's probably not a limit you need to worry about.

For failover, it's unlikely you would want or need more than a couple failover nodes, since only one will be running at a time.

Again, Directory Server doesn't support distributed clustering in the same sense as the DCC product where multiple nodes are running at the same time; there's no need for it, as it's a fairly low-load application.

If you are planning on using DCC with Workflow or Web Access, it does have a limit to the number of scheduler nodes, but that limit is unrelated to your Directory Server setup.

2 0

replied on August 10, 2016

Got it thanks was confused by the naming since never used DCC where I'm looking for failover

0 0

You are not allowed to follow up in this post.

Question

Question

Rio Enterprise Implementation

Answer

Replies

Sign in to reply to this post.