Question

Setting up Laserfiche Servers in a remote DR site

Laserfiche Forms WebLink

Updated October 22, 2018

asked on April 20, 2018

Hello,

I have a RIO production site with Laserfiche Server, Forms and Weblink which need to replicated to a another site (DR).

I was planning of setting up new Laserfiche Server, Forms and Weblink on the DR site and then restore the backups from the production environment as DR drill. I wanted to know if this is a good approach.

Since, the new set of servers will have a new hardware fingerprints, what are the configuration changes i should consider taking into account that i will be shutting down the production server during the drill?

Regards,

Vimal

0 0

Answer

SELECTED ANSWER

replied on April 20, 2018

Hi Vimal,

I believe it is the best way to go about this. It will ensure that all data is relevant up to the date of replication. You will then also have historical instances of the Forms processes in production, with corresponding information and documentation in the Laserfriche repository.

Please let me know if you have any questions?

Kind regards,

Freddie van Rooyen

0 0

Replies

replied on April 20, 2018

If you want to use your production server licenses for your backup servers, you will have to first deactivate the production server licenses using the deactivation tool, then reactivate it (either using the same tool, or by re-installing the product) on the backup servers.

If you have extra licenses that your backup servers can use, you can use those instead of doing the deactivation and reactivation.

For more comprehensive information, see the backup and recovery white paper.

0 0

replied on April 27, 2018

Hi Leif,

'Designing a Laserfiche 10 backup and recovery plan' - awesome documentation!!!

Thank you for that.

Just a confirmation - the configuration files can be restored once or a few times as these files won't be changing much,

Regards,

Vimal

0 0

replied on April 20, 2018

Hi Leif,

Does it apply for Rio as well as you can have unlimited servers? Meaning that I would prefer to have separate set of servers for the DR and then restore backups from production.

0 0

replied on April 20, 2018

You'd still have to deactivate and reactivate the Directory Server master license, unless Directory Server is not being backed up. If it's just the application servers, then yeah, the production system and the DR system can run on separate licenses. If you use separate licenses, then there aren't any hardware fingerprint issues.

0 0

replied on April 20, 2018

Thank you Leif. This is where I got stuck - LFDS. I mean I will need to restore one in the DR site and shutdown the production one. Any possibility to simply have a LFDS on DR site without going through this maneuver?

Regards,

Vimal

0 0

replied on April 20, 2018

For testing purposes (i.e. failover and recovery simulation), you can ask your VAR or Laserfiche regional manager for a temporary license.

If you want the second LFDS to be permanently always up and running, you need to purchase an additional license. Otherwise, if you have only one license, there will be some downtime between when you deactivate the old LFDS and reactivate the new one. If you don't use single sign-on, your application servers will still be able to function for a 7-day period without calling back to LFDS, when LFDS is down. But if you're using single sign-on, users won't be able to authenticate to application servers when LFDS is down.

0 0

replied on October 22, 2018

Where can I find the documentation for this? I've looked high and low in whitepapers and online...

"application servers will still be able to function for a 7-day period without calling back to LFDS, when LFDS is down."

0 0

replied on October 22, 2018

In the "Designing a Laserfiche 10 Backup and Recovery Plan" white paper linked to above, check out the "Recovering Laserfiche Directory Server" section.

0 0

You are not allowed to follow up in this post.

Question

Question

Setting up Laserfiche Servers in a remote DR site

Answer

Replies

Sign in to reply to this post.