Backups you can actually restore

A backup is not proven reliable until it has been restored successfully. Businesses often discover problems only during an incident: the backup is old, incomplete, accessible to an attacker or missing the data they actually need.

Nemis helps make backups and recovery procedures verifiable. A backup is a copy of data or a system; disaster recovery is the agreed way to return to operation after an outage.

Arrange an initial consultation

I need IT help

When backups exist but nobody knows whether to trust them

This service is suited to businesses that do not know their backup status, run backups without testing or have data spread across local servers, NAS devices, cloud services and laptops.

You do not need to wait for a complete overhaul. We clarify the current state, address the most important issues and then build further capabilities. Technology supports business operations without becoming an endless project.

ASSESSMENT

The actual backup status is unknown

Backup jobs may be running, but nobody can say clearly which data is included, where it is stored or whether it can be recovered in time.

DISTRIBUTION

Data is spread across multiple locations

Local servers, NAS devices, SaaS services, cloud storage and laptops need a shared view of responsibilities, priorities and protection.

RISK

One incident can reach production and backups

If backups share production access rights, location or equipment, an outage or attack can affect both.

A completed transfer is only part of a backup strategy

Whether something currently works is only part of the picture. We also consider documentation, recoverability, access rights and behaviour during a change or outage. The initial assessment focuses on business impact as well as devices.

RECOVERY

Backups exist, but recovery has never been tested

A successful backup job does not prove that an application, data or server can actually be restored to a usable state.

NAS

A NAS or snapshot is the only protection

A local NAS and snapshots can be part of a solution, but without a separate backup they are insufficient for wider outages, mistakes or attacks.

ACCESS

Backups are accessible with production permissions

Administrator accounts and production access should not automatically grant unrestricted access to historical backups.

LOCATION

No off-site or offline backup

A physically or logically separate backup matters when an outage, fire, mistake or incident affects the primary location.

PRIORITIES

No agreed recovery order

An incident should not be the first time you decide which applications, data and users take priority when returning to work.

RPO/RTO

Acceptable data loss and downtime are undefined

Without agreed data loss and recovery time targets, choosing the right level of protection is difficult.

KNOWLEDGE

One person knows the recovery process

If recovery is undocumented and untested, one person's absence can prolong an incident and increase uncertainty.

Backups, access and recovery as a connected system

For each area, we first assess how your business works today and what is genuinely critical. We then identify the smallest useful action that reduces risk or improves reliability. Features are introduced for a purpose rather than simply because a product offers them.

We consider people, processes, existing equipment, maintenance costs and whether another responsible person could understand the solution. The outcome must be verifiable: we agree what success means, how to check it and where essential settings are documented.

ASSESSMENT

Reviewing existing backups

We record data, systems, applications, SaaS services, NAS devices and endpoints, then check what is actually backed up and what remains unprotected.

3-2-1-1-0

The 3-2-1-1-0 strategy

We define multiple copies, different media, a separate location and, where needed, immutable or offline backups, with regular verification.

ACCESS

Encryption and access

We organise encryption, key management, separate accounts and permissions to avoid unnecessary exposure of backups to production credentials.

OFF-SITE

Off-site and cloud backups

We assess separate locations, transfers, recovery capacity and the role of cloud services. Cloud synchronisation does not necessarily provide historical backups.

TEST

Test recovery

We perform sample restores of data, applications or virtual systems and record the outcome, duration and any limitations.

TARGETS

RPO and RTO

We define acceptable data loss in time and the target time for service restoration according to business impact.

Disaster recovery planning

We define priorities, responsibilities, the recovery sequence, communication and decision points after a major outage.

MONITORING

Regular verification

We establish alerts, regular reviews and sample restores, and update documentation when services or the environment change.

A separate remote backup of business data

Layered protection needs separation as well as multiple copies

The 3-2-1-1-0 strategy provides a useful framework for assessing resilience. Your business needs more than one copy, backups should not all depend on the same technology or location, and at least one copy should be separated from normal production access.

We also assess encryption, key management, separate accounts, alerts and the recovery path. Off-site or cloud backups are useful when it is clear what is transferred, how long recovery takes and who makes decisions during an incident.

RESILIENCE WITH VERIFIED PROTECTION

Separation reduces the risk of shared failure

Production systems, local backups, remote copies and immutable or offline copies serve different purposes. They address different risks and together support more realistic recovery.

