Incomplete scope
Individual devices, cloud data or new applications were never added to the backup plan.
Managed service · Managed Backup
Backups that do not need explaining when it matters.
BITSS plans, monitors and documents backups for business-critical data and systems. The focus is not only on the copy, but on a realistic recovery.
Why this matters
A green tick is not the same as a recovery.
Many backups run for years without a visible error. Only when something fails does it become clear whether all the required data is included, whether credentials are available and whether the restart path is known.
Shared point of failure
Backup and production system are connected in such a way that encryption, hardware failure or a mistake can hit both.
Unclear restart
It has not been defined which systems are needed first and how long a restore may take.
Typical scope of service
What BITSS takes care of on an ongoing basis.
The exact scope depends on your existing IT, your business requirements and the agreed response times.
- Review and prioritisation of the data and systems to be backed up
- Backup concept based on the 3-2-1 principle, adapted to your environment
- Setup or takeover of automated backup jobs
- Monitoring of jobs and assessment of relevant error messages
- Documentation of storage locations, retention and responsibilities
- Recovery concept plus agreed tests within the defined scope
The limits of the service and the interfaces to internal staff or other providers are agreed in writing before we start.
Before the technology
Four questions shape the backup plan.
Management and IT should first agree on what the business actually needs after an incident.
- Which systems and data must become available first?
- How much data loss is tolerable for each system class?
- How quickly must work on that system resume?
- Who approves a recovery and who records the result?
These answers define RPO, RTO, backup intervals and clear responsibilities. The values are set for each system class and documented in the backup plan.
Approach
From the initial review to a tested recovery path.
Take inventory
Systems, data, dependencies and priorities are recorded together.
Define the backup plan
Copies, retention, backup intervals, service limits and responsibilities are documented.
Monitor
Errors, warnings and missing backups are detected and handled within the agreed scope.
Test recovery
Agreed restore tests cover the defined scope and record the result in a traceable way.
Frequently asked questions
Questions about Managed Backup.
What does the 3-2-1 principle mean?
Three copies of the data on at least two different storage media, with at least one copy held outside the primary system or site. A recovery test is additional evidence and does not replace any of these elements.
Is a cloud backup automatically safe?
No. What matters is access protection, separation from the production system, versioning, monitoring and a recovery path you can follow.
What is the difference between response time and recovery time?
Response time describes when qualified work begins. Recovery time describes the objective for returning a system to operation and depends on factors including data volume, connectivity, hardware and necessary approvals.
How are RPO and RTO defined?
RPO describes the maximum tolerable data loss. RTO describes the target time for resuming operation. Both values are agreed for each system class and documented in the backup plan.
Can BITSS review an existing solution?
Yes. We look at which data is actually captured, how the backups are separated and whether the recovery path is traceable.
No-obligation first contact
First clarify the situation. Then decide.
In the initial call we look at your existing systems, open risks and responsibilities. You receive a clear assessment of which measures really take priority.