AppWorx, Dollar Universe and Sysload Community

 View Only

Best practice for batch suite DR

  • 1.  Best practice for batch suite DR

    Posted Jan 07, 2020 10:19 AM
    ​Windows, $U 6.9

    Scenario is there is a batch suite running on node A consisting of several sessions which run in order. All of the $U objects Uprocs, sessions etc are replicated onto the DR node B but any tasks are disabled on node B. In this way Node B can run the batch suite at any time.

    If the batch is running on node A and there is a loss of node then the batch can be continued on node B. The issue is how can $U determine where about the batch suite got to on node A so it can continue from the same place on node B?

    This does sound more like an applications issue, but would like to have as much automation as possible in $U so that the DR node can start running from place the batch suite stopped. It may be that the background DBs that run applications automated by $U would fail over automatically.

    Is there a way to transfer events after every uproc completes or is there a particular $U config to allow DR between 2 separate nodes?