AufiCloudLogo

You have backups, but do you have a continuity plan? A checklist to keep things running

¿Tienes backup, pero tienes plan de continuidad? Checklist para no parar

Having a backup is not the same as being able to resume operations quickly. When something goes down, the question isn’t “do we have a backup?” but rather “how long will it take to get back up and running?” This checklist addresses that.
It is designed for SMEs and IT departments that already perform backups but want to know whether those backups are sufficient to keep the business running in the event of an incident. It explains the difference between backups and business continuity, the questions a continuity plan must answer, how to define such a plan using two key metrics and specific tests, how AufiCloud can help, and how to build the plan in stages—concluding with a checklist for final review.

The problem: backup is not continuity

Muchas empresas tienen backup, pero no un plan de continuidad. Cuando ocurre un incidente —un equipo que muere, un ransomware, un borrado— descubren que restaurar es lento, incompleto o que la copia nunca se probó.

El resultado es el peor: la copia existe, pero la operación está parada de todos modos.

La diferencia se ve en cómo se vive el incidente. Con backup pero sin plan, el equipo improvisa: nadie sabe quién decide qué se restaura primero, cuánto tarda cada sistema ni si la copia más reciente sirve. Con plan, cada persona sabe qué hacer y en qué orden, y la empresa sabe de antemano cuánto tiempo estará parada.

AspectBackupContinuity plan
What it isThe copying of data and systems.The set of decisions, timelines, and procedures for resuming operations.
What is the response?Does a copy exist?How long will it take to resume operations, and what is the maximum potential loss?
What’s includedScheduled and stored backups.RTO and RPO per system, restoration tests, designated personnel, and documented procedures.
How it is testedVerifying that the backup was created.Performing an actual restore and measuring how long it takes.
Who respondsIT, when time permits.A designated person in charge, with backup available if they are unavailable.

There is also a risk that exacerbates the problem: backups are themselves a target. According to Veeam’s 2024 ransomware trends report—a survey of 1,200 organizations that experienced at least one attack—attackers attempted to reach backup repositories in 96% of those incidents. The same survey indicates that, on average, only 57% of compromised data was recovered, and that a mere 37% of organizations verify that their backups are clean before performing a restoration. While these figures come from a backup provider—and should therefore be viewed as an indicator of a trend rather than an exact measurement—they accurately describe the scenario that any contingency plan must account for.

The questions a plan must answer

A continuity plan is defined by two metrics and a series of tests.

These two metrics are the RTO and the RPO. The RTO (Recovery Time Objective) is the target time for resuming operations—that is, how long a system can remain down before the damage to the business becomes unacceptable. The RPO (Recovery Point Objective) is the maximum amount of data that can be lost, measured in terms of time; for instance, if a system has an RPO of four hours, the most recent backup must be no more than four hours old. Both metrics are defined on a per-system basis, as not all systems carry the same level of importance.

An illustrative example, using hypothetical values, shows what this definition might look like for a medium-sized company:

SystemRTORPOWhat it implies for backup
Facturación y ventas2 hours1 hoursFrequent backups and very fast restoration.
Email and collaboration4 hours4 hoursYou make copies several times a day.
Shared files8 hours24 hoursA daily copy is usually enough.
Low-criticality internal systems3 days24 hoursRestoration without urgency.

There is also a risk that exacerbates the problem: backups are themselves a target. According to Veeam’s 2024 ransomware trends report—a survey of 1,200 organizations that experienced at least one attack—attackers attempted to reach backup repositories in 96% of those incidents. The same survey indicates that, on average, only 57% of compromised data was recovered, and that a mere 37% of organizations verify that their backups are clean before performing a restoration. While these figures come from a backup provider—and should therefore be viewed as an indicator of a trend rather than an exact measurement—they accurately describe the scenario that any contingency plan must account for.

Las preguntas que un plan debe responder

A continuity plan is defined by two numbers and some tests.

The two metrics are RTO and RPO. RTO is the target time for resuming operations—that is, how long a system can remain down before the damage to the business becomes unacceptable. RPO is the maximum amount of data that can be lost, measured in terms of time; for instance, if a system has an RPO of four hours, the most recent backup must be no more than four hours old. Both are defined on a per-system basis, as not all systems carry the same weight or importance.

An illustrative example, using hypothetical values, shows what this definition might look like in a medium-sized company:

SistemaRTORPOQué implica para el backup
Invoicing and sales2 hours1 hoursFrequent backups and very fast restoration.
Email and collaboration4 hours4 hoursYou make copies several times a day.
Shared files8 hours24 hoursA daily copy is usually enough.
Low-criticality internal systems3 days24 hoursRestoration without urgency.

Testing is the step most frequently overlooked. A backup only proves its worth when it is successfully restored. It is advisable to test at three levels: restoring an individual file, restoring an entire system, and—at least once a year—conducting a full-scale simulation that walks through the entire procedure from start to finish, measuring how long it takes and identifying any points of failure.
With this in place, a plan should be able to answer seven questions without hesitation:

• Which systems are critical? Those that, if they stop, bring the business to a halt.

• How long can each one remain down? That is the RTO.

• How much data can each one afford to lose? That is the RPO.

• Where are the copies, and who can delete them? A copy that an attacker can delete is not a guarantee.

• When was a restoration last tested? If the answer is “never” or “I don’t know,” that is where the risk lies.

