Is your business backed up — or more importantly, recoverable?

Is your business backed up — or more importantly, recoverable?

Most businesses understand the importance of backups. Files, databases and business systems contain information that may have taken years to build, and losing that data could cause serious disruption.

So when the question comes up, “Are your systems backed up?”, the answer is often a confident yes. But there is another question that matters just as much:

If something happened today, could you actually recover the business?

Having backups and having a reliable recovery strategy are not necessarily the same thing.

A backup may be running successfully every day, but that alone doesn’t tell you where the data is stored, whether it is protected from a cyberattack, how far back you can recover, what information is included, or how long it would take to get critical systems operational again.

For a business that depends on its IT systems every day, those details matter.

Where your backups are stored matters

For many years, backing up business data meant copying it to another device, server or storage system at the office.

Local backups can still be useful. They can provide fast access to data and make certain types of recovery more convenient.

The problem arises when the backup and the systems it protects are exposed to the same event.

A hardware failure may affect a single server, but other incidents can have a much wider impact. Theft, fire, power-related damage or a cyberattack could potentially affect both production systems and locally connected backup storage.

This is why offsite backup has become an important part of business continuity planning.

Keeping a protected copy of business data outside the local environment means that a problem at the office does not necessarily remove the business’s ability to recover.

Cloud-first backup solutions take this a step further by sending backup data directly to an offsite cloud environment rather than relying on a local backup as the primary copy.

But simply putting a backup in the cloud doesn’t answer every recovery question either.

Ransomware changed the backup conversation

Backups have always been important for recovering from hardware failure, accidental deletion and data corruption. Ransomware introduced another problem: the backup itself may become a target.

If attackers gain sufficient access to an IT environment, encrypting the live data may not be their only objective. Preventing the organisation from restoring its systems makes an attack considerably more disruptive.

This means businesses now need to consider whether their backups are sufficiently separated and protected from the systems and accounts that could potentially be compromised.

One of the ways this can be achieved is through immutable backups.

An immutable backup is a protected copy of data that cannot simply be altered or deleted during its protected period. Even if ransomware gains access to the business network, an isolated immutable copy provides another recovery point that the attack cannot modify in the same way as ordinary connected storage.

This doesn’t make a business immune to ransomware. There are still many other security controls that need to be in place. But what it does strengthen, is the recovery side of the equation.

Good cybersecurity isn’t only about trying to prevent an incident. It also means being prepared to recover in the event of being compromised.

Yesterday’s backup may not be the one you need

Another question businesses often overlook is retention.

A daily backup may appear to provide everything the business needs, until someone discovers that a file was deleted several weeks ago or that a database problem started well before anyone noticed it.

If only recent versions are available, a perfectly successful backup from last night may already contain the same problem.

This is where retaining different historical recovery points becomes useful.

Depending on the business and the type of data involved, a backup strategy might retain daily backups for a period while also keeping selected weekly, monthly or longer-term recovery points.

More retention isn’t automatically better, however.

Consider an accounting database. Restoring a copy from a year ago may be technically possible, but it could be of limited practical value if doing so means losing a year’s worth of transactions that then need to be reconstructed.

The appropriate retention period therefore depends on what is being protected, how the information changes and what the business could realistically do with an older copy.

The objective shouldn’t simply be to keep backups for as long as possible. It should be to keep useful recovery points for an appropriate period.

Do you know what is actually being backed up?

Another common assumption is that if a backup system is running, everything important must be included. That isn’t necessarily the case.

Businesses change over time. New applications are installed, staff begin storing information in different locations, additional servers are added and more business processes move into cloud platforms.

A backup strategy that was appropriate several years ago may no longer reflect where the organisation’s important information resides today.

The same consideration applies to cloud services.

Using Microsoft 365, OneDrive, SharePoint or another cloud platform certainly provides advantages in availability and resilience, but storing information in the cloud should not automatically end the backup discussion.

The business still needs to understand what information needs protecting, what recovery options are available, how long information can be recovered and whether an independent backup is appropriate for its requirements.

The important question remains the same: If we needed this information back, could we recover it?

A successful backup needs someone watching it

There is another risk that has nothing to do with ransomware or sophisticated technology.

A backup can stop working.

A configuration change, authentication problem, storage issue, software fault or change elsewhere in the environment can interfere with a backup process.

If nobody is monitoring the backup, the business may continue operating under the assumption that everything is protected. The danger here is that you may only discover the issue when someone needs to restore something. At that point, a backup failure from three weeks ago becomes considerably more important.

This is one of the reasons centralised backup monitoring forms part of a managed IT environment. Backup status can be reviewed, failures can be investigated and problems can be addressed before the backup is needed.

The objective is straightforward: don’t discover that you have a backup problem during a recovery.

The real test is whether you can restore

A backup only delivers value when data can be recovered from it. This is exactly why backup planning should include the recovery process itself.

That means understanding questions such as:

  • Which systems and data are business-critical?
  • How recent does the restored information need to be?
  • How quickly does the business need those systems operational again?
  • Where will the data be restored if the original hardware is unavailable?
  • Are the required recovery points actually available?
  • Has the recovery process been tested?

The answers won’t be identical for every organisation. A five-person professional practice has different operational requirements from a company with multiple branches, servers and line-of-business applications. Some systems may need to be restored quickly. Others could remain unavailable for longer without materially affecting operations.

That is why backups should be considered in the context of business recovery, rather than treated as a technical checkbox.

Why IT Trust is standardising its approach to backup

IT Trust is increasingly moving managed client environments towards N-able COVE Data Protection as its preferred backup platform.

The reason is not simply to introduce another piece of software.

COVE uses a cloud-first approach, with primary backup data stored offsite rather than depending on a local backup appliance. It also provides immutable copies of protected data, configurable retention policies and centralised management.

For IT Trust, having clients on a consistent backup platform also improves visibility.

Instead of managing a collection of unrelated backup products across different client environments, technicians can work from a common platform, apply a more consistent approach and monitor backup status centrally.

Standardisation doesn’t remove the need to determine what each individual business needs. Backup frequency, retention and recovery requirements still need to reflect the organisation and the data being protected.

What it does provide is a more consistent foundation from which those requirements can be managed.

Backups are the starting point, not the finish line

The question every business should be able to answer isn’t simply:

“Do we have backups?”

A better set of questions would be:

What are we backing up? Where is it stored? How is it protected? How far back can we recover? Is somebody monitoring it? And if we needed it tomorrow, could we actually restore it?

You don’t need an incident to find out whether those answers are satisfactory.

Reviewing backups before they’re needed is part of the same preventative approach as maintaining hardware, installing security updates and monitoring the health of an IT environment.

Because ultimately, a backup isn’t there so that a report can say the backup completed successfully. It’s there so that the business can recover when it needs to.

Unsure about your current backup setup?

If you’re not sure what is being backed up, how your backups are being monitored, or what would happen if you needed to recover your systems, speak to IT Trust. We can help you review your current backup and recovery approach and identify any gaps that may need attention.

Updated:

Found this useful?
Share it with your network or explore more insights below.

Latest Posts

IT Trust Pulse

A monthly read for SME business owners

Practical IT insights, security tips, and what’s worth knowing about managing technology in your business.

Subscribe below.