Discussion

Laserfiche RIO Server on a Microsoft Cluster Server with Active Passive Fail Over - Licensing Issues?

Laserfiche Licensing Installation and Upgrades

Updated September 29, 2017

posted on January 27, 2016

I'm Wondering if anyone have any experience with Running a Laserfiche Server in a Microsoft Server 2012 Fail over Cluster Configuration.

I' not sure if the Laserfiche Directory Server for Rio can handle this scenario, or at least we seem to be having an issue configuring it correctly.

Here is a simple explanation of the scenario we want.

We Have a Microsoft Cluster Server with 2 Nodes (Server1 and Server2)

Laserfiche Server is installed on Both sides of the Cluster.

It is set to fail over from one active node to the other as needed.

The Display name for the Virtual Cluster Server Resource seen by the Domain is, lets say "Server3"

This is the common Laserfiche Server Name that will be broadcasting our Repositories.

The Question is how to apply the Licensing from the LFDS server.

I can register "Server1" with LFDS and assign the license to that node

-> When I do, it gets the hardware fingerprint of that Node

I can register "Server2" with LFDS and assign the license to that node

-> When I do, it gets the hardware fingerprint of that Node

I can even register " Server3" (the virtual resource) with LFDS )

-> When I do, it gets the hardware fingerprint of the Current Active Node

----------------

Once I have the lic files copied to each server I can test the Laserfiche service from the Cluster.

I made sure all dependencies are there for Laserfiche to run.

Initially The Laserfiche Server Started on Node 1 of the Cluster and we Created a test Repository.

I attempted to Fail it over to side 2 and was not able to get the Laserfiche Server to Start on Node2

Can anyone with experience with this type of configuration shed some light on this subject.

Also if anyone in Development or Testing for Laserfiche Directory Server sees this post, can you please let me know if the configuration I am wanting to setup will work with LFDS and the regular Polling of the LF servers.

Thanks for your thoughts,

Milton K

0 0

Comments 0
Follow-Ups 2

You are not allowed to reply in this post.

License distribution

Discussion 1

posted on January 28, 2016

Hi Milton,

First you don't have to register "Server3" (the virtual resource) with LFDS, you need only to register and generate licenses for the two nodes.

After that you install both servers with generated licenses then register your repository from the active node only.

Important Notes:

Make sure to check the configuration specially (SQL Connection String & Registry replication key) as Laserfiche has issue in this point so you have to rename the registry key: (EncryptedConnectionString) and create new one: (ConnectionString) with proper connection string as stated in (Enterprise Deployment: Failover Clustering Considerations for Laserfiche) document on both nodes.

https://support.laserfiche.com/search/RecordClickHandler.ashx?url=https%3a%2f%2fsupport.laserfiche.com%2fGetFileRepositoryEntry.aspx%3fid%3d2204%26mode%3ddownload&sid=82711881-2889-477a-8b62-7c4f0391a290&rank=2

0 0

replied on January 29, 2016

Thanks Abdellah, you sent me in the right direction.

The document is quite old but the principles are the same. The Connection String is a little different for Version 9 or 10 or Laserfiche as they use a newer version of the SQL Client.

Basically when you setup the Microsoft Cluster Server to Active / Passive in the scenario mentioned in my first post you need to manually add a ConnectionString to the SQL database in the Registry and once done Make sure that this key is Replicated on Fail Over to the Other node on the Cluster.

Here is the Registry Key that needs to be added for Fail over to work:

HKEY_LOCAL_MACHINE\SOFTWARE\Laserfiche\Engine\Repositories\YourRepository

in this path once you create your repository you will find a Key:: EncryptedConnectionString

You should rename this to OLD and add a new Key:

ConnectionString

with the following String Value:

Driver={SQL Server Native Client 10.0};SERVER={YOURSQLSERVER};Trusted_Connection=yes;DATABASE={YourRepository};

Replace "YOURSQLSERVER" with well you know

Same with "YourRepository"

Hope this helps someone.

Happy Clustering

SQLstring.png (64.14 KB)

| Download

1 0

replied on December 6, 2016

Thank You Milton.

Helped me very much.

Regards

Sufyan Khatib

0 0

Discussion

Discussion

Laserfiche RIO Server on a Microsoft Cluster Server with Active Passive Fail Over - Licensing Issues?

Comments 0

Follow-Ups 2

License distribution

Discussion 1

Sign in to reply to this post.