For Immediate Support Call: 713-783-6453
Copyright© 2023

Disaster Recovery Planning - Most IT guys miss too many of these things.

Only consider what you haven't thought of or already have, but plan for the absolute worst scenario and work your way down from there.
Facility I (square footage)
Facility II (furniture)
Infrastructure I (cabling and availability / delivery timelines)
Infrastructure II (switches routers and availability / delivery timelines)
Infrastructure III (Internet Service Provider and availability / delivery timelines)
Infrastructure IV (Phone lines and availability / delivery timelines)
Infrastructure V (Functioning cell phones and availability / delivery timelines)
Equipment (Computer / Server / Software and availability / delivery timelines)
Installation times (Technician availability / installation times)

All the above products priority placement on personnel's priority.

Perfect scenario I (Only your business had the disaster)
Facility I (next day - week)
Facility II (same day)
Infrastructure I (same day)
Infrastructure II (same day - next day)
Infrastructure III (2 days - 45 days)
Infrastructure IV (2 days - 1 week)
Infrastructure V (same day - next day)
Equipment (same day for compromised local hardware or 7 - 10 days for ordered equipment)
Installation times (same day to 3 days for data recovery)
If you were to overlap the tasks then 2 days for minimum start to function to 45 days for full functionality

Semi-perfect scenario II (localized disaster area wide)
Facility I (days - weeks)
Facility II (days - multidays)
Infrastructure I (days - multidays)
Infrastructure II (days - multidays)
Infrastructure III (multidays - 45+ days)
Infrastructure IV (multidays - 1 week)
Infrastructure V (days - multidays)
Equipment (multidays for compromised local hardware or 7 - 10 days for ordered equipment)
Installation times (same day to 3 days for data recovery)
People (did you lose key personnel to death or permanent relocation?)
If you were to overlap the tasks then multiple days for minimum start to function to 45+ days for full functionality

Total meltdown scenario III (disaster city / state / nation area wide)
Facility I (weeks - months)
Facility II (weeks - months)
Infrastructure I (weeks - months)
Infrastructure II (weeks - months)
Infrastructure III (multiple weeks - multiple months)
Infrastructure IV (weeks - months)
Infrastructure V (weeks - months)
Equipment (weeks - months)
Installation times (weeks - months)
People (did you lose key personnel to death or permanent relocation?)
If you were to overlap the tasks then multiple weeks for minimum start to function to multiple months for full functionality

Real stats for Small Businesses 2 to 50 computers
8 - 12 hours to get the server right
1 hour per computer average to get computer right (minimum 5 hours for 5 computers and under because it takes 2.5 hours per computer consecutively)
You can back up your server in an average of 9-19GB per hour on a typical server, but it takes 4.5-9GB per hour to restore that data.
Typical small business servers we deploy average 9GB - 160GB of data.
This means 2 hours to 36 hour to recover with an average recovery time of 12-16 hours to get data right.

What can you do to help minimize recovery times?
Have contacts listed ahead of time for all vendors all in town and out of town alternate vendors.
Do multiple backups regularly (onsite and offsite backups)
Use services like Iron Mountain to be scheduled to come by weekly/daily to pickup/rotate a tub of business essentials to be taken offsite.
Copy all of your CD's and store the originals or in a fireproof and waterproof container and have checkout policies for those CD's.
Copy all of your original serial numbers and certificates of authenticity and store the originals offsite or in a fireproof and waterproof container. Make sure you know that MANY MANY MANY MANY MANY serial numbers and product key codes ARE NOT TRANSFERRABLE to other servers and workstation computers. You will have to purchase them again if you have retail copies or open license agreements with Micrsoft. Open Value agreements DO have transferrable licenses and product key codes and they are stored at Microsoft for the length of your contract.
In that fireproof/waterproof safe don't forget to have the maximum contact list for both your employees as well as your customers. You can't have one without the other.
Keep your insurance carriers contact information in that safe as well.
Video document as much as you can and describe what you are looking at if you have to flash evacuate in a hurry.
Come up with a timeline of how long it takes to do things. Your business may have started small and grew to where it is today. So, although you may have thought you knew how long it took to do certain tasks, you may not have done them from scratch at the current scale.
Consider storing your servers at a Data Center facility in a colocated facility or in a managed services area. VeriCenter / CyrusOne / Level3 are a few Data Center options with locations nationwide.
Know your hourly losses to help you decide the level of protection you need.
So what if your company has insurance on the computer equipment that cost you $50K. If you are losing $10-$20K per day, you could have saved your company from losing more in revenue if you had a well planned, well thought-out single day of revenue set aside for rapid recovery and knew it ahead of time. They say hind sight is 20/20. I say use your 20/20 now and do it in an organized realistic cost perspective of "what-if".
Even a minor disaster call literally kill a business if your data is not backed up. Lose your data and lose your business.

p.s. keep the contact number for your fireproof/waterproof safe in your wallet, because that's where it all begins.

£ouis