• Who carries out the recovery, and according to what instructions? The procedure must be documented.

• What happens if that person is not there? There should be a substitute who can follow the procedure.

The solution: continuity with AufiCloud

AufiCloud backs up data and systems in the cloud and, above all, enables rapid restoration so you can resume operations within your RTO. The backup is no longer just an untested insurance policy—it becomes a functional plan.

With a secure, cloud-based, and restorable backup, an incident shifts from «days of downtime» to «minutes for recovery.»

Two features are essential for business continuity. The first is that it backs up both data and systems, allowing for the restoration of full operations rather than just individual files. The second is that it keeps copies in the cloud—safely out of reach of an attack—which ensures a clean restoration following an incident. An off-site backup is particularly valuable when an issue affects the office itself, such as a theft, equipment failure, or a ransomware attack that encrypts everything on the network.

When evaluating any cloud backup service—including AufiCloud—it is advisable to ask the following questions and confirm the answers with Aufiero in the context of your specific situation:

• How long does a typical restoration of a critical system take? It should be comparable to the RTO.

• How often are backups performed? It must be able to meet the RPO.

• Who can delete or modify the copies? Protection against deletion is key when dealing with ransomware.

• Is the information encrypted? Both when it is stored and when it is transmitted.

• How long are previous copies kept? This is to allow for reverting to a point in time prior to the infection.

• Is it possible to test the restoration without affecting production? A test that disrupts service is not performed.

You have backups, but do you have a continuity plan? A checklist to keep things running

How to build your plan in stages

Define the RTO and RPO for each critical system, configure cloud backups accordingly, test the restoration process periodically, and document the procedure so that anyone can execute it.

A tested plan makes the difference between “we think we can get back up and running” and “we know exactly how long it will take to get back up and running.”

These four actions can be organized into six stages, with tangible results at each step:

• 1. Inventory. List the systems, the data, and the people who depend on each one.

• 2. Classify by criticality. Decide what to restore first, with input from business areas—not just IT.

• 3. Define RTO and RPO. A value for each critical system, accepted by the person responsible for the business.

• 4. Configure cloud backup, with frequency and retention settings aligned with those values.

• 5. Test the restoration. At a fixed frequency and by measuring the actual time.

• 6. Document and maintain. A written procedure, with designated personnel and alternates, which is reviewed whenever systems change.

The table proposes a testing frequency as a starting point, which each company adjusts based on its level of criticality:

ProofSuggested frequencyWhat is verified
Restoring a fileEvery month.Ensuring that backups are created and can be read.
Restore a complete systemEvery quarter.Verify that the system is functional again and determine how long it takes.
End-to-end simulationAt least once a year.Ensuring that the procedure, the individuals responsible, and the timelines all work together.
Plan reviewWhen a critical system changes.Determining which RTO, RPO, and procedures remain valid.

Continuity checklist

To review your current situation, mark which of these points are already addressed. Each unmarked point represents a specific risk:

• ☐ I have a list of the company’s critical systems and data.

• ☐ Each critical system has an RTO defined and accepted by the business.

• ☐ Each critical system has a defined RPO, and the backup frequency meets it.

• ☐ There is at least one off-site copy, in the cloud.

• ☐ The copies are protected against accidental or malicious deletion or modification.

• ☐ Backup covers data and systems, not just files.

• ☐ I attempted a complete restoration within the last twelve months.

• ☐ I know how long that restoration took, and I compared it with the RTO.

• ☐ I verify that the copies are clean before restoring.

• ☐ The recovery procedure is written down and is clear to someone who did not write it.

• ☐ There is a person in charge and a substitute to carry it out.

• ☐ I know whom to notify and how to communicate with clients and the team during an incident.

• ☐ I review the plan when the systems change.

If more than four points remained unmarked, the backup exists, but the continuity does not yet.

Common mistakes when creating a continuity plan

• Defining the RTO without consulting the business is a mistake. IT does not know the cost of each hour of downtime; that decision must be made by those responsible for the operation.

• Assuming that “the backup was created”—a “backup successful” notification is no guarantee that it can actually be restored.

• Store the copies in the same location as the data. An incident affecting the site also affects the copy.

• Writing a procedure that only its author understands—that person might not be present on the day an incident occurs.

• Failure to review the plan. A plan that was appropriate two years ago may no longer be so when systems change.

Conclusion

Having a backup is necessary, but it is not enough. A continuity plan—with defined RTO/RPO, verified restoration processes, and protected copies—is what ensures that an incident doesn’t bring your operations to a standstill. AufiCloud provides cloud-based backup and rapid recovery to support this.
At Aufiero Informática, we help you develop your continuity plan using AufiCloud—covering implementation, testing, and local support—so that, no matter what happens, you can keep your business running.

Frequently Asked Questions

Are a backup and a continuity plan the same thing?

No: the backup is the copy; the continuity plan defines the timeframe within which—and the maximum allowable data loss with which—you resume operations, based on a tested restoration process.

What are RTO and RPO?

RTO is the target time for resuming operations; RPO is the maximum amount of data you can afford to lose.

Does AufiCloud protect against ransomware?

By keeping copies in the cloud and out of reach of an attack, it helps ensure a clean restoration following an incident.

Does it cover data and systems?

Yes: back up data and systems to restore full operations, not just individual files.

More articles

Want to protect your company's information?