Back up Microsoft SQL Server

Full, differential and transaction log backups, with restore to any minute.

The agent backs up SQL Server databases with SQL Server's own backup commands, so every restore point is a normal .bak or .trn backup — stored encrypted in Beyond Cloud Vault.

Supported: SQL Server 2012 and newer, every edition including Express. Each instance on the computer (default and named) is found automatically.

1. Give the agent access to SQL Server

The agent runs as the Windows Local System account. SQL Server must allow it to make backups. Choose one of the two options.

Option A — one click (recommended). Open Beyond Cloud Backup → Databases. If an instance shows no access, click Allow Beyond Cloud to back up this SQL Server. You need to be an administrator of SQL Server; Windows asks for permission once.

Option B — in SQL Server Management Studio. Connect as a sysadmin and run:

IF SUSER_ID(N'NT AUTHORITY\SYSTEM') IS NULL
    CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS;
ALTER SERVER ROLE [sysadmin] ADD MEMBER [NT AUTHORITY\SYSTEM];

Then reopen the Databases page: the instance should show connected.

Using a SQL login instead? Click Use a SQL login next to the instance and enter a login with the sysadmin role, then Save and test. The password is stored encrypted on the computer.

2. Check the recovery model

Transaction log backups — and restoring to a precise minute — need the database to use the FULL recovery model. The Databases page shows each database's model.

To switch a database to FULL:

ALTER DATABASE [YourDatabase] SET RECOVERY FULL;

Databases in SIMPLE recovery are still protected with full and differential backups; only log backups are skipped.

3. Create the backup

1. Go to Backup → SQL Server · your instance.
2. Leave All user databases checked (new databases are included automatically) or pick specific ones.
3. Choose the schedule. A good start:
   • Full — every Sunday at 22:00
   • Differential — every day at 21:00
   • Transaction log — every 15 minutes
4. Choose how long to keep restore points, then Save.

Good to know

• The backup file is written to SQL Server's own backup folder first, then stored in Beyond Cloud Vault and removed. Leave free space in that folder about the size of your largest database.
• Don't run another product's log backups on the same databases — two tools taking log backups break each other's chain.
• To restore, see Restore a database to a point in time.