More predictable recovery and clearer decisions

Good delivery makes key services more predictable, enables evidence-based troubleshooting and helps the business understand which decisions it needs to make.

This reduces dependence on individuals, shortens troubleshooting and supports more realistic cost planning. Backup decisions follow business priorities: systems have different impacts and may need different recovery targets.

RECOVERY

A better chance of successful recovery

Verified backups and agreed procedures mean recovery does not start with trial and error during an incident.

SEPARATION

Clear separation of backups from production

Separate media, locations and access rights reduce the chance of the same fault or attack reaching data and its backups simultaneously.

CALM RESPONSE

Less improvisation during an incident

The sequence, responsibilities and basic decisions are prepared in advance, making communication faster and clearer.

PRIORITIES

Clear priorities for data and applications

The business knows what is critical, what can be restored later and which data loss and downtime are acceptable.

SCENARIOS

A foundation for disaster recovery scenarios

Backups become part of a wider recovery plan covering services, users, communication and external support.

EVIDENCE

A documented backup verification process

Records of restore tests, timings and limitations support realistic planning and identify improvements.

First, establish what matters and what is achievable

We start by defining the business goal, scope, dependencies and constraints. We review the current state, available documentation and points where a change might affect users or data before making changes in production.

For larger changes, we prepare a sequence, maintenance window, verification process and rollback approach. We distinguish urgent actions from improvements requiring a separate project, licence, supplier or partner.

1. GOAL

Business impact and scope

We identify critical services, data, locations, users and the acceptable consequences of an outage.

2. ASSESSMENT

Backup status and gaps

We review what is backed up, where copies are stored, who has access, whether they are separated and when recovery was last tested.

3. IMPLEMENTATION

Approved improvements in stages

We organise priorities, access rights, locations, alerts, sample restores and documentation before making carefully planned production changes.

4. FOLLOW-UP

Regular verification and updates

When applications, data or the environment change, we adjust backup scope and check that agreed targets remain valid.

We verify backups by restoring working services

A restore test reveals more than a successful backup report. It checks backup availability, data integrity, access requirements, the sequence of steps and the actual recovery time. We record the result as the basis for further improvements.

RPO defines acceptable data loss in time: how much data the business can lose between the latest usable backup and an incident. RTO defines the target time for restoring a service. Both follow application importance and outage consequences as well as technical possibilities.

RPO AND RTO

Recovery targets are business agreements

Different systems may need different backup frequencies and recovery times. A good plan aligns protection with what is critical to the business and clearly describes remaining risks.

Test recovery and planning recovery objectives

An organised recovery plan for business IT services after an outage

Secure remote access, with on-site work when needed

Remote support is our usual way of working. Secure, documented access lets us review status, logs, configurations, permissions, alerts and diagnostic information without waiting for a visit.

Physical replacement, local recovery, connecting a separate device or security restrictions may require on-site work. We choose the approach that delivers the right result.

RESPONSIBLE DELIVERY

Quality delivery includes verification and scope boundaries

After implementation, we verify the agreed result and update documentation where needed for future maintenance. Work that could significantly affect availability, data or costs requires approval.

Backup and disaster recovery: frequently asked questions

For an initial assessment, useful details include important systems and data, approximate user or site numbers, existing backups and your main concern. If documentation is missing, we start with a limited review.

Is a NAS enough?

A NAS can be part of the strategy, but it needs a separate backup and verified recovery. Access, location, backup history and the business importance of data also matter.

How often should recovery be tested?

This depends on criticality and changes. Regular tests, recorded results and retesting after major application, infrastructure or procedural changes are important.

Does using the cloud automatically provide backups?

No. Synchronisation and provider availability do not always provide a separate historical copy. Retention, access, recovery options and responsibilities need checking.

What are RPO and RTO?

RPO is acceptable data loss measured in time; RTO is the target time for restoring a service. Both are defined according to business impact.

Do backups protect against ransomware?

They can reduce the consequences if copies are separate, access is restricted, retention is suitable and recovery is verified. Backups are one security measure among several and do not prevent every attack.

Organise your backups before you urgently need them

Describe your company size, number of users or sites, important systems and data, existing backups and main issue. Tell us whether this is urgent or a planned improvement. We will suggest an assessment, project approach or ongoing support arrangement.