Backup and restore (backup + restore testing)

A backup that has never been tested is just hope. You get a complete backup strategy: automation, encryption, multi-location storage and regular restore testing — so you know your data can be recovered.

The problem

Many companies have no backups at all, or have copies that have never been tested. Common issues: backup stored only on the same server (disk failure = loss of both data and backup), no encryption (data leak if backup is accessed), no rotation (disk fills up, backups stop), no restore procedure (nobody knows how to recover data in a panic after failure). Consequences range from losing a few hours of work to total loss of business data and days of downtime.

Scope of work

Audit of the current backup strategy and gap identification
Implementation of the 3-2-1 strategy: three copies, two media, one copy off-site
Automated database backups (MySQL/PostgreSQL) and application file backups
Backup encryption (GPG/AES) before transfer and storage
Backup rotation: daily, weekly, monthly with configurable retention periods
Regular restore testing with a report – confirming the backup actually works

What you get

Configured and automated backup system with schedule and rotation
Backups stored in at least two locations (server + off-site/cloud)
Restore script and procedure with step-by-step documentation
Periodic restore test (manual or automated) with a report confirming data integrity
Backup monitoring with alerts for errors or delays

Related services

Monitoring and alerts (Grafana/Prometheus/Loki)

Monitoring backup status, alerts for errors and delays – full visibility into the backup process.

DevOps and Linux server administration

Backups are part of a broader server maintenance strategy — combined with monitoring, hardening and CI/CD for complete coverage.

Frequently Asked Questions

What is the 3-2-1 backup strategy?

The 3-2-1 strategy is an industry standard: maintain three copies of your data, on two different media, with one copy off-site (outside the primary server). This ensures that even a server failure, fire or ransomware attack does not result in data loss.

How often do you test backup restoration?

Monthly tests are recommended — automated or manual, depending on the environment complexity. Each test ends with a report confirming data integrity. Under ongoing maintenance, tests are part of the subscription.

Can I store backups in the cloud?

Yes — off-site copies go to S3-compatible services (AWS S3, Backblaze B2, MinIO), SFTP or a dedicated backup server. Copies are encrypted before transfer, so even the cloud provider has no access to your data.

Does the backup cover only the database or files too?

A complete backup covers the database (full dumps and/or binlogs for point-in-time recovery), application files, server configuration and SSL certificates. The scope is defined individually to ensure nothing critical is missed.