DR Failover Steps

[Nate Kruse]

Good afternoon,

We just completed a successful practice failback (the failover was a little rougher) from DR to our PRD server.

In doing so, we typically like to keep Cloverleaf as clean/empty of messages as possible. So we have a process that three people on our team stop all inbound threads and once cleared, then all outbound threads. This can be a little time-consuming over 12 sites. Why do you only have three people doing this? Good question. We have found that too many people doing this seems to cause the GUI to freeze and was more of a hindrance on performance.

My question is…What is your high-level process for shutting down Cloverleaf in the event of a DR Failover drill? Of course, a real DR Failover wouldn’t allow such preparation. A topic we run into with departments is trying to shutdown the non-essential interfaces first while keeping the essentials going as long as possible.

Thank you in advance.

Nate K

Topic

[Mark Thompson]

Nate,

One of the things I really like about Cloverleaf is that you can still do pretty much anything from a command line.  That means you can get as creative as you want with scripts like STOP_ALL_INCOMING_THREADS and STOP_ALL_SITES.  (I tend to use ALL CAPS for script names like these to discourage running them inadvertantly in production.)

- Mark Thompson
HealthPartners

[Author]

Replies