Backups out of attackers’ reach
At least one backup outside the office, and one that cannot be deleted or encrypted from a company computer.

Most often a business finds out that its backup does not work on the day it needs it: the wrong data was backed up, the backup sat on the same disk, or it was encrypted along with the data. That is why we test backups the way they will be used: by restoring them.
We do not ask whether the backup ran. We check whether you can get back to work from it.
These are the two questions we start with. Accounting can afford to lose at most a day of work, an online shop an hour, a project archive a week. The answer determines how often we back up, where we keep the backups and how much it costs.
We also organise the data itself: where the company’s documents are, who has access to them and how long we store them. Less clutter means smaller backups, lower costs and less data that can leak.
The result has to be verifiable: you know what is backed up, where, how often and how long a restore takes, because it has been tested.
At least one backup outside the office, and one that cannot be deleted or encrypted from a company computer.
We regularly run test restores of files, email or an entire server and record how long they took.
Simple instructions: what we restore first, who decides and how quickly the key applications are back.

You can start with a review alone. If your backups turn out to be fine, you get that in writing.
We check what is backed up, where and how often, and whether data can be recovered from it, by running a test restore.
We define what we back up, how often and for how long, depending on how much data the business can afford to lose.
We set up off-site and deletion-proof backups, including for Microsoft 365 and Google Workspace.
We regularly test-restore selected data and record the result. It is the only proof that a backup works.
One place for company files, access by department and rules on how long we keep data.
The restore order, contacts and decisions for the day of an outage, written down in advance, not under stress.
Each stage ends with evidence: a review report, a written policy and a record of the test restore.
What is backed up, where and how often, and whether it can be restored.
How much data you can afford to lose and how long you can stand still. Everything else depends on that.
Off-site, deletion-proof backups with failure alerts.
We record how long the restore took. As part of ongoing support, we repeat this regularly.

A review with a test restore costs from PLN 2,900 net. Implementing a new backup policy: from PLN 3,900. Continuous monitoring with regular test restores: from PLN 990 per month plus the cost of backup storage. Backup monitoring is included in all ongoing support plans.
Mivare Systems
We use the files the site needs to work. Optional analytics tools will run only after you agree to them.
Necessary
Technical files the site needs to work properly and to remember your choice.
You will find the details in our Privacy policy and Cookie policy. You can change your choice at any time from the site footer.