Skip to content

Resgrid Blog

Resgrid Blog

Resgrid.com Blog | Open Source Dispatch

Resgrid Disaster Recovery

August 31, 2021 by Resgrid Team

In the specter of the Caldor Fire we’ve been hard at work with Resgrid’s backend and resilient systems. We have some redundancy plans in place but with a major event we felt it necessary to step up our efforts and ensure that Resgrid is always available.

Although we have some really cool feature we are working on, Push to Talk and Invoicing, we are halting work on those right now to ensure our platform can recovery from a major event within a reasonable amount of time.

So what are we doing? First we did some evaluations of Cloud Platforms to see where it makes sense for us to house our backup infrastructure and we decided on Linode (https://www.linode.com/). Resgrid originally started as a Microsoft Azure hosted service, but after opening up our source code and trying to ensure our hosted environment matches what people can deploy locally we have to avoid vendor lock in at all costs.

Linode has long hosted some of our other backend services and we’ve never had any issue with their platform and it offers a great Price to Performance ratio. Our backup provider will be Digital Ocean as we have used them a ton in the past (our Url Shortner and original Status Page were hosted there) but they have some restrictions on sending email’s that could impact us.

What does this mean for you? Well, nothing changes. We will be working on this for the next little bit and there will be some downtime that we will have to schedule. You can see when we have that downtime scheduled on our status page (https://resgrid.freshstatus.io/). This will be us moving our active hosting to the backup hosted to simulate a Disaster Recovery event and have it running there for a set period of time (probably a couple of weeks), at which time there will be scheduled downtime to migrate back.

Why would we move our active running instance to our DR site? Well, just having an Disaster Recovery plan doesn’t mean much if your not exercising it. This will allow us to verify the process and operations and also allows us to perform maintenance on our main Data Center. We have 2 very large servers (Canterbury and Donnager) that host Resgrid in an active-active fashion, we want to upgrade the RAM in both, and during the DR testing that gives us a great time to perform that.

Post navigation

Previous Post:

Announcing Resgrid Dispatch

Next Post:

Major API and Unit App Update

Leave a Reply Cancel reply

You must be logged in to post a comment.

Recent Posts

  • How to Create Standard Operating Procedures | Step-by-Step Guide
  • 8 Essential Crisis Communication Strategies for 2025
  • Top Incident Management Best Practices to Improve Response
  • Resgrid’s NextGen Apps
  • A New Year, a New Resgrid

Links

  • Resgrid Open Source Dispatch
  • LinkedIn
  • Resgrid Github
  • Resgrid Docs

Archives

  • September 2025
  • July 2025
  • January 2024
  • September 2023
  • July 2023
  • November 2022
  • December 2021
  • November 2021
  • August 2021
  • April 2021
  • March 2021
  • December 2020
  • November 2020
  • September 2020
  • August 2020
  • July 2018
  • January 2016
  • October 2015
  • September 2015
  • May 2015
  • January 2015
  • December 2014
  • October 2014
  • June 2014
  • April 2014
  • September 2013
  • March 2013
  • February 2013
  • July 2012

Categories

  • Announcements
  • Articles
  • Engineering
  • Guides
  • Resgrid System
  • Responder App
  • Uncategorized
  • Unit App

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
© 2025 Resgrid Blog | WordPress Theme by Superbthemes