IT continuity and recovery

Microsoft 365 backup and IT disaster recovery for Swiss SMEs

A backup that has never been restored is not a backup.

Contivaro separates your backups from your infrastructure, performs real restores at an agreed interval, times the result, and maintains the plan that lets someone other than you do it again.

  • A copy out of reach of admin accounts
  • Restores actually performed
  • No on-call promise we cannot keep
  • Your provider stays in place
Recovery framework
Recovery time2 h 14target 4 h
Data loss15 mintarget 1 h
Last drill12 Sepnext in December
  • Offline copy verified
  • Restart order tested
  • Internal certificate: expires 30 Nov
  • ERP licence bound to hardware
  1. 01

    Identify the priority services and data

  2. 02

    Separate the backups and write the procedures

  3. 03

    Restore for real, measure, fix

Who it is forMid-sized firms and organisations whose activity stops when an application or a database stops.

In 30 seconds

A backup that actually works on the day you need it

Backing up is not enough. You need a copy nobody can erase, a procedure someone else can follow, and restores that have really been tested.

Your systems

Servers, databases, email: on site or with your host.

Contivaro

Copy out of reach, written procedures, timed drills.

Measured recovery

A real time to recover, a known data loss, a gap register.

RTO

Recovery time: how long without the service. Measured during a drill, not promised in a brochure.

RPO

Accepted data loss: how many hours of work you can afford to lose. Depends on the real backup frequency.

Immutable copy

A backup locked against writing for a fixed period. Ransomware that takes over administration cannot erase it.

Drill

A real restore on a separate environment, timed, with the list of what was missing.

The problem is almost never the backup.

The backups exist. They run at night, they send a green report in the morning, and nobody reads them because they are green. The problem appears on the day you need to use them.

That is when you find out, in order: the backup does contain the files but not the database, or the database but not the configuration the application needs to read it. The account that can launch the restore belongs to the person who left last year. The procedure is current for a version of the software that is no longer installed. And the backups sit on the same hypervisor as what they back up, so they are lost with it.

None of those problems show up in a green report. All of them show up in the first real restore drill. That is why Contivaro starts by running one.

What a complete framework contains

Every item is verifiable. If one is missing, the framework has a hole, and it is better to know before you need it.

  • A copy out of reach

    At least one copy that cannot be reached from production administrator accounts. Ransomware that takes administration also takes any backup reachable from it.

  • Written priorities

    Which services restart first, and in what order of dependency. Agreed with management, not only with IT, because it is a business decision.

  • Agreed, quantified targets

    How long without the service, and how much data you accept losing. Two numbers, written down, approved, and confronted with reality at each drill.

  • A procedure a third party can execute

    Written for someone who did not build the system, with the required access located. A procedure only its author can follow is worth nothing on a Sunday.

  • Dated drills

    Restores actually performed, at an agreed interval, with the time achieved and the list of gaps found.

  • A gap register

    What failed at the previous drill, who is fixing it, and where that stands. Without this register, you run the same drill and meet the same surprises.

The numbers the framework produces

Three indicators recorded at each drill. They come from a restore performed in front of you, not from a vendor dashboard.

RTO

Recovery time achieved

The time actually measured between the start of the drill and the service being usable again, compared with the agreed target.

RPO

Data loss observed

The gap between the last restored data and the moment of the simulated incident, which depends on the real backup frequency, not the configured one.

Gaps

Open items

The number of problems found at the drill and not yet fixed. This is the indicator that should trend to zero between two drills.

Estimate

What a day of downtime costs

The cost of an incident is worked out before it happens. That figure is what justifies the framework, or not.

Indicative estimate of staff idle time and data re-entry. It counts neither lost revenue, nor penalties, nor reputation.

Estimated cost of one incident
Get a detailed analysis

Pricing

What a recovery framework costs

Indicative ranges excluding applicable taxes. The monthly fee covers the restore drills and the follow-up, which is where most of the value sits.

01

Assessment

3'000 – 5'000 CHF

Two to three weeks. Inventory of real dependencies and priorities settled by management.

Request an assessment

02

First drill

8'000 – 15'000 CHF

One real restore, timed, on a separate environment. The report lists what is missing.

Request an assessment

The monthly fee is higher than the market average because it includes restores that are actually performed, not just backup monitoring.

What Contivaro does not include by default

No 24/7 on-call, no quantified uptime guarantee and no immediate emergency intervention are included. Coverage hours, response partners and any penalties are contracted separately, after checking they are sustainable. Promising an on-call service you cannot staff is worse than having none.

FAQ

Frequently asked questions

Is this just backup?

No, and backup is the least distinctive part of it. The value is in procedures written for a third party, restore drills actually performed, and tracking the gaps between two drills.

Is 24/7 intervention included?

Not by default. We assess what your activity genuinely requires, what it costs, and which partners are needed. That coverage is then contracted separately, with commitments we can keep.

Do we have to change hosting provider or managed service provider?

No. Contivaro works with your existing provider. The assessment states what is missing from the current setup, including when the answer is that your provider simply needs to enable an option they already offer.

What happens if a drill fails?

That is the most useful outcome of a first drill, and it is common. The failure produces a list of dated and assigned gaps. A drill that succeeds first time teaches almost nothing.

Does Contivaro touch our production?

Drills run on a restored environment, not on production. Any action that would touch production is announced, scheduled and approved by you beforehand.

Request an assessment

Start by knowing where you stand

Tell us which applications you cannot lose, how long you could hold out without them, and when a restore was last actually tested. We reply within two working days.

  • Swiss engineering
  • Reply within two working days

Email Contivaro

Tell us when a restore was last tested. If the answer is “never”, let’s start there.

Email Contivaro