One service decides what gets copied and how often. The other keeps one copy permanently out of reach of fire, flooding or anyone who breaks into your network.
We list what genuinely needs protecting: the accounting database, the shared drive, Microsoft 365 mailboxes, firewall configuration. Then we set schedules and retention, make sure a failed job raises an alarm, and draft a brief playbook for the day it all goes wrong.
Your data is encrypted, then stored with a European provider behind its own logins and a lock that blocks deletion. Ransomware that takes over your domain has no path to it.
For each system we pin down RTO, the longest it may stay offline, and RPO, the amount of recent work you could bear to redo. Below are example figures for a firm with a few dozen staff.
Offline for 4 hours at most, 1 hour of data at most. A single overnight copy of a Comarch, Symfonia or enova365 database is not enough on a VAT filing day. The database needs its transaction log captured several times during the working day.
24 hours down and 24 hours lost are acceptable. For most companies one copy after hours covers it.
4 hours offline, 1 hour of data. Microsoft is responsible mainly for keeping the platform up, not for bringing back a mailbox a departing employee emptied. A separate mailbox backup is essential.
An hour offline, an hour of data. With Allegro orders and BLIK payments flowing in, restoring from a copy takes too long. A warm standby environment is the only realistic answer.
24 hours either way. Realistic only if files are synced to OneDrive instead of sitting on somebody's desktop.
Copying data to a second folder on that very server protects nothing. One dead disk controller, one encrypting worm or one careless delete, and both versions vanish at once. As a bare minimum, keep two copies on separate hardware and a third outside the building, preferably in the cloud.
Everything happens remotely over secure access to your servers and the Microsoft 365 admin portal. Setting things up is usually a matter of days. Step four is where the value lies, and it is the step most firms skip.
We trace where business-critical files actually live. Typical traps are a price list saved only on one salesperson's laptop, or signed agreements nobody filed anywhere except an inbox.
With you, we decide on a tolerable outage and tolerable data loss per system. Those figures drive the budget, never the other way round.
Schedules, retention, encryption and an off-site copy. You get an alert when a job fails, and also when the expected report never turns up.
At an interval agreed with you, selected data is recovered into a sandbox while we log the minutes. The result goes into a report you can hand to an auditor.
Ask whoever looks after it when they last restored anything. Common findings are jobs that have been failing for months, a backup pointing at an outdated folder, or an encryption password that left with a former employee. Our check ends with a clear verdict.
Only if an attacker cannot reach it from inside your network using the same accounts. Criminal groups now hunt for the backup server and wipe it before they start encrypting. You need a copy with separate credentials and a lock that blocks changes for a fixed period.
We usually start with 30 days of dailies, three months of weeklies and twelve monthly snapshots. Accounting records need a longer horizon because Polish accounting law requires books and approved statements to be kept for years, and medical practices face even longer periods for patient records.
Yes. The GDPR explicitly mentions the ability to restore access to personal data in good time, and organisations covered by NIS2 and the Polish cybersecurity act are expected to manage business continuity. Test restore reports are hard evidence when an auditor or the data protection authority asks. Whether the act applies to you is worth confirming with a lawyer.
One of your staff following our step-by-step instructions, or a local technician you already use. We diagnose the fault, say exactly which drive to pull and take over everything that can be done across the network: rebuilding the array, restoring data and checking consistency.
We review your current set-up remotely, attempt a restore from it and tell you honestly whether it would rescue the company on a bad day.
Your enquiry has reached us
You will hear back within one working day, and if you have reported an outage that is holding up work, it goes to the front of the queue.
No match for that name. Try a different spelling or pick a bigger town nearby - all our support is delivered online, so your choice has no effect on the service.
