Order of operation applying hotfix

[gregoryyoung1]

What's the order of operation when applying a hotfix/patch to TES 6.2.1 on Linux server with Fault Tolerance? We have a Primary Master, Client Manager, Backup Master, and Fault Monitor? This environment is new to our team, and we are interested in how to apply hotfixes when the time arises.

[Derrick Au]

Hi Gregory,

Do you have a time maintenance window for applying patches? If Primary Master is active, then you can start by applying the hotfixes for the Backup Master. The Client Manager can be done at any time just check to see if there are any Webservice or Sacmd type of jobs active (in that case, good idea to place them on hold)

• Stop Backup Master, apply hotfix here
• Failover to the Backup Master, and then make sure Tidal is running smoothly (if not, then no need to go any further)
• Stop Primary Master, apply hotfix here
• Failback to the Primary Master, and then make sure Tidal is running smoothly
• Turn off Fault Tolerance, which will result in Primary Master running as a standalone
• Apply hotfix to Fault Monitor
• Apply hotfix to Client Manager

Once done, then re-enable Fault Monitor

If Fault Monitor does not see the Primary Master active, then set system queue = 0, and stop the Primary Master

Start up Primary Master

Start up Backup Master

then the Client Manager

BR,

Derrick Au

[gregoryyoung1]

Derrick,

We do not have a maintenance window at this time as we are still on a single Windows platform and will be moving to the Linux FT platform in a few weeks. We'll have to implement one for the future, and thanks for the order of operation in our environment.

Regards,

Ggregory Young