Skip to content

Restore the database to a point in time. Bring the directory back.

Servers and databases is the application-aware backup module in the Backup system of The One Stack, the platform MSPs run their whole business on. It backs up SQL Server with full, differential and log backups for point-in-time recovery, and Active Directory system state on domain controllers. It is for the MSP whose clients depend on a database server and a directory.

Servers and databases is part of Backup, one of the six systems of The One Stack.

Illustration, sample data. Server and database jobs in one list, with full, differential and log backups and the reason a job failed.

What it does.

SQL Server full, differential and log backups

SQL Server takes each backup itself, with compression and a checksum, and reads the backup file back before it is accepted.

Point-in-time recovery

The log chain is tracked for each database. Choose a moment, and the restore plan picks the full, differential and log backups needed to reach it.

Restore beside the original

A database can restore under a new name on the server, so you can check the data before anything replaces production.

Active Directory system state

Domain controllers are backed up with the operating system’s own system-state backup, through the agent on the server.

A guided directory restore

A directory restore produces a step-by-step plan for the technician at the domain controller: system-state recovery, an authoritative restore, or deleted objects from the recycle bin. The technician records the outcome on the restore.

Inside servers and databases.

More of the product, screen by screen.

Restore points, and whether each was verified

Each completed backup of a server is a restore point with a badge that says if it has been verified. For a database server, the page also lists the instants each database can be restored to from its log backups.

Illustration, sample data. One server’s restore points with their verification state, and the instants each database can go back to.

How it connects.

Servers and databases reads and writes the same record as the rest of the platform.

Discovery spots the role

When a managed device runs SQL Server or is a domain controller, discovery proposes database or directory backup for it.

Monitoring and alerting

It runs through the one agent

Database and directory backups run through the agent already on the server. There is no backup server to stand up beside it.

The platform

A server that stops backing up opens a ticket

A database or a domain controller that passes its expected interval without a successful backup opens a ticket in the service desk.

Monitoring and reporting

The whole machine has an image

When the server itself is lost, not only its data, the block-level image restores it to new hardware or as a new virtual machine.

Image and bare-metal restore

Questions

Questions about servers and databases

Does it support point-in-time recovery for SQL Server?

Yes. Full, differential and log backups are tracked as one chain, and a restore plan reaches the moment you choose.

Are SQL Server backups application-consistent?

Yes. SQL Server takes each backup with its own backup commands, with a checksum, and reads the file back before the backup is accepted.

What does SQL Server backup need on the server?

The agent’s account needs backup rights in SQL Server and a staging folder that SQL Server can write to. It is a documented setup step for each server.

Can Active Directory be restored without a technician?

No. A directory restore is a guided procedure a technician runs on the domain controller, because a domain controller enters its recovery mode at the machine. The plan and the recorded outcome stay on the restore.

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.