What is included

We configure the backups and, more importantly, the verification procedure: a copy without a tested restore is hope, not protection.

Discuss the scope

Defining requirements

What is critical, how much data can be lost and how quickly you need to be back up.

Backup scheme

Three copies, two types of media, one of them off site.

Configuring jobs

Servers, databases, virtual machines, hardware configurations and email.

Protecting the copies

Separate credentials and immutable copies so ransomware cannot reach them.

Monitoring

Failure alerts sent to a real person, not to the mailbox of someone who has left.

Restore testing

A defined routine: spot checks monthly, a full server restore quarterly.

How the work runs

Configuration for typical infrastructure takes one to two weeks including the first full run.

01

Assessment

What is already backed up and what is not, where the copies are kept and whether a restore has ever been attempted.

02

Design

A scheme with calculated volumes, retention depth and the backup window.

03

Implementation

Configuring jobs, storage, permissions and alerts.

04

Verification

A test restore with the time measured. That is your real RTO.

Retention depth matters more than backup frequency. Ransomware sits in a network for weeks before it fires. If you keep seven days of copies and the malware activated on day fourteen, every copy you have is already infected. A sensible minimum is a month, plus monthly snapshots kept for a year.

Frequently asked questions

Databases with a proper dump, virtual machine images, configurations of network hardware and firewalls, the user directory and licence keys. Configurations are what people usually forget: the data is there, but the settings exist only in an engineer head.

Spot checks once a month and a full restore of a critical server once a quarter, timed. The real recovery time is almost always longer than expected, and it is better to find that out during a drill.

Only with the right permissions. If the backup account can delete objects, the malware will delete the cloud copies too. You need a key with no delete rights and immutability enabled on the storage side.

We will set up your backups

Tell us what needs protecting and how much downtime is acceptable. We will propose a scheme that meets those requirements.