I have a prospect for Laserfiche RIO - 100 users.
There will be multiple instances of workflows running, audit trail reporting, web access and eventually BI and advanced reporting/ dashboards on Laserfiche data & workflows.
Based on the Laserfiche hardware planning guide, we have recommended a 3-tier architecture and the data will reside on a SAN. The servers will be MS Hyper-V virtual machines dedicated to Laserfiche components as follows:
· Web server - 4 CPU and 8 GB RAM
· MS SQL server - 4 CPU and 12GB RAM
· Laserfiche App/ workflow/ audit trail server - 4 CPU and 12GB RAM
1. Is it mandatory to have the SQL on physical server? I understand that for best performance, MS SQL needs to be on a physical server but how can we covert that onto a virtual machine specifications for Laserfiche. I need to cater for high availability and backup and having 2 physical servers dedicated to MS SQL will complicate the setup and increase costs.
2. The prospect is also working towards his DR site and expects a RPO of 4 hours. We normally use visionsolutions Doubletake replication software to replicate the VMs.
Since we have a RIO solution and unlimited servers, we could setup a Laserfiche server and MS SQL server on the DR site. Then I believe that we would only need to replicate the Laserfiche Volumes and Laserfiche MS SQL database files to the DR setup.
a. Please validate the above approach and provide your recommendations or better alternatives.
b. The other challenge is how can we ensure that the volumes and database are in sync. It is expected that Laserfiche will be heavily used with multiple workflows running in parallel.
c. Is case of a disaster, is it possible to resume the workflows from the disaster point/ last replication state on the DR server?
3. Is there a template that you can share to draft Laserfiche project plans and analyse/set the scope of work for Laserfiche projects (Avante, RIO, Workflow). We wish to standardise on Laserfiche approach and methodology