Traverse High Availability Options

Follow

Comments

6 comments

  • Avatar
    Chris McBride

    The whitepaper helps, but is pretty much what I thought was the case.  Level-3 HA is custom and expensive.  Level-2 HA is manual, somewhat difficult to recover from, has outage windows, and possible lost data, along with additional license costs.  Level-1 is not an option.

     

     

  • Avatar
    Rob Arends

    We deployed Level-2 HA.  We found the built in backup script did not include every piece required to restore.  So we wrapped the script in our own creation that picks up the missing info (eg custom XML), and replicates it every 6hrs to another server.  The second server has Traverse installed but not running.  There are a number of steps required to restore the data in readiness for Traverse to be able to run as a replacement to the original failed instance.  Our script does all this, including handling of VIP migration between servers. It is long and detailed, but the end result is functional.

     

    It is disappointing that this level of HA,  given you have to buy the standby licences, is not included in the base product.

     

    Rob.

  • Avatar
    Piyush Mehta

    Hello Chris. Rob

    Thank you for your inputs. Your concerns/suggestions have been brought to the attention of the Account Manager.

    Chris - let us know if Support can assist in any way on the ticket.

     

    Regards,

    Piyush

  • Avatar
    Ben Smeele

    Hi Piyush,

    Has there been any development on this or is they only HA option effectively a backup? We need a cluster type setup of active-active so we can ensure up time particularly of the BVE as its a single point of failure.

     

    Regards,

    Ben Smeele

  • Avatar
    Rob Arends

    Me too, Me too - don't hold your breath.

  • Avatar
    James Clayton

    Active-active is the only true resilient way of doing this where 2 dge's share the load and in the event of one failing the other picks up the load and still has all the historical data, prov.db and customer scripts.

Please sign in to leave a comment.