We are very familiar with both types of plans, we know the process and profiles and can consult and assist your organization.
And it’s considered a subset of business continuity, but it’s a little different than business continuity. Number one, IT systems in data increasingly is critical to companies and, I would submit, countries. So once this happens, all the important players need to be notified so action can begin to be taken.
Also the demand for a rapid recovery is increasing. So research from 2015 shows that companies with a major loss of data 43% never were able to recover and reopen, 29% closed within two years. So we’re talking about backing up data and systems, we’re talking about once we back it up, on a periodic basis, we have to test it to make sure that that approach and everything works. Also understanding the scope of what the recovery looks like, and the disaster recovery teams, and responsibilities.
Disasters happen, Jennifer said, but recovery must be planned.
Just like any plan, a disaster recovery plan is made up of pieces.
Jennifer outlined what a disaster recovery plan is and what it should consist of: Why do you care?
Because, at a high level, a disaster recovery plan is helping to backup data systems on a regular basis to avoid loss and testing to make sure these procedures are running as planned.
Also from 2018, there’s an article, “The importance of disaster recovery,” and it suggests that downtime lasting for an hour can cost a small company approximately ,000, a mid-sized company around ,000, and a large company up to 0,000. Then when an event occurs, we have to recover and then we have to rebuild. So what are some of the things we need to consider? So when it is invoked, every member on the team needs to know specifically what they’re responsible for, so they can take action. We also need an inventory of all the IT systems that may be impacted as well as the network equipment.
So first of all, if an event occurs, if a disaster occurs, who is the emergency contact? Also, it’s important to know who is the disaster recovery lead, because they are actually leading this effort to the recovery. They are responsible for keeping the approaches, the processes, and all of this up to date. So when we talk about data and we talk about backups, we also want to know what is the frequency? So this can be very expensive and this can be very detailed. Number two, review the whole process on a regular basis to ensure that it’s up to date.
We also need to know the network team, the server team, applications team, and the data and backup recovery team. Depending upon some data, some data is backed up continually real time. Then we need to know the restoring, the IT functionality. So this is just a high level look at all the aspects that we need to consider. And number three, backup and then confirm that the backups did work properly.
So they’re capturing the data and they’re backing up real time. So if you need a tool that can help you with your disaster recovery plan, then sign up for our software now at Project