Backing up isn’t enough. You need to be able to restart.
CERVOX Jour Zéro, our IT recovery test, shows within a defined scope what you can actually restore, how long it takes and what gets in the way — before an incident forces the question.
- Restored in an environment kept separate from production
- Dated, documented results
- You set the objectives
You have backups. Whether you can restart is another question.
A backup proves that a copy exists. It doesn’t tell you whether your systems will come back, or how long that will take.
A copy you can’t use
It exists, but it’s incomplete, too old, or hit at the same time as your systems. You find out when you try to restore.
A restart order nobody wrote down
Your applications depend on the network, the directory, a database. In the wrong order, nothing comes back.
A missing access or a missing person
The admin account lives on the server that’s down; only one person knows the procedure.
A recovery test turns these unknowns into findings.
Check in 5 questionsCERVOX Jour Zéro, the IT recovery test
We restore your essential systems in an environment kept separate from production, measure how long it takes before they are usable again, and document what blocks recovery.
Five questions the test answers
- What can you actually restore?
- Under what conditions is recovery possible?
- How long does it take, within the tested scope?
- Which prerequisites, dependencies or blockers stand in the way?
- Which actions would improve your ability to recover the most?
Understand, test, document, improve, keep on track
- Understand: where you stand, in 10 questions (free self-assessment).
- Test: what actually restarts (CERVOX Jour Zéro).
- Document: a dated record of results, gaps and limits (test report).
- Improve: fix things in the right order and organise recovery (priority actions, DRP, BCP).
- Keep on track: keep that readiness current as your systems change (Copilot PRA, periodic tests).
Questionnaire, test or tracking: what each one tells you
| Self-assessment | CERVOX Jour Zéro | Copilot PRA | |
|---|---|---|---|
| What it is | 10 free online questions | A documented recovery test, within a defined scope | Software that helps you prepare for recovery, between tests |
| What you learn | What to look into and where to start | What restarts, how long it takes, what blocks it | The gaps that could block recovery |
| What it relies on | Your answers | A real, timed restore | Analysis of your configurations |
| What it isn’t | Not a test, not proof | Not a fix, not a certification | Not a recovery test, not a guarantee |
| Action | Take the self-assessment | Request a test | Discover Copilot PRA |
DRP and BCP: who does what, during and after the outage
- A disaster recovery plan (DRP) brings your systems back in the planned order, with procedures your team can follow under pressure.
- A business continuity plan (BCP) keeps essential work going during the outage: fallback modes, backup communication, delegated authority.
Not every business needs a BCP. And a plan that has never been run is still just an intention.
DRP vs BCP explainedCopilot PRA: stay ready between tests
Your infrastructure keeps changing. Between tests, Copilot PRA, our recovery-readiness software, helps spot the configuration gaps that could block recovery. It prepares your tests; it doesn’t replace them.
Discover Copilot PRAWho it’s for
Business leaders
Know how long the business would be down, and decide what’s acceptable.
CERVOX Jour ZéroIT directors and IT managers
Move from stated confidence to measured capability, with results you can show leadership.
CERVOX Jour ZéroFinance and risk
Base your assessment of outage risk on observed durations, not assumptions.
CERVOX Jour ZéroIT service providers
Prepare your clients’ recovery tests by spotting early the gaps that could block them.
Copilot PRASupplier questionnaires and tenders
Answer with dated results, not statements.
Answer a customer or tenderM&A and fundraising
Make recovery capability visible in due diligence, with written consent from the company reviewed.
Make a requestHow we work
- Nothing is done on your production: the restore happens in a separate environment, following a test plan you approve in writing.
- Named, temporary access, limited to the agreed scope, which you create and remove.
- Where the method calls for it, the deletion of the temporary environment is recorded in a written deletion record.
- If CERVOX carries out fixes, the report says so, and another engineer runs the retest where feasible.
What we don’t promise
- Guaranteed recovery or a guaranteed recovery time: we report what works within the tested scope.
- Certification, or compliance with a standard or regulation.
- Lower insurance premiums, or success in a tender, audit or sale.
- That a questionnaire or an alert proves a system will restart: only a test shows that.
You get dated results, their scope and their limits. The decisions remain yours.
FAQ
Our IT provider already handles backups. Why test?
Your provider runs your backups day to day. The test answers a different question: will your systems restart, and how long will it take? It brings a separate technical perspective. You keep your provider, who can take part in the test.
Do you touch our production systems?
No. The restore happens in an environment kept separate from production, following a test plan you approve in writing.
Can the test be done remotely?
Yes, when the environment and access allow it. Where and how the restore happens is agreed during scoping, depending on your environment.
What if the test fails?
That’s exactly what you want to learn before an incident. The report documents what blocked recovery and the priority actions. Nothing is fixed without your decision.
Is this a certification?
No. You get dated results, their scope and their limits. They can support an audit or a questionnaire, without replacing an auditor or a certification body.
How long does it take and what does it cost?
It depends on the scope. After a first conversation, we send you a written proposal.
Find out before you have to restart
Tell us about your situation in a few lines. We’ll suggest a test scope that fits.