Skip to content

A dead server comes back as a new VM.

Backup is the backup and recovery system in The One Stack, the platform MSPs run their whole business on. It protects Microsoft 365, Google Workspace, endpoints, SQL Server, Active Directory and whole machines from one console, and it replaces your SaaS backup, endpoint backup and server image backup. A dead server, restore as a new VM.

Cloud suites, endpoints, databases, directories and whole machines are protected from the same console that monitors them. A missed backup opens a ticket. A failed server restores from its image as a new virtual machine.

Replaces: your SaaS backup, endpoint backup and server image backup.

Harbor ITMeridian LawSample data

Backup

Cloud suites, endpoints, servers and images
Protected
Meridian LawMicrosoft 365Protected
Cascade FinancialGoogle WorkspaceProtected
MER-FS01Server imageProtected
APX-SQL-02SQL ServerMissed · T-4819
CAS-MBP-07FilesProtected
Restore · MER-FS01 image
Restore pointToday, 02:00
Restore asNew virtual machine
AlsoBare metal · files and folders
Restore as a new VM

The restored machine keeps its place on the client record.

Illustrative product view with sample data.

The job, start to finish.

The work Backup carries, in the order it happens, and where it hands off.

  1. 01

    Switch it on

    Backup switches on per client on the agent that is already installed. Discovery reads each device’s role and proposes what to protect: files, SQL Server, Active Directory or the whole machine.

  2. 02

    Protect

    Microsoft 365 and Google Workspace are backed up through a connection to the client’s tenant. Endpoints, databases, directory state and machine images are backed up on the schedule a policy sets.

  3. 03

    Verify

    Integrity checks re-read stored recovery points, decrypt them and compare checksums. Each recovery point shows when it last passed, and an alert rule fires when the checks go stale.

  4. 04

    A missed backup opens a ticket

    When a device or a tenant stops producing successful backups past its expected interval, a ticket opens in the service desk with the client, the device and the last success on it.

  5. 05

    Restore

    Restore a file, a mailbox item, a database to a point in time, or the whole machine. A dead server, restore as a new VM.

Inside Backup.

A few of its screens. Every module page shows its own.

A dead server comes back as a virtual machine

An image restore point gets a one-time recovery code. The new virtual machine starts from recovery media, takes the code, and the image is written to its blank disk, read back block by block and made bootable. The machine then checks in as the same device.

Image and bare-metal restore

Illustration, sample data. An image restore point, its one-time recovery code, and the steps that turn it into a running virtual machine.

Each client tenant, with its last backup

A Microsoft 365 tenant is one connection on the client’s record. The card names the data it protects, such as mail, OneDrive, SharePoint and Teams, and shows its state and when it last ran.

Microsoft 365

Illustration, sample data. Each client tenant with the data it protects, its state and its last backup.

Every client on one dashboard

Device health, cloud connections, open alerts and the latest jobs for every client sit on one page. A backup that stops raises an alert and opens a ticket in the service desk with the client and the device on it.

Monitoring and reporting

Illustration, sample data. Every client’s backups on one page: device health, cloud connections, open alerts and the latest jobs.

What it hands to the other systems.

A missed backup opens a ticket

Service gets a ticket with the client, the device, the policy and the last successful backup. If the same problem repeats, the open ticket is reused instead of a new one opening.

Service desk

Backup runs through the one agent

The backup module is part of the agent Endpoints already installed. Protecting a device is a setting for that client, not another rollout.

The platform

Backup status sits on the asset

The asset record in Endpoints shows the device’s backup status beside its configuration and documentation, read from the same device identity.

Assets and documentation

An incident finds its recovery point

From a Defend incident, an analyst sees the device’s recovery points from before the incident began and starts a restore from the one they choose.

Detection and response

Reports for the business review

You generate service-level and review reports per client, and take them to the business review.

Monitoring and reporting

Storage is metered

Backup is part of the plan and backup storage is metered. Usage is tracked per client and exports as a spreadsheet file, so you can see what each client stores.

Pricing

What changes for you.

For owners

Backup is part of the plan, and only storage is metered. You see per client what is protected, what is not and what it stores, and you stop reconciling separate backup vendors.

MSP owners

For technicians

A missed backup arrives as a ticket with the device on it, and the restore starts from the same console. There is no second agent to deploy and no separate backup portal to sign in to.

Service managers and technicians

For co-managed IT

A client’s IT team is notified by email when one of their own backups fails. They hear about no other client.

Co-managed IT

Proof slot

A customer running Backup on The One Stack

A named MSP, the tools it retired for this system, and a quote approved in writing by the customer.

Switching to it.

What imports

There is no backup history to import. Protection starts with the first backup taken here, so keep your current product’s recovery points for as long as each client’s retention needs them.

Bring your data

What runs side by side

Switch backup on for one client while your current backup product keeps running. Take a restore from each, compare them, then move to the next client.

Run side by side

What you turn off

When a client’s restores check out here and the old recovery points are past what you need, cancel that client’s SaaS backup, endpoint backup and server image backup.

How switching works

Questions

Questions about Backup

What does Backup back up?

Backup protects Microsoft 365, Google Workspace, files and folders on Windows, macOS and Linux, SQL Server databases, Active Directory system state and block-level images of Windows machines. Each workload has its own restore path, from a single item to the whole machine.

Can a failed server be restored as a virtual machine?

Yes. A dead server, restore as a new VM. The block-level image restores to a blank virtual disk or to new hardware, with the disk layout rebuilt and the boot files repaired.

Does Backup need a second agent?

No. Backup runs as a module of the one agent that already monitors and patches the device. Microsoft 365 and Google Workspace need no agent at all, only a connection to the tenant.

How is backup storage charged?

Backup storage is metered. Backup itself is part of the platform plan, and the pricing page explains how storage is charged.

What happens when a backup is missed?

A ticket opens in the service desk. It names the client, the device, the policy and the last successful backup, and a repeat of the same problem reuses the open ticket.

Can I run it beside my current backup product?

Yes. Switch Backup on for one client at a time while your current product keeps running, and retire the old one when that client’s restores check out.

Start

Run on One.

Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.