If your server room has just gone dark, the first 60 minutes go to keeping people safe, finding out whether the cause is power or water, and deciding whether to switch work to your backup systems.
The rest of the company still has work to do while IT restores the hardware. Billing, HR, and customer service can only keep going if they can reach their records, and at many companies those records are on the same servers that just went down.
This checklist covers the first hour of server room disaster recovery step by step, along with the planning that keeps everyone else working until the systems come back.
Disaster Recovery First Steps for the First 10 Minutes
Confirm the outage is real, and make sure nobody is in danger. Find out whether it’s building-wide or limited to the server room, and whether anyone on site reports water, smoke, or alarms.
Then work through these in order:
- Keep people out of standing water near electrical equipment. The Centers for Disease Control and Prevention (CDC) advises calling an electrician if you’d have to wade in to reach the main power switch, and never switching power on or off while standing in water.
- Call the person your plan names to declare a disaster. That formal call activates the recovery plan, so start a timestamped log of every action and decision from that point on.
- Notify the incident team and the outside contacts on your list, such as the building manager and the utility.
- Hold off on restarting equipment or swapping hardware until you know the cause. Re-energizing a tripped circuit or wet equipment too soon can damage hardware or create a shock hazard.
The CDC’s flood safety guidance is written for homes, and a server room adds one hazard a house doesn’t have: an uninterruptible power supply (UPS) can keep circuits live after the main power is off. Treat equipment near water as energized until an electrician says otherwise.
If your plan doesn’t name who makes the disaster call, make that your first fix once the lights are back on. It’s one of the recovery planning basics teams tend to skip until the night they need it.
Server Room Flood or Power Outage? Diagnose the Cause
Minutes 10 through 30 go to diagnosis, and power is a good first guess. Uptime Institute’s 2026 outage analysis found that power remains the leading cause of impactful data center outages, with failures involving UPS systems, transfer switches (which move the load from utility power to a generator), and generators dominating.
A UPS is a battery system that keeps equipment running through a short interruption. Its runtime is typically measured in minutes, which is long enough to start a backup generator or shut systems down properly, but not long enough to ride out an extended utility outage.
When the UPS is alarming or drained and the generator never picked up the load, you’re looking at a power event. Check the breaker panel, the box of switches that feeds each circuit, for a tripped main. Don’t reset it until someone qualified knows why it tripped, and leave it to an electrician entirely if there’s any sign of water nearby.
Water leaves different evidence: leak-detection alerts, wet floor tiles, drips from ceiling pipes or cooling lines, or a sprinkler discharge. A flood changes the order of operations. Nobody touches equipment until an electrician has made the room safe, and wet hardware stays off until it’s completely dry and checked.
Fail Over or Wait It Out?
By the end of the first hour, you need a failover decision. Failing over means switching work to backup systems, often at a second site, and failing back means returning to the primary systems once they’re repaired.
Under the National Institute of Standards and Technology’s definition, your recovery time objective (RTO) is how long a system can stay down before the outage starts hurting the business. If the utility’s restoration estimate or the flood cleanup will run past your RTO, start failing over early enough to finish inside it. When power is likely back well within that window, waiting can cost less than failing over now and failing back later.
Business Continuity First 24 Hours: Who Keeps Working
Disaster recovery restores systems, data, and hardware. Business continuity keeps the business operating while that happens.
Ready.gov’s IT disaster recovery guidance says to develop the two plans together. It calls for setting recovery time objectives during a business impact analysis, which estimates what a disruption would cost each part of the business, and documenting the IT recovery plan as part of the business continuity plan.
Business continuity in the first 24 hours comes down to whether your team can reach the records it needs. If contracts, invoices, personnel files, and customer histories sit only on the file server in that dark room, everyone waits on IT.
If a provider had already scanned those records into a cloud-based document management system (software that stores, indexes, and controls access to digital files), the picture would look different. Accounts payable could still pay vendors, HR could still answer a benefits question, and customer service could still pull an account history.
The stakes vary by sector. A law firm’s court deadlines don’t move because its server room flooded, and an insurance agency still has claims files that customers are waiting on.
The Disaster Recovery First Steps Everyone Skips
Recovery plans usually cover the servers and leave out the paper. That gap means the benefits of a disaster recovery plan stop at the IT department, while everyone who works from paper files waits.
Ready.gov’s data backup guidance addresses it directly, noting that vital records, the documents a business can’t operate without, can be backed up by scanning paper copies into digital formats. The same guidance asks you to define a recovery point objective (RPO), the point in time your data has to be recoverable to after an outage.
A filing cabinet has no recovery point at all. If a pipe bursts over it, the only copy is the one that just got wet.
A few other gaps tend to show up during an outage:
- No vital records list. Nobody wrote down which documents the business can’t go a single day without, such as active contracts, payroll records, licenses, and insurance policies.
- Backups in the same building. Backup tapes or drives stored beside the servers can share the same flood, so any small business backup strategy should send at least one copy offsite. Providers in our network keep tapes in climate-controlled offsite tape and microfilm storage, and a backup tape rotation scheme decides which tapes leave the building and when.
- An untested plan. A plan nobody has rehearsed usually fails at the handoffs, like who calls the utility and who tells staff where to work in the morning.
Business Continuity First 24 Hours Starts with Scanning
Consider a company that had its working files digitized the year before. When its server room goes dark at 2 a.m., IT still has a long night ahead, with a vendor on the phone and a step-by-step recovery runbook open.
At 9 a.m., the office opens anyway. Staff work from laptops at home or in a borrowed conference room, pulling files from cloud storage in a data center hundreds of miles from the dark server room.
The office can open because, months earlier, a provider in our network scanned and indexed the paper files and loaded them into a document management system with access permissions matched to the office’s own.
Because the IT manager pushed for that project, the outage stays an IT problem. Providers in our network digitize and host records for businesses in cities like Columbus, OH, and Portland, OR.
FAQs on Disaster Recovery
Confirm the outage and make sure no one is in danger, and keep everyone away from electrical equipment if there’s any chance of water. Then call the person your plan names to declare a disaster, and start a timestamped log.
The person your disaster recovery plan names, often the IT director or an executive with authority to approve failover costs. Name a backup as well, since outages rarely wait for business hours.
Recovery is about getting systems, data, and hardware back. Continuity covers the people and processes that have to keep going in the meantime, including access to the records they need to do their jobs.
A safety check, outage confirmation, a disaster declaration, a timestamped log, notifications, a diagnosis of the cause, and a failover decision measured against your RTO. It should also say where staff will find the records they need that day, which many checklists leave out.
Run the manual workarounds your continuity plan documents, and give staff access to the records those workarounds depend on. Records your provider has scanned and now hosts offsite keep that work moving, which is one reason they belong in your broader data protection strategy.
How We Help You Keep Records Within Reach
Record Nations connects you with certified, vetted providers who digitize paper records and host them in cloud records storage that doesn’t depend on your own server room. For the providers handling your paper, look for PRISM Privacy+, the records and information management certification from the International Secure Information Governance & Management Association (i-SIGMA), along with its imaging and digitization endorsement for scanning work. Record Nations is an i-SIGMA member.
Fill out our form or call (866) 385-3706 to get free quotes. We’ll help you scope which records to digitize first and find competitive pricing from providers near you.
