Our client is planning to establish a Disaster Recovery (DR) environment and requires a configuration that ensures an immediate cutover to the DR site whenever the primary site goes down. The expectation is for Laserfiche to remain continuously available without any noticeable disruption to end users.
A key requirement is that the client does not want to go through the process of deactivating and reactivating licenses during failover. Instead, they expect a seamless experience where users remain unaffected by the switch.
The proposed DR site will be a replica of the production environment, including:
-
A Laserfiche Application Server
-
A Web Server (hosting Forms and LFDS)
-
A Workflow Server
With the existing licensing model, failover introduces complications:
-
The Hardware Fingerprint (HWFP) will change once the system switches to the DR site.
-
This change causes the LFDS site to be locked, since there would effectively be two active sites at the same time.
- Allow for multiple domains to be included in the license (as the client currently has two identity providers configured in LFDS). - An application for this update has already been submitted to Laserfiche.
Based on the above and referring to LF documentation, the plan is to
-
Renew the primary license by updating the existing license to domain-based licensing.
-
Re-register all applications (Forms, Workflow, LFDS, etc.) using the updated domain-based license.
-
Validate that the DR site functions as expected under the new licensing model
Could you please let me know if there are any additional considerations we should be aware of before proceeding with the switch? Also, would there be any potential issues in reverting back to an HWFP-based licensing model if required? Ideally, what would the rollback plan look like?
Thank you in advance for your guidance.