Dears
We have a DR (Disaster Recovery) setup of Laserfiche Rio servers already, however we have not setup the Directory server yet.
Did any one has setup DR for Directory Server already, if yes can you share the procedure you have followed?
Dears
We have a DR (Disaster Recovery) setup of Laserfiche Rio servers already, however we have not setup the Directory server yet.
Did any one has setup DR for Directory Server already, if yes can you share the procedure you have followed?
Hello Kirruba,
Please follow the instruction as per the following link.
Thank You.
Mazahir,
Thank you for the update!
I'm not looking for failover clustering. On disaster we might not able to do failover using cluster server.
So I'm looking specifically for DR!
Regards
Kirubaa
Can you elaborate on what you mean by DR that is not covered by a failover cluster? Disaster Recovery is a broad term that basically just means "a plan in place to handle disaster with minimal business impact".
Are you looking for backup options?
Hi Brianna,
I'm looking for Disaster recovery option for LFDS. We DR for rest of the Components, such as Laserfiche Server, Workflow server, Webaccess, and Quick fields.
We are facing an issue during DR drill, due to the LFDS is still in Head office. If the LFDS services running in HO and DR servers able to connect to the HO, then DR Laserfiche servers are working fine.
We are now looking to setup LFDS in DR!
Please advise.
I'm still not quite clear what your definition of "DR" is.
Are you saying you want to be able to move LFDS to a different physical location? If so, are the computers from this second location completely separate from the machines at the head office?
If not, you could potentially still use failover clustering.
If they are, you would need to handle the transition to an LFDS in a separate location yourself. You can handle the transition of the SQL database backend the same way you do for LFS.
If possible, I recommend configuring your DR licensing site (using your master license), then deactivating it and turn off the LFDS service.
In that case, you would do the following:
To prevent the need to re-license your machines when LFDS is moved, you can set up a DNS alias. Or, if your DR environment is identical to your production environment, just ensure that the LFDS machine has the same name.
Hi Brianna,
do you mean export the LFDS DB on the production server, move LFDS DB to DR server, Import DB and attach licensing site on DR server? in theory this will result in a active-active DR solution?
Is this a workable solution?
Hi Brianna,
Thank you for the reply!
I think the approach of Deactivate and activate is the only option, when setup a LFDS in DR!
Hope Attaching and pointing to the existing Database would be straight forward, without any complication.
Can we map DNS name with IP using the HOST file instead of changing the DNS server?
Do you use Single Sign On?
If not, mapping it in the HOSTS file might be OK, since you would only need to update the file on all your machines that talk to LFDS directly even without SSO: Laserfiche Server, Web Access, and Quick Fields.
If you do use SSO, users are redirected to a login page hosted on the LFDS machine, so all their personal machines would also need to be updated, as well as the Forms and Discussions machines if you use those products.