Hi,
We are trying some scenarios of Disaster Recovery and are wondering how we could recover an installation, when the DS and the Laserfiche License DB can't be recovered.
Infrastructure :
Server A : Windows Server 2016 with Directory Server/SQL Server database with the Laserfiche License DB
Server B : Windows Server 2016 with Laserfiche/Forms/Workflow/WebLink - Components are linked to the directory server
Server C : Windows Server 2016 SQL Server database with the Laserfiche, Forms, WF, WebLink DB
Scenario :
The server A crashes with no possibilities to be recovered and without any backups.
We want to install a new Directory Server, then with new SiteID and new Licence Manager Database.
And then "link" all of the components installed on the Server B (Laserfiche, Workflow, ...) to the new Directory Server.
Is that possible ?
Question
Question
Disaster Recovery for LFDS 10.3.1
Replies
From an administration perspective I think you've got this wrong. If you can end up in a situation where all data on server A is lost with no backup then the same thing could happen to Server B or C. Losing your repository or workflow databases with no hope of recovery would be a disaster you could not recover from.
This is something you need to address from the network administration side of things, and make sure that you won't end up in a situation where the data is lost with no hope of recovery. You need to alter your scenarios to include things like electric generators, cloud and off site backups, VM imaging, etc...
If you're concerned about how to free up server A's license for use on the new Directory Server, the answer to that is to use the deactivation tool. You'll need the hardware fingerprint and host ID of server A, in addition to the activation key.
After you've deactivated server A, you can use the same activation key for the new Directory Server.