High Availability Lessons from Disney and Pixar’s Soul

SIOS Background
Reading Time: 6 minutes

In Disney and Pixar’s Soul, the main character Joe Gardner (voiced by Jamie Foxx) has dreamed of being a professional jazz pianist.  However, despite his many attempts, to his mother’s dismay, he finds himself miles away from his dream, living as “a middle-aged middle school band teacher.”  But then, “thanks to a last-minute opportunity to play in jazz legend Dorothea Williams’ quartet, his dreams seem like they are finally about to become a reality.  That is until “a fateful misstep sends him to The Great Before—a place where souls get their interests, personalities, and quirks— and Joe is forced to work with a “22”, an ancient soul with no interest in living on earth, to “somehow return to Earth before it’s too late (D23.com).”

Disney and Pixar’s Soul is a great movie with lots of interesting and relatable characters, humorous, descriptive and sometimes disturbingly relatable takes on life, purpose and living.  But, it is also a movie with rich leadership lessons, life lessons, and lessons on higher availability.

Seven thoughts on Higher availability from Disney and Pixar’s Soul

1. Pay attention to what’s going on

In Disney and Pixar’s Soul Joe lands his dream gig.  But as Joe starts walking and sharing the great news, he is so engaged with his phone that he walks into the street, nearly gets crushed under a ton of bricks, and then he wanders dangerously towards an open, but clearly marked manhole.  So what’s the lesson for higher availability– pay attention.  Pay attention to the alerts and error messages from your monitoring and recovery solutions.  Pay attention to the changes being made by your hosting providers, and especially to critical notices from vendors and partners and security teams.  Alerts and warnings are there for a reason, failing to address them or take the appropriate action when you see the warning could lead you into a deep hole.

2. Don’t fall into a hole

Oblivious to the warnings, or ignoring them, Joe finally meets his end when he falls into an open manhole and becomes a soul.  This immediately alters his dreams and plans.  So, what hole could your enterprise be poised to fall into?  Are there open holes lurking in the path of your enterprise such as: coverage holes, versioning gaps, holes in maintenance plans and reality, or even a black hole with vendor responsiveness?  Look around your environment, what holes could you fall into beyond the obvious single points of failure?  Is there a warning that you have an open hole related to unprotected critical applications, communication gaps between your teams, or even holes in your process and crisis management.  Don’t fall into a hole that could damage or even end your high availability.

3. Don’t rush high availability

After becoming a soul Joe begins actively trying to get back to his own body.  When he gets paired with 22, she takes him to Moonwind who agrees to try to help him find his body, which they do.  But Joe becomes too eager to jump back into his body, despite Moonwind’s caution.  In his rush both he and 22 fall back to earth, but Joe ends up in the body of a cat and 22 ends up in his body.  Like Joe if we aren’t patient, the jump happens too soon and we end up in a precarious or even worse situation.  We may not be in the body of a cat, but we may also be far from the best position necessary to maintain HA.  Jumping too soon looks like:

  1. Deploying software without an architecture or holistic solution
  2. Deploying in production without testing in QA
  3. Deploying into the cloud without understanding the cloud or what the cloud means by HA
  4. Deploying into production based on a timeline and not completed acceptance tests
  5. Deploying without a purpose built, commercial grade solution for application monitoring and orchestration

4. Don’t quit too soon – high availability is never easy

When Connie, a young trombone player, comes to the apartment of her teacher she is frustrated and wants to quit.  She begins by telling Joe (who is actually 22 in Joe’s body) that she’s frustrated and that she just wants to give up and quit.  But after a few moments, she plays one last piece on the trombone and realizes that it is too soon to quit.  In higher availability, we are all a lot like Connie. Sometimes, a difficulty makes us feel like we are at the end of our rope and want to quit.  Sometimes an outage will make us feel certain that it’s time to throw in the towel. Don’t be so quick to quit.  HA is never easy, never!  But, it is always too soon to quit striving to end downtime, so like Connie, maybe we just need to keep at it.  Which leads me to the next lesson.

5. You haven’t tried everything

In the movie 22 is a soul who hasn’t lived yet.  She believes that she has tried all the possible things to give her a spark, but when she falls into Joe’s body she realizes there is a lot that she hasn’t tried.  In creating a higher availability solution, it can be easy to feel like you’ve tried everything and every product, but most likely you haven’t.  A fresh perspective, or looking at the challenges and problems with a new set of eyes may help you improve your system and enterprise availability.

Some things to try for higher availability can be simple, such as:

  1. Set up additional alerts for key monitoring metrics
  2. Add analytics.
  3. Perform regular maintenance (patches, updates, security fixes)
  4. Document your processes
  5. Document your operational playbook
  6. Improve your lines of communication
  7. Perform regular maintenance

Other ideas may require more work, research, time and money but could be worth it if you haven’t explored them in the past.

Ways to improve your higher availability with more time and effort include:

  1. Remove hacks and workarounds.
  2. Create solid repeatable solution architectures
  3. Go commercial and purpose built
  4. Hire a consultant
  5. Audit and document your architecture
  6. Upsize your VM; CPU, memory, and IOPs
  7. Add additional redundancy at the zone or region level

6. Ask more (and better) questions

After Joe, as Mr. Mittens, accidentally cuts a path down the middle of his hair, Mr. Mittens and Joe have to take a trip to see Dez, Joe’s barber.  While Joe is in the barbers chair with Dez they begin having a conversation about purpose, life, existential existence and more.  After the haircut, 22 asks Dez why they never had conversations like this before, about Dez’s life.  Dez responds that he’d never asked before.  Sometimes we can get so tunnel focused in solutions, in methods for the cloud or on-premise, in languages and architectures, and in telling others what we are doing that we forget to ask questions that can open up a whole new world.  As Joe asked questions he learned more about Dez, and about himself.  Perhaps the lesson for better HA is to start asking more questions about our solution, about the architecture, about the business goals and challenges, about the end customer goals, about our teams, and even about our roles and responsibilities within the bigger picture.

Some simple questions to increase our availability include:

  1. If a disaster happens tomorrow, what system, process, product, or solution would be the cause?
  2. What is the single most important thing to protect?  Application, data, metadata, all of the above?
  3. What RPO can our applications and databases tolerate?
  4. What won’t our customers tolerate?
  5. What am I missing?
  6. Where do we have this architecture documented?
  7. What don’t I understand?

7. Perseverance pays off

“The counts off,” says Terry.  Tasked with keeping track of the entrants to The Great Beyond, Terry is meticulously counting the number of souls that should be arriving or have arrived.  After Joe takes a detour to The Great Before, Terry grows determined to find the missing soul and fix the tally. When he begins his work, he is in a long corridor of file cabinets that stretch as far and as high as the eye can see.  But after a while, he finds the file of Joe and discovers that Joe has found a loophole and that is why the count was off.  The same perseverance displayed by Terry will also pay off in the realm of higher availability.  In the face of a daunting uncertainty, a plethora of log files, and an ocean of possible failure scenarios the moments of perseverance to uncover and then remedy problems before they occur, or analyze and remediate them effectively after they occur will lead us to the better outcomes we desire.  Similarly, a lack of diligence and perseverance will mean that the same problem will likely resurface later, even in a new environment with new software.

As the movie Soul ends, Joe returns to the Great Before, finds and then convinces 22 to take her Earth pass and take the plunge.  Reminiscent of when she fell to earth with Joe, she takes another plunge.  To the dismay of my children, the movie ends without describing what 22 makes of her life or the new opportunities that follow.  She simply leaps from the Great Before with an anticipation of what will happen next.  Perhaps we too stand at a moment where we can take the plunge… a moment in the “Great Before” and an opportunity to make this a year of additional higher availability.

– Cassius Rhue, VP Customer Experience

Recent Posts

SIOS Background

The Challenges of Using Amazon EBS Multi-Attach for Microsoft Failover Clusters

Overview of Amazon EBS and Microsoft Failover Clusters  Amazon EBS Multi-Attach volumes and Microsoft Failover Clusters are powerful tools in the world of […]

Read More

Build High Availability with a HANA 3-Node HSR Cluster in AWS Using SIOS LifeKeeper

Introduction: How to Ensure HA and DR in Your Database Creating a highly available SAP HANA environment in AWS is a critical task […]

Read More

How Manufacturers Can Use Failover Clustering to Avoid Downtime

In manufacturing, ERP systems and databases like SAP, SAP HANA, Oracle Database, and SQL Server manage various processes throughout their operations. One of […]

Read More