---
title: "Managed backup — a backup that provably comes back"
description: "Backup for workplaces, servers and Microsoft 365 — monitored, with regular restore tests and a log. Billed per protected system, as a building block of managed operations."
canonical: "https://corevatis-redesign.pages.dev/en/services/backup/"
lang: en
schema_type: WebPage
---
# Managed backup — a backup that provably comes back

Backup for workplaces, servers and Microsoft 365 — monitored, with regular restore tests and a log. Billed per protected system, as a building block of managed operations.

## The short version

- **What:** Backup for workplaces, server workloads and Microsoft 365 — monitored, with restore tests and a log.
- **For whom:** Every company whose data deserves a second place. So, every company.
- **Model:** Add-on to managed operations, billed per protected system or by volume — as its own position.
- **Result:** A log with date, duration and result instead of hoping the green tick tells the truth.

A good fit if:

- The backup has run for years — nobody has ever restored from it
- Nobody knows how long a recovery would take
- Microsoft 365 data counts as 'it's in the cloud, it's safe'

What is a backup worth? Exactly as much as its last successful restore. A backup that has never been restored is not protection — it is hope with a green tick. The difference decides whether your business stands still for a day or a week.

That is why the core of our backup is not the copy but the proof: we restore at agreed intervals and log date, duration and result. [The backup drill shows how such an exercise works.](/en/use-cases/backup-drill)

## What gets protected? The three levels

| Level | What is protected | Against |
|---|---|---|
| **Workplaces** | Files and device state | Failure, theft, ransomware, accidental deletion |
| **Servers** | Complete instances — physical, virtual, cloud | Outage, encryption, failed updates |
| **Microsoft 365** | Mailboxes, OneDrive, SharePoint, Teams files | Deletion, account takeover, expiry of Microsoft retention |

Every level is bookable on its own and its own invoice position. The backup runs [via our operations platform](/en/services/managed-workplace), separated from production, with one copy off-site in the EU.

## How deep? Graded by recovery target

Not every system needs the same depth — and the depth sets the price. Per system we fix two numbers with you: how much data loss is bearable (backup rhythm), and how fast it must run again (recovery path). The ERP gets tighter targets than the file server — both stand in the offer, not in the small print.

## What "managed" means concretely

- **Monitoring instead of ticks** — failed runs get seen and fixed. A backup failure is an incident with us, not a log entry.
- **Restore tests with a log** — at agreed intervals we restore a file, a mailbox or a whole system, and record how long it took.
- **Recovery when it happens** — practised, documented, with known duration. You set the priority: ERP first, then mailboxes, then the rest.

## Honesty about limits

Recovery times depend on data volume, connectivity and target environment — so we do not promise a blanket number on the website; we measure your actual duration in the restore test and write it into the log. And a backup does not replace [the protection before it](/en/services/it-sicherheit) — it is the last line of defence, not the first.

## How is it billed?

As an [add-on](/en/services/add-ons) to managed operations: per protected system or by volume, monthly, as its own position. Restore tests are part of the block, not a surcharge — we would not want to own a backup without them.

## FAQ

**We already have a backup solution. Do we have to switch?**
Not necessarily. The assessment checks what exists. If it works, we take over monitoring and testing on top of it; if it has gaps, we say so with reasons and numbers.

**Where does the backup go?**
Separated from the production system, with one copy off-site in the EU — the concrete architecture follows your environment and the recovery targets we define together beforehand.

**Does Microsoft 365 really need its own backup?**
Yes. Microsoft protects the platform, not your content against deletion, overwriting or encryption through compromised accounts.

## Related topics

- [Proving data comes back — the backup drill](/en/use-cases/backup-drill)
- [Managed Server — backup supervision is part of server operations](/en/services/managed-server)
- [IT security — the lines of defence before it](/en/services/it-sicherheit)