Backup & Disaster Recovery
We design resilient backup, off-site and Disaster Recovery solutions with defined RPO/RTO, ransomware protection and tested recovery.
- ✓ Scope tailored to the project
- ✓ Reply within 1 business day
- ✓ Vendor-neutral
Backup only has value if you can actually recover from it
Creating a backup is only the beginning. When storage fails, data is deleted, ransomware strikes, a database becomes corrupted or an entire environment is lost, the important question becomes: how quickly can the organisation return to operation, and how much data can it afford to lose?
sLogic Group designs and implements Backup and Disaster Recovery solutions based on service criticality, risk and RPO/RTO requirements. We combine local and off-site backup, immutable protection, environment separation, monitoring and tested recovery scenarios.
We do not stop at a “backup completed successfully” message. The real outcome is the ability to recover the right data and restore critical services.
Resilient to failures and ransomware
We design backup separation, off-site copies, immutability and controlled administrative access to the backup infrastructure.
Defined RPO and RTO
We establish acceptable data loss and required recovery times for individual systems and business services.
Tested recovery
We verify that data and systems can actually be restored instead of assuming that a successful backup job means successful recovery.
The most important metric of a backup system is not the number of completed backup jobs. It is the ability to restore the right data and services within the required timeframe.
You have backups — but do you know whether you can recover after a major failure?
We will assess your data protection architecture, copy separation, retention, RPO/RTO and actual recovery readiness.
Backup and Disaster Recovery — what is the difference?
Backup
Recovers data. It provides copies of files, databases, virtual machines, configurations or complete systems from an earlier point in time.
Disaster Recovery
Restores services. It defines recovery order, dependencies, alternative infrastructure, responsibilities and the actions required during a major outage.
An organisation can have valid backups and still lack a realistic way to restore operations quickly. Recovering an application may also require networking, identity services, DNS, databases, storage and other infrastructure dependencies.
What does our Backup and Disaster Recovery service cover?
Backup architecture
We design protection for virtual machines, servers, data, configurations, databases and critical infrastructure services.
Off-site backup
We create independent copies outside the primary site or failure domain of the production environment.
Immutable backup
We use mechanisms that prevent protected copies from being modified or deleted during a defined retention period.
Disaster Recovery
We design failure scenarios, recovery priorities, required resources and procedures for restoring services.
Backup monitoring
We monitor jobs, errors, retention, repositories, off-site copies and other parameters affecting continuity of protection.
Recovery testing
We test data restoration, system recovery and complete recovery scenarios instead of relying on assumptions.
RPO and RTO
We help define business requirements for maximum acceptable data loss and service recovery time.
DR plan and runbook
We document priorities, dependencies, responsibilities and the steps required to recover the environment.
RPO and RTO — backup starts with business requirements
The question “how often should we run backups?” should only be answered after the importance of each system has been established.
RPO — how much data can we lose?
RPO defines acceptable data loss expressed in time. A transactional system may require a much shorter RPO than a document archive.
RTO — how quickly must we recover?
RTO defines the target maximum period for restoring a system or service after a failure or incident.
The more demanding the RPO and RTO, the more advanced the required architecture may become. That is why we do not protect every system in exactly the same way.
Not every system is equally critical
An ERP platform, database, email system, file service, production application and document archive may all require completely different levels of protection.
Before designing the architecture, we determine:
- which systems are critical to business operations,
- how long the organisation can operate without each service,
- how much data loss is acceptable,
- which dependencies exist between systems,
- in what order systems should be recovered,
- where they can be started if the primary infrastructure is unavailable,
- who has the authority to activate the Disaster Recovery procedure.
Ransomware-resilient backup
An attacker with administrative privileges may attempt to destroy not only production systems but also their backups.
For this reason, the protection architecture may include:
- immutable repositories,
- independent off-site copies,
- separate administrative accounts and security domains,
- least-privilege access,
- MFA for administrative access,
- restricted access to backup repositories,
- data encryption,
- monitoring for attempts to modify or delete backups,
- offline or logically isolated copies where justified.
A backup stored within the same trust zone as production may be lost during the same incident. Separation is just as important as creating the backup itself.
The 3-2-1-1-0 backup strategy
The 3-2-1-1-0 model is a useful reference point when designing a resilient data protection strategy.
3 copies of data
Production data plus additional copies that preserve recovery capability after one set is lost.
2 storage layers
Reducing dependency on a single device, repository or storage technology.
1 off-site + 1 protected
A copy outside the primary location plus an additional immutable, offline or appropriately isolated layer.
0 undetected errors
Monitoring and recovery testing should identify problems before the backup is actually needed.
We do not treat 3-2-1-1-0 as a rigid formula. The architecture should be based on risk, data volume, RPO, RTO, available bandwidth, location requirements and budget.
Off-site backup
A data centre outage, fire, power failure, administrative error or security compromise may affect both production systems and local backups.
Additional copies can therefore be stored:
- in a second server room,
- in an independent data centre,
- in the cloud,
- in object storage,
- in another environment providing an appropriate level of separation.
The model is selected based on data volume, available bandwidth, retention, required recovery time, data-location requirements and overall cost.
Disaster Recovery — when the entire environment is affected
Backup restores data. Disaster Recovery defines how to turn that data back into a functioning business service.
Recovery scenarios may include:
- loss of a single server or cluster,
- storage failure,
- loss of the primary site,
- ransomware or compromise of multiple systems,
- database corruption,
- failure of critical network infrastructure,
- loss of identity services,
- starting the environment in an alternative location.
Disaster Recovery plan
During a major failure, the organisation should not be discovering for the first time who has access to the backups, which system should be recovered first or where the documentation is stored.
Recovery priorities
The order in which services should be restored according to their importance to the organisation.
Dependencies
DNS, identity, networking, storage, databases and other components required for applications to operate.
Roles and responsibilities
People responsible for decisions, recovery activities, incident communication and coordination with suppliers.
Recovery runbook
Step-by-step actions, checkpoints and procedures for confirming that the environment has been restored correctly.
Recovery testing — before the failure happens
An untested backup does not provide enough confidence that it will work when it is genuinely needed.
Testing may include:
- restoring individual files,
- database recovery,
- starting a virtual machine from backup,
- restoring an application together with its dependencies,
- starting systems at an alternative site,
- measuring actual RTO,
- validating DR procedures,
- recovery exercises involving the customer's team.
After testing, we document the result, identified issues and actions required to improve recovery readiness.
Backup monitoring
A single undetected failure can leave a critical system without a current backup for days or even weeks.
Monitoring may include:
- backup job status,
- backup duration,
- available restore points,
- repository utilisation,
- off-site copy status,
- replication errors,
- retention,
- backup infrastructure health,
- unusual events requiring investigation.
What can we protect?
Virtualisation
Virtual machines and configurations running in environments such as Proxmox VE, Hyper-V and other platforms.
Servers and applications
Linux, Windows Server, business applications, file servers and other infrastructure components.
Databases
Protection designed around data consistency, change frequency and required recovery points.
Cloud and SaaS
Additional protection for data stored in cloud services and SaaS platforms.
Files and storage
Data stored on file servers, storage arrays and other storage layers.
Configurations
Configurations and information required to rebuild critical infrastructure components.
Hybrid environments
Protection strategies spanning on-premises, data centre, Private Cloud and public cloud infrastructure.
Multiple locations
Copies distributed between branches, data centres and other independent locations.
Technology matched to the environment
We do not require the entire environment to be migrated to a single platform. The solution is designed around the organisation's data, risk, RPO/RTO and existing architecture.
We work with environments using technologies including:
- Veeam Backup & Replication,
- Proxmox Backup Server,
- Proxmox VE,
- Microsoft Hyper-V,
- Linux and Windows Server,
- local and object storage,
- S3-compatible repositories,
- on-premises, Private Cloud and public cloud infrastructure.
Technology selection is the result of requirements and risk — not the starting point of the project.
How do we deliver a Backup and Disaster Recovery project?
Assessment
We inventory data, systems, existing protection, retention, locations and key dependencies.
Requirements
We define system criticality, RPO, RTO and relevant failure and cyberattack scenarios.
Architecture
We design backup, retention, off-site copies, separation, protection mechanisms and the required Disaster Recovery capability.
Implementation and testing
We deploy the solution, configure monitoring, document recovery procedures and perform recovery testing.
If the current level of protection is not well understood, we can start with an IT Audit and Architecture review.
Managed Backup — continuous data protection
Backup is not a one-off deployment. Infrastructure changes, new systems and data appear, repositories grow and RPO/RTO requirements evolve.
We can therefore provide a specialised ongoing service covering:
- backup monitoring,
- failure handling,
- retention management,
- capacity monitoring,
- off-site copies,
- regular recovery testing,
- documentation updates,
- extending protection to new systems,
- data protection reporting.
This is not generic IT outsourcing — the scope is specifically focused on continuous data protection and recovery readiness.
Backup and DR as part of cyber resilience
Backup and Disaster Recovery are part of a broader cybersecurity and Business Continuity model. The backup environment should be designed so that compromise of production systems does not automatically result in the loss of all recovery copies.
For organisations with broader requirements, this area can be integrated with our CISO as a Service or NIS2 / KSC services.
Why sLogic Group?
We understand the whole infrastructure
We design backup in the context of virtualisation, storage, networking, databases, operating systems and application dependencies.
Recovery-first
A green backup status is not the objective. The objective is the ability to recover data and restore services.
Vendor-neutral
The architecture is not tied to one vendor. We select solutions based on risk, existing infrastructure and business requirements.
Design + implementation + testing
We design the architecture, implement it and verify it through real recovery scenarios.
Frequently asked questions
Are Backup and Disaster Recovery the same thing?
No. Backup creates recoverable copies of data, while Disaster Recovery defines how systems and services are restored after a major failure. Backup is a foundation of DR, but it is not a complete recovery plan by itself.
What does RPO mean?
RPO — Recovery Point Objective — defines the acceptable amount of data loss expressed in time.
What does RTO mean?
RTO — Recovery Time Objective — defines the target maximum time required to restore a system or service following a failure.
How often should backups be performed?
Backup frequency should be determined by RPO and the nature of the data. Different systems may require completely different backup frequencies or additional replication.
Is local backup enough?
Not always. If production and all copies are located in the same site or administrative domain, one major incident may affect both. This is why off-site copies and additional separation are often required.
What is immutable backup?
Immutable backup is a copy protected against modification or deletion for a defined period. It provides an additional layer of protection against ransomware, administrative error and compromised privileged accounts.
Does backup protect against ransomware?
A well-designed backup solution significantly improves the ability to recover from ransomware, but copies alone are not enough. Separation, access control, immutable or offline protection, monitoring and tested recovery are also important.
Do you test recovery?
Yes. Testing may range from restoring an individual file or database to starting an entire application or performing a complete Disaster Recovery scenario.
Can you take over an existing backup environment?
Yes. We can assess the existing architecture, verify configuration and backup status, improve monitoring and recommend changes only where they are actually needed.
Do we have to use sLogic Group infrastructure?
No. We can work with the customer's own infrastructure, data centre, selected cloud platform, object storage or hybrid architecture. Location and technology are determined by project requirements.
Do you offer Managed Backup?
Yes. We can provide continuous monitoring, failure handling, off-site copies, retention management, recovery testing and ongoing development of protection as the infrastructure changes.
How much does Backup and Disaster Recovery cost?
The cost depends on factors such as data volume, number of protected systems, retention, backup frequency, required RPO/RTO, copy locations and the level of Disaster Recovery capability. After assessing the environment, we prepare an architecture and cost model aligned with the actual requirements.
Do not just ask whether you have backups. Ask whether you can recover.
We will assess your data protection environment, identify the main risks and design Backup and Disaster Recovery around your organisation's actual requirements.