Field notes · Jaen Baldwin
Ask what a recovery would actually require.
I would rather discover a missing account or an untested restore during a planned review than while the business is waiting to reopen. A recovery discussion needs more detail than a green backup status.
Which business functions come first?
Identify the applications, data, accounts, and network services behind them. The priority list should come from the business, with the technical dependencies recorded alongside it.
What has actually been restored?
Ask when a usable restoration was last tested and what the test covered. Recovering one file answers a different question from bringing an application and its dependent systems back into service.
Can the recovery team still get access?
Review the administrative accounts, copies, documentation, contacts, and infrastructure needed to restore. Consider what happens if the usual devices or identity system are not available.
Who makes the decisions?
An incident can involve leadership, insurance, legal, forensic specialists, vendors, and IT. Establish the technical roles and authority instead of assuming that everyone will agree in the middle of an outage.
Related services
Have a situation like this?
Tell Jaen what is happening and what your business needs. We can identify the next step without assuming the answer in advance.