Genesys Engage on-premises

 View Only

Discussion Thread View
Back to discussions
Expand all | Collapse all

Windows patches causes restart of Genesys servers. What's the best practice followed in such monthly restarts?

  • 1.  Windows patches causes restart of Genesys servers. What's the best practice followed in such monthly restarts?

    Posted 12-20-2018 10:43
    Hello,

    When there are monthly Microsoft patches to be applied in Genesys servers which requires restart of host post patching. What is the best practice followed in such a scenario, as it is huge process to check the services after the hosts are up and running?

    How is it managed in a huge multi site environments where there are multiple hosts?

    Thank You
    Best Regards,
    Rashid
    #Security

    ------------------------------
    Rashid Yusuf
    BTC Networks Saudi Arabia
    ------------------------------


  • 2.  RE: Windows patches causes restart of Genesys servers. What's the best practice followed in such monthly restarts?

    Posted 01-07-2019 17:04
    ​Rashid,
    Most larger sites have several instances of the Genesys framework; a dev environment, a testing environment and a production environment.
    In addition, some of them have an A side and a B side, indicating the HA nature of server pairs. At one site in particular, we had two production environments at different geographical locations that shared the same agent pool.

    The core principle is to be able to have redundancy for the environment so that you can fail over should a large data-center fail, and to disperse your servers across data centers so that one failure will only affect half of your servers, and the ones that drop out have their HA partner in another data center or location to resume functionality.

    With this set up, you automatically have a set of dark-servers that can be patched in the middle of the day, provided there are no on-going data issues. After successful patching, a night-time fail-over is performed to the patched servers. In the morning, the other half of the environment is patched and you are ready to go for the month.

    This strategy also fine-tunes your fail-over procedures, so that in an emergency, the process is familiar to all parties involved.
    Another benefit is that any failed, inactive servers are identified and re-activated at the next patching cycle.

    ------------------------------
    Todd McCall
    Bank of America
    ------------------------------

    Original Message


Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources