ITDrill is an independent reference site about one narrow subject: finding out whether an IT recovery would actually work before the day it has to. It publishes method, worked examples and a planning worksheet for people who own recovery outcomes: IT managers, infrastructure and backup engineers, and the continuity or risk stakeholders who depend on them.
What the site is
The material covers how to design and run recovery drills, how to test that backups can be restored, how to set and check recovery time and recovery point objectives, how to write runbooks another person can follow, and how to run tabletop exercises and review the results. The articles are written as practitioner explanations: they include commands, records and arithmetic you can adapt, and they say where a detail depends on your product or version so that you verify it rather than trust it.
The drill planner is a rule-based worksheet. You describe your situation, and it proposes a first exercise, a scenario, roles, success criteria and the evidence to capture, with the reasoning shown. Everything runs in your browser.
What the site is not
ITDrill does not run drills, restore backups, monitor systems, scan networks or audit anyone’s environment. It has not tested, and cannot tell you anything about, your infrastructure. Nothing it produces is a certified recovery plan, and the planner’s output is not an audited recovery time or recovery point. It is not a backup service, a managed recovery service or a consultancy with a published offering. If a statement on this site sounds as though one of those things has happened to you, that is a defect in the site, and it should be reported once a way to report it is open (see the contact page; none is open yet).
How to read it
Treat each article as a method to adapt, not a standard to comply with. Where the articles suggest frequencies or targets, they are starting points that should change with your systems, your obligations and what your first drills reveal. Where they cite external guidance, such as NIST publications on exercise programmes, they name it so you can read the source yourself.
Recovery guidance that is wrong can do real harm, so accuracy is treated as more important than coverage. The site would rather publish fewer articles than thin or speculative ones. If you find an error, a command that is unsafe as written, or a claim that is not supported, the contact page will list a way to report it once a channel is open. No channel is open yet, and the site cannot receive corrections until one is.
Where to start
New to the subject: read designing a recovery drill, then restore testing. Already running restores and asked for numbers: RTO and RPO. Looking for everything in one place: the resource index.