The server sends a copy to an appliance at your office. From there an encrypted copy goes to us, in Poland. After an outage we restore the data on site or, if the whole site is lost, from the copy we hold.
Backup as a service
We place a NAS appliance at your office and run it for you: the schedule, retention, monitoring, and the response when a job fails. After the first full copy, later jobs send mainly the changes, so they can run often. An immutable copy cannot be deleted from the production server. The scope depends on the backup software: servers, virtual machines, workstations, files, databases, and applications.
An appliance on site that we manage
A copy of changes and an encrypted copy in Poland
Monitoring, alerts, and separate credentials for the copy
Restore, with a path to full DRaaS
A file comes back from the NAS. A whole system does too. When the software allows it, the copy starts at once as a virtual machine, without waiting for a new server. If both the server and the on-site appliance are lost, we restore from the copy we hold. Continuous replication, automatic failover, and a return to the production server are a later stage of the same architecture.
Restore a file or a system, or start the copy as a machine
Restore after the whole site is lost, from the copy in Poland
Later: continuous replication, failover, and failback
From a copy to full DRaaS
We start with a managed copy: an appliance at your office and a second copy with us. Then, when a shorter time back to work (RTO) is needed, we add starting a system from the copy. Full DRaaS, with a low RPO and RTO, is the third stage.
Stage 1: a local copy and an off-site copy
Stage 2: start the copy as a machine
Stage 3: continuous replication and failover
The copy path
1
Local copyThe server sends changes to the NAS on site.
2
Copy in PolandThe NAS sends an encrypted copy away from your site.
3
RestoreA file and a system from the NAS. The whole site from the copy we hold.
What you get
After every test you get a report, and the restore procedure is written down step by step. Below is an example with fictional data.
Example · fictional data
Restore test report
Test date
14.03.2026
Scope
ERP, file server, email
Target RTO
4 h
Measured recovery time
3 h 12 min
System
Restore time
ERP— No issues
1 h 05 min
File server— No issues
48 min
Email— With notes
1 h 19 min
Result: passed with notes
To fix
The appliance at the office is low on free space. Disks need adding before the next test.
The database password was not in the password vault. It delayed the email restore by 20 minutes.
Example · fictional data
Restore procedure, excerpt
01
IT manager
Confirms whether a file, a server, or the whole site is down.
02
alpha backup
Restores a file or a system from the appliance on site. ERP first.
03
alpha backup
If the appliance is down too, restores from the copy in Poland.
04
IT manager
Notifies teams using the contact list.
05
Both sides
After the repair, agree the return to the production server.