You are viewing limited content. For full access, please sign in.

Question

Question

Disaster Recovery For Workflow

asked on August 11, 2014

Hi Folks,

I have a customer that is putting together a disaster recovery plan for Laserfiche Workflow.

As it is not possible to run Workflow in a clustered environment, we are looking to run a workflow server in the production environment and in the DR environment.

 

What we would like to do is:

 

Have two WF Servers and Subscriber Services installed and configured.

Production to the Production Repo, and DR to the DR Repo.

We believe that we can have the Workflow Servers started in both environments, but initialise the Subscriber service in DR after bringing the DR repo online. This would allow us to keep the workflows in sync as they are modified in Production.

 

Has anyone tried running two Workflow servers ? and then using the Subscriber service as the switch ?

Does anyone think the the MSMQ's would need to be replicated ? and what impact could this have ?

0 0

Replies

replied on August 14, 2014

Hi Chris,

 

Just wanted to let you know that the Workflow team is aware of your question, and will be providing insight soon.  They've been pretty swamped this week, but they should have time to get you a response before the end of the week.  Let us know if you don't hear anything by then.  Thanks for your patience!

1 0
replied on August 17, 2014

Hi Brett,

Still waiting to hear from the product team.

0 0
replied on September 3, 2014

 < bump />

0 0
replied on August 12, 2014

Hi Chris,

 

We have implemented Workflow in DR, the system works well without any problems.

 

DR workflow server do not needs to run in parallel with the Production workflow server. MSMQ does not require to be replicated, even we have omitted that in our DR setup.

 

Is your Production and DR servers are pointing to same DB server?

It is recommended to start the workflow server services after the DR Rep is online.

 

 

0 0
replied on August 12, 2014

Hi Kirrubananthan

We have the DR workflow server currently pointing to it's own DR db instance.

The only real reason for contemplating keeping the DR Workflow Server online, was to be able to easily push updated workflow templates across to DR.

 

So would you suggest that we restart the Workflow service on failover ?

0 0
replied on August 16, 2014

Hi Chris,

 

It does not require restart of Workflow server service, in this case.

 

Though it was not running templates must be updated with SQL server system.

Did you face any issues, WF templates not getting updated?

 

 

 

 

 

0 0
replied on August 22, 2017

Hi Folks,

so this issue remains 3 years on, the workflows only start in DR if they are uninstalled and re-installed.
Any ideas / suggestions ?

0 0
replied on September 8, 2017

Guys,

Any update on this please?

We can really do with some guidance here.

Thanks

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.