Home›Services›Backup & DR Check

Your backups work only if a restore works. Let's find out.

Most teams back up GitLab and their registries. Far fewer have restored them. We take your real backups, restore them into an isolated environment, measure how long it takes and list everything that was missing — before you find out on a bad day.

from $1,200 · fixed price Scope fixed on the first call Production untouched
The problem

Backups run every night. Nobody has tried a full restore.

What we do

Restore GitLab, registries, secrets and storage into an isolated environment.

The result

Real restore times, a gap list and a written runbook.

Is this you?

A common gap

From GitLab's own documentation:1

What we test

We agree the list on day one. Typical scope:

SystemWhat we restore and check
GitLabDatabase and repositories, plus configuration, secrets file and object storage; log in, open projects, run a pipeline
RegistriesHarbor, Nexus or GitLab registries: pull a sample of images and packages after restore
Secrets storeVault or OpenBao snapshot restored and unsealed; read a test secret
Object storageBucket contents and versioning; sample objects compared with the source
IaC stateState files restored and a plan run against them

What you get

Restore result per system

Worked, partly worked or failed — with evidence.

Measured times

How long each restore really took, compared with what you need.

Gap list

Missing files, keys, steps and people, ranked by impact.

Restore runbook

Step-by-step instructions written during the test, ready for the next time.

How it goes

Shown for a typical mid-size setup. Larger platforms take longer; the scope and price are fixed on the first call.

  1. Day 1

    Scope and access

    Agree systems, get access to backups, prepare an isolated environment.

  2. Day 2

    Restore

    Restore each system, test it, time it, write down every step.

  3. Day 3

    Report

    Results, gaps, runbook and a short walk-through.

What we need from you

  • Access to your backups (read-only).
  • An isolated environment for the restore — or we provide a temporary one.
  • The person who knows where keys and configuration are kept.

Not included

  • Fixing the gaps — quoted separately, or included in Open-stack care.
  • Testing application databases outside the platform scope.
from $1,200

Fixed price, agreed on the first call.

What changes the price

  • Number of systems to restore.
  • Data volume — large restores take longer.
  • Environment — yours or a temporary one from us.

Questions teams ask

Will you touch production?

No. We read backups and restore them somewhere else. Production keeps running as usual.

What if the restore fails?

Then the test did its job. You get the exact reason and the fix, while there is still time to apply it.

Can this run regularly?

Yes. A restore test every quarter is part of Open-stack care.

Often done together

When did you last restore GitLab?

If you are not sure, it is time. A 30-minute call is enough to scope the test.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public announcements, documentation and legal texts, for orientation only; not legal advice. GitLab is a trademark of GitLab Inc.
  1. GitLab docs: Back up GitLab
Book a 30-minute call