Disaster Recovery 101 - Learn how to define what “Disaster” means to the company, how to avoid it as much as possible, and how to get things “backup” (pun intended) and running when something goes wrong!
Quorum provides instant recovery of data, applications, and servers from any type of disaster, helping businesses safeguard their revenue, customers and reputation. The award-winning Quorum appliance and hybrid cloud solutions (disaster recovery as a service, or DRaaS) allow mid-market companies to recover within minutes. As operations continue in recovery mode, Quorum is unique in ensuring your business remains compliant to standards like PCI, HIPAA, SOX, and others. Most importantly, Quorum is simple and cost-effective. If your company avoids just 30 minutes of downtime, the Quorum solution pays for itself. Visit www.quorum.net for more information.
TornadosFloodsElectrical stormsFiresEarthquakesTsunamisBlizzardsA tree falling through the roofSolar flaresSpace rocks hitting a communications satellite..Squirrels Attack!!! chewing through the lines1994 - Asquirrel chewed through an electric company’s power line, leading to a 34-minute interruption when the exchange’s own backup power system in Trumbull failed to kick in. “No one is yet ready to describe the recent problems as anything more than a run of bad luck,” The New York Times wrote at the time.1987 - a stray squirrel touched off a power failure in Trumbull, Conn., that shut down the Nasdaq for 82 minutes, preventing an estimated 20 million shares from being traded.
FiresHackers sabotaging RansomwareHuman accidentsIntern deleting data - clickphysical accidenta ship dragging an anchor through a cableSomeone clicking on a malicious link Car driving through a telephone pole
DR = processes & procedures to keep IT systems running on after an incident:Data integrity and availabilityNetworkConnectivity (LAN, WAN) - remote connectivityVoice / video communicationsApplication and server uptimeBackup Power supplies & generatorsIt’s often said that disaster recovery is not planning for IF a disaster will occur, it’s planning for when it will occur
All sorts of templates available in the Spiceworks communityhttp://community.spiceworks.com/storage/disaster-recovery-planningData Network VoiceServersPower Phone treeEvent triggers and responsesEmergency response teamEmployee contact / Family ContactMedia contactLegal actionsInsuranceWebsite Call centerInsurances
LAN, WAN, power, voice, remote connectivity, redundant servers backups, security audits, regular antivirus updates, surge protectors / power backups, redundant serversto fail over to, regularly testing backup systems, accounting for standard failure rates, having a plan B and CNetwork & systems management monitoring tools, event logging & reporting, trigger based alerts, storage monitoring, database monitoring, smoke alarms, etcImplementing plan B - restoring backups, actually failing over to redundant systems, firing up power generators, connecting backup communications systems, contacting fire departments, vendors for support…
Back up with recovery in mindBackup is useless without the ability to recover… test your backups. Practice restoring backups Shorter your time to recovery – more expensiveFull backup or incrementalBackup AutomationRestoring from tape slowest – down for daysRemovable disks are fasterNetwork attached disks even fasterFailover should be near instant
Photo lab with10 retail stores and the main printlab we learned it’s important to have a backup generator. We were prepared this week. We have a primary and secondary battery backups in place (APC Smart-UPS 3000 RM XL) that will sustain power to our 20 servers for almost 9 hours. This gives us enough time to safely shutdown anything non-essential and re-direct power to a generator. We haven’t needed it yet, but redundancy is always important. It may be an additional price to pay, but when it saves you in the time of need, it was well worth the investment. Our SAN is replicated to another storage device in the event that it fails. We don’t virtualize anything yet, and the current setup is failing in more ways than one. We are currently planning on implementing a virtualized solution that would ultimately make disaster preparedness much easier and almost 100% automated. Actions are already underway to ensure there is an off-site location to collect our FTP orders. The network was set up long ago by my predecessor and it’s not up to par with today's standards. My goal is to have our domain network attached to an actual domain. This will allow us to change the FTP IP address to the domain name. This means that we can setup our DNS records to point to our physical location during normal operations, and will redirect to our "hosted" solution in the event of outages. That way it will appear to our customers we are still online.This process is called “Mitigation.” We look at what can go wrong, and minimize the effects. Backups are part of this process, and we need to take a good look there and determine just what information we really need to keep. The old advice was back everything up. Now VM backups make this really easy to do, but since not all software is created equally, we need to make sure that first we know what we’re backing up, and most importantly, can we actually do a restore if we need to. This process usually involves close monitoring of your backups, and then doing occasional practice restores.The “Planning” side of the house is actually writing it all down. I like step-by-step instructions, usually with lots of pictures. When you write it down, do so in 4th grade English. These things always seem to happen at 3 AM when your brain is tired, you’re under the gun, and the last thing you need to do is try to figure out what you meant eight months before. Best advice here, practice your plan. The wrong time to find out if it’s going to work for you is when you need it.
Business ContinueityIncludes Disaster Recoveryand more considerations.Staff illnessDeparture of key staffersSupply chain problems (what if you run a factory)Water, natural gasNon IT related Machinery / equipment (trucks, factory machines)Etc…Governments have business continuity plans – President, VP, Speaker of the House, President pro temp of the senate, secretary of state, secretary of tresasury, secretary of defense, attorney general, etc
Spiceworks Disaster Recovery – Avoid IT Apocalypse!
Protect Against IT
Network Newbie III - Backup & Disaster Recovery
Peter Tsai, Spiceworks IT Content Guy
Presented by Spiceworks
Protect Against IT Apocalypse!
What is Disaster Recovery?
What’s in a DR Plan?
Something Broke – Fix it!
With Special Guest:
Nigel Hickey (AKA DJ Whiplash)
System Administrator - Houston, Texas
17+ years in IT
VCP5-DCV, VCA [DCV|WM|Cloud]
Disasters… it’s not
a matter of IF….
What’s in a Disaster Recovery Plan?
What “disaster” means
How to circumvent disaster
How to fix things after a disaster
List of potential disasters in order
of risk, impact, probability, cost
What’s in a Disaster Recovery Plan?
1. Preventive measures
2. Detective measures
3. Corrective measures
Disaster Recovery - Backup Strategy
Tape, SAN, NAS, removable disk
On-site, off-site, cloud, hybrid
Failover (High Availability)
Time to Recovery