Backups matched to the systems you use.
We define the scope of each backup and the procedure for restoring it. Frequency, retention and monitoring are agreed around your data and business operations.
Servers and websites
Backups of the files, databases and configurations covered by the plan. We prepare the procedure for restoring a website, an online shop or the services on a server.
Let’s talk ↗ 02 /Databases
Backups using procedures compatible with each database. We set the frequency according to how often the information changes and check restoration.
Let’s talk ↗ 03 /Full and incremental local backups
We configure full backups, incremental backups and local mirrors of the agreed data on computers, shared folders and NAS devices. Each method has its role and retention settings; mirrors complement backups that retain earlier versions.
Let’s talk ↗ 04 /Online, secondary and offline copies
A backup intake server receives online backups. We add secondary and offline copies, documenting the destinations, access and scope of each copy.
Let’s talk ↗ 05 /Monitoring and tests
Reviewing logs, identifying failed jobs and testing restoration. We agree how often these checks take place and how issues are reported.
Let’s talk ↗ 06 /Restoring data and services
We review the available backups, select the appropriate version and help restore it. What can be recovered depends on the valid copies and what they contain.
Let’s talk ↗Quote
A quote based on your systems and data.
We set out the initial configuration, storage destinations, retention, monitoring and testing tasks. Cost depends on the amount of data, backup frequency and service scope.
Let’s talkFrequently asked questions
What does going beyond 3-2-1 mean?
Alongside the minimum copies, we make full local backups, incremental backups and mirrors. The online setup includes a backup intake server, secondary copies and additional offline copies. Scope, frequency and retention are defined for each system.
How long are backups kept?
This is agreed for each system. Frequency determines how much work could be lost between copies; retention determines how far back we can attempt to restore. Both are defined before setting up the service.
Is a NAS or a synchronised folder already a backup?
Not necessarily. A NAS may hold the only version of your data, and synchronisation can propagate a deletion or a damaged file. We check whether independent copies and recoverable versions exist.
Is an off-site copy protected from ransomware?
Location alone is not enough. That is why we add offline copies and review access to the other backups. After an attack, the available versions must be checked to establish which can be restored; we do not assume a copy is valid without reviewing it.
Can you review our existing backups?
Yes. We review jobs, storage destinations, errors and retention, and test restoration within the agreed scope. We then propose any changes needed.
What if we have already lost data?
Tell us what happened, which systems are affected and what backups exist. We assess the restoration options. Recovery cannot be guaranteed without checking the available copies.