Sorry, I should've been more specific. The Subscriber writes its monitored repositories to the registry. Are you transferring those keys to the DR server?

Dear Miruna,

We are not transferring registry keys, but will configure again in DR workflow server at the initial stage.

Then I'm not sure what you're really asking. Once you configure the Subscriber, it will start processing events from that point on.

We have set up the DR in January 2016. and tested all working fine. 

Then we stopped the services in DR and moved the services to Production system. When we started the DR again in today, the workflows in DR started to trigger for all documents created from January 2016.

I need to overcome reprocessing the files in DR again. How to overcome this subscriber trigger again which are triggered by production subscriber?

This is expected behavior for a Subscriber that's fully configured then shut down. When it's restarted, it tries to catch up with the work it missed.

In your case, you want the Subscriber to start processing only events going forward. You have 2 options:

1. You only configure it to add the repository when it needs to start working.
2. If you configure it beforehand, you can then shut it down and edit the registry to indicate that it only needs to process events going forward: HKEY_Local_Machine\Software\Laserfiche\Workflow\Monitored Repositories\<Repository ID>. Edit the ASN value and set it back to 0. Keep in mind that every time the Subscriber is started, it will monitor the repository for events and write the latest processed activity log ID to the ASN value. So if you do testing of your DR server, you'll have to reset the ASN to 0 after each round of testing.

Thank you Miruna For the recommendation.

I could only see one repository with ASN Value in the Registry, other repository does not have ASN key created. 

What does the ASN 0 means? Does this mean, Assigning 0 to ASN value makes Subscriber to stop processing which are missed when it was missed?

The ASN is the ID of the latest event the Subscriber processed. Setting it to 0 indicates to the Subscriber it's supposed to only process events going forward, not try to catch up where it left off before it was shutdown. The Subscriber service needs to be shutdown before modifying the registry.