Free SQL Server tool

Backup RPO and RTO calculator

Estimate how long the entered restore sequence takes, whether routine log backups fit the RPO, and how much retained backup storage the schedule uses.

Use real measurements

Use compressed backup sizes from msdb.dbo.backupset and restore throughput from a completed restore test. Guessed throughput cannot validate an RTO.

Recovery inputs

Use measured backup sizes and restore speed

Enter compressed sizes from backup history and throughput from a real restore test. Zero network speed means local or already included in the measured rate.

Recovery model

Target RPO

min

Log backup interval

min

Target RTO

min

Full backup size

Differential in sequence

Log chain in sequence

Measured restore rate

MB/s

Network limit (optional)

Mb/s

Files in restore sequence

Overhead per file

sec

Validation and cutover

min

Retention

days

Full backup every

days

Daily log backups

Daily differential

Planning estimate

Compare the estimated recovery with the targets

This calculation covers the entered restore sequence and explicit overhead. A restore drill is still the validation step.

Estimated RTO

85.9 min

Inside target

Routine RPO

10 min

Inside target

Effective throughput

180.0 MB/s

Restore data

600.0 GB

Data-copy time

56.9 min

Retained backup storage

1972.0 GB

2 retained full backups in the estimate

The estimate excludes media discovery, server provisioning, queueing, human decisions, and unexpected recovery work unless those minutes are included in validation and cutover time.

Generated output

SQL Server recovery planning estimate
Recovery model: full
Restore sequence data: 600.00 GB
Effective throughput: 180.00 MB/s
Estimated data-copy time: 56.9 minutes
Estimated sequence overhead: 4.0 minutes
Validation and cutover: 25.0 minutes
Estimated RTO: 85.9 minutes (target 120.0)
Estimated routine RPO: 10 minutes (target 15.0 minutes)
Estimated retained backup storage: 1972.0 GB over 14 days

Planning result only. Confirm it with a complete restore drill and application validation.

What the calculator includes

The restore estimate adds the full backup, the latest selected differential, and the log chain after that differential. It divides the total compressed size by the lower of the measured restore rate and the optional network limit, then adds per-file handling and validation or cutover time.

The routine RPO is the entered transaction-log backup interval for full or bulk-logged recovery. Simple recovery needs a different RPO discussion because transaction-log backups are not available for point-in-time restore. The storage result is a transparent schedule estimate; it does not include copies, object-store minimum retention, immutability overhead, or temporary restore space.

Use the correct restore sequence

Under the full recovery model, a typical sequence is the base full backup, the latest differential based on that full backup when one is used, and every required log backup in order. A tail-log backup may be needed when the source database is accessible and the recovery point requires it.

Microsoft documents this sequence in Plan and perform restore sequences. Backup history exposes backup start, finish, type, size, and compressed size. Compression ratios vary, so measured compressed size is a better planning input than a generic ratio.

Validate the estimate with a restore drill

A useful drill restores onto infrastructure that resembles the recovery target, replays the complete backup chain, checks database consistency where required, validates application access, records manual waiting time, and confirms who can make the cutover decision.

Continue with the SQL Server recovery guide, the recovery runbook checklist, and the backup review guide.