Write a restore runbook for a critical system in Commvault
The person who knows how to restore your most important system shouldn't be the only one who can.
- You get
- A step-by-step runbook a second engineer can follow, with checks, timings to record and who to call.
- Works in
- ChatGPT
- Claude
- Copilot
- Gemini
Fill in the blanks
A few words each is enough. Leave a blank empty and the assistant will ask you or assume.
Describe, don't paste: no CUI, personal data, hostnames, IP addresses or credentials. What you type stays on this page until you copy it or open it in an assistant.
Your prompt0 of 6 filled
Act as a Commvault engineer. Write a restore runbook for one critical system, clear enough that an engineer who has never restored it could follow it at 2 am. - System: [System, e.g. ERP running on SQL Server across two VMs] - What it depends on: [Dependencies, e.g. Active Directory, DNS, a file share, a licence server] - What Commvault protects for it: [Backups, e.g. VM backups, SQL database backups, file system] - Where the copies are: [Locations, e.g. on-prem disk, Commvault AirGap, a second site] - Recovery time target: [Target, e.g. 4 hours] - Recovery point target: [Target, e.g. 15 minutes] Structure the runbook as: 1. Before you start: who approves the restore, how to choose a clean recovery point if ransomware is suspected, and what to check is already running. 2. Numbered restore steps in order, including dependencies, with a check after each step. 3. How to confirm the system works: what the application owner should test. 4. What to record: start and finish times, the recovery point used, problems, and who signed off. Describe screens in plain words if you aren't sure of exact menu names in our release. Mark anything you assumed with "(assumed)". Some details above are still in square brackets. Ask me for them before you answer, rather than guessing.
Before you paste
Run the runbook once in a test and fix every step that didn't match. An untested runbook is a draft.
Then check the answer
Recovery Co-Pilot
Rehearse and run recovery with KELYN
More commvault prompts
All 28 prompts- Find why a Commvault backup job failedA Commvault job failed or finished with errors and the failure reason doesn't tell you what to fix.
- Harden your Commvault environment against ransomwareAttackers go after the backup system first, and you want to know how well yours would hold up.
- Plan disaster recovery for the CommServeEvery restore depends on the CommServe, and you need a plan for getting it back first.
- Set Commvault retention to match your records rulesYou need retention settings that meet your records and compliance rules without paying to keep everything forever.
- Plan a Commvault upgradeYou're moving to a newer Commvault release and want a change plan that won't leave you without backups.
- Collect CMMC evidence from CommvaultYour assessment is coming up and you need to show, not say, that your backups meet the 800-171 requirements.
- Turn Commvault reports into a leadership updateYour monthly backup numbers mean something to you and nothing to the people who fund them.
Want a person to check the answer?
AI gets you a first draft. A KELYN engineer can tell you whether it would hold up in an assessment or a real recovery.