Take a furniture maker in the Savinja valley with 35 staff. Pantheon runs on a server in the office, drawings and CNC programs sit on the PC beside the machine, quotes live on the sales team's laptops and email is in Microsoft 365. Backup is a NAS in the same cabinet as the server, filled each night with a Pantheon copy. The machine PC is left out because it was set up ten years ago and nobody ever thought of it as a computer. Nobody has tried restoring Pantheon from the NAS either. When ransomware reaches the server, the NAS, protected by the same admin passwords, will be encrypted that very night. This situation is common: backups exist, but nobody knows what they actually protect against. That is why our starting point is never a product. It is a set of scenarios: a deleted file, a failed server or laptop, ransomware, and the loss of the whole site. Every scenario receives a dedicated response, and the recovery time is clocked in a genuine test. Everything happens remotely.
We start by tracking down every place where data is created, then give each scenario a protective layer of its own.
Servers, NAS units, laptops, cloud mailboxes and files, business application databases, plus the places people overlook: the PC next to the CNC machine, the X-ray workstation at a practice, the quotes folder on the director's desktop. Whatever is missing from the list is not backed up.
For each system we agree the longest tolerable outage (RTO) and the largest tolerable loss of recent work (RPO). Your business software needs different rules from an archive of finished projects.
Snapshots during the day plus version history in OneDrive or SharePoint. A user gets a deleted file back within minutes, and for a whole server the local copy on the NAS is the quickest way back.
At minimum one copy stays untouchable for a fixed window, admin password or not. This is the layer that defeats ransomware, and the cloud backup service sets it up in full.
The backup console does not use accounts from the company domain. Access requires dedicated accounts with multi-factor sign-in, so a stolen admin password does not also unlock the backups.
Daily, weekly and monthly copies with well-considered periods. Statutory retention of invoices and accounting records is agreed with your accountant, while GDPR requires that personal data is not kept longer than needed. Copies containing health records or other special categories of personal data are always encrypted.
A job that fails or never runs triggers an alert both for us and for someone you choose. Each restore test is logged: when, what was restored, and how long it took.
The timeline depends on data volume and the number of systems. Your quote already names the day of the first test restore.
We establish what is backed up today, where and how often, and whether anything has ever really been restored. We nearly always uncover at least one forgotten source.
For each system we settle the acceptable data loss and downtime. Those answers shape the budget, not the other way round.
Backup jobs, encryption, dedicated accounts and notifications are put in place remotely while everyone keeps working. Licences and storage appear in the quote separately from our labour.
We bring a key system back in an isolated environment and time it. That number becomes your real recovery time, replacing the one on paper.
You have to restore the order of things, not just the data. When several systems must come back at once, sequence matters more than the speed of any single step. The business software will not run without its database, the database needs the user directory, and nobody can sign in without a working network and VPN. So with every set-up we write a short step-by-step recovery plan: what comes first, who checks what, and when people can get back to work. The plan is tested together with the first restore.
That depends on how much work you could stand to redo. A webshop taking orders around the clock, or accounts during closing, may justify hourly copies; an archive of finished projects is fine with one a day. We decide system by system.
Not necessarily. If almost all your data already lives in Microsoft 365 or the cloud, a local NAS may be unnecessary. If you do need one, we write the specification, you order it through your usual supplier, a colleague plugs it in following picture-based steps, and the configuration is done by us remotely.
They are the ones most often forgotten. CNC programs, machine settings and recipes frequently live on a single elderly PC that nobody dares restart. If its operating system still allows an agent, we add it to the regular schedule; if not, we agree a manual copy routine with instructions or a file transfer to a shared folder.
First at set-up, then as agreed, typically once a quarter for key systems. Each test produces a record you can show to management, an auditor or your insurer.
Labour is charged at €50 per hour plus VAT, or it falls within a Start, Business or Premium plan. Licences and storage space are itemised on their own and you pay those providers yourselves.
Tell us which systems you run, roughly how much data there is and the downtime each one can tolerate. Our answer will be a proposal built on scenarios.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.
