// Systems

Disaster recovery and backup

A backup that has never been restored is not a backup: it is a hope. We design daily backups and recovery plans that we actually test, so an incident is a bad moment and not the end of your business.

Daily backups
Tested recovery
Anti-ransomware
// 01

Daily, strategic backups, not on autopilot

We design a backup strategy tailored to your business: which data is critical, how often, where it is stored and how long it is kept. Daily backups, layered retention and always a destination that does not share the same risk as the source, because ransomware that encrypts your server must not be able to encrypt your backups too.

Backup is the last safety net against human error, hardware failure, attacks and physical disasters. We treat it as such: monitored, alerted and verified, not as a task someone configured once and nobody looked at again.

Daily backups and layered retention
Isolated destinations against ransomware
Automatic verification and alerts
Strategy tailored to your critical data
// 02

Recovery that is tested, not just promised

A disaster recovery plan defines exactly how your business comes back after a serious incident: in what order, in how long and with which steps. But a plan that is never rehearsed is worthless. That is why we test restores, measure real times and adjust until the plan survives contact with reality.

This demand comes from our background in clinical-hospital software, where downtime was not an inconvenience but a risk to people. We apply that same rigor to your company, whatever its size.

Documented disaster recovery plans
Tested restores with real timings
Clear recovery objectives (RTO/RPO)
Rigor inherited from critical environments
// 03

How we design your plan, step by step

First we understand what needs protecting: we inventory your data and systems and classify them by criticality, because not everything is worth the same or needs the same backup frequency. Then we define the recovery objectives with you in business terms, not jargon: how long you can afford to be down (RTO) and how much data you can afford to lose (RPO).

With those objectives we design the strategy: what gets copied, how often, to which destinations and with what retention, always with at least one destination isolated from the production environment. We implement it, automate daily verification and schedule test restores. And when your infrastructure changes, the plan gets reviewed: an outdated recovery plan is almost as dangerous as having none.

Inventory and classification of data by criticality
Recovery objectives defined with you (RTO/RPO)
Layered strategy with isolated destinations
Automatic verification and review on changes
// 04

The backup mistakes we run into every week

Data disasters almost never come from exotic catastrophes: they come from silent mistakes. The backup stored on the same server it protects. The job that has been failing for months while nobody reads the warning. The critical folder that was left excluded. Single-version retention that overwrites good data with encrypted data. The restore nobody ever tested.

And an increasingly common one: assuming that email and files in the cloud are 'already backed up' because they are in the cloud. The provider guarantees that its platform runs, not recovering what you delete or what an attacker destroys. Our strategy covers that data too, and continuous verification keeps any silent failure from going months undetected.

Backups stored in the same place as the source
Backup jobs failing with nobody watching
Retention too shallow to survive ransomware
Cloud data nobody is actually backing up
// 05

Continuity designed for Balearic businesses

In an economy as seasonal as the Balearics, the timing of a disaster matters as much as the disaster itself: losing the booking data in May, or patient records at any time, is not an IT problem, it is a business problem. We design recovery plans around your calendar and test restores before your critical months, not during them.

Being in Mallorca also counts when the disaster is physical: if systems need rebuilding after a serious failure, a flood or a burglary, you do not manage the crisis through a support line a thousand kilometers away. And backup does not work alone: Penny's monitoring watches every copy, and the service integrates with SYSBalear's maintenance and cybersecurity.

Plans that respect your calendar and your high season
Restores tested before the critical months
On-site response when the disaster is physical
Backups watched 24/7 by Penny's monitoring
// FAQ

Frequently asked questions

We already have backups, why do we need you?

The key question is not whether you have backups, but whether they work when needed. Many companies discover their backups were incomplete or corrupt precisely on the day of disaster. We verify your backups, run real restore tests and close the gaps that almost always appear.

Do you protect backups against ransomware?

Yes. We design backup destinations to be isolated from the production environment, so an attack that encrypts your servers cannot reach your backups too. That is exactly what makes the difference between paying a ransom or restoring and getting back to work.

What are RTO and RPO, and why do they matter?

They are the two numbers that define your plan: RTO is how long you can afford to be down, and RPO is how much data you can lose (the hours of work since the last backup). We do not set them for you: we define them with you in business terms, and from there come the backup frequency, the destinations and an investment proportional to what is at stake.

Do you also back up the email and files we keep in the cloud?

Yes, and it is more necessary than it looks. The cloud provider guarantees that its platform runs, but recovering a deleted mailbox, a wrecked folder or data destroyed by an attacker is your responsibility. We include that data in the backup strategy with its own retention, just like the data on your servers.

◇ Let's talk, tell us your idea

◇ Let's talk, tell us your idea