Skip to content
BackupTool.com
PLATFORM / READ THE SIGNAL

Every status should tell you
what to do next.

Explore the observations in your workspace. Each one tells you something different about a backup job.

YOUR STORAGE.
YOUR CONTROL.
INTERACTIVE / SIGNAL EXPLORER

Same site. Different evidence.

Select an observation to see what it tells you and where to investigate next. This is an illustrative scenario.

ILLUSTRATIVE SITE / OAK & COReported success
Client siteMonitoring hub

A job completed, according to your backup plugin.

The connector delivered a signed completion report. Your job history records the reported result and completion time.

What this does not establish

It does not prove that an archive exists in storage or that a restore will work.

NEXT ACTION

Review archive evidence separately and record the outcome of a restore test you perform.

Portfolio visibility

Review the sites in your private account with their monitoring expectations and latest reported results.

A history with context

Retain job observations, source and reported size when supplied. Generate readable site histories.

Recovery records

Keep the date, archive reference, outcome and limitations of a test your customer performed.

PAGE-SPECIFIC ANSWERS

What does a status establish?

What makes a heartbeat different from a job report?

A heartbeat records connector contact. Only a backup-job report updates the last backup time and reported result.

Can a reported success prove recovery?

No. Check the archive separately and perform a restore test. Customer-entered test records document your work; BackupTool does not perform the test.

FROM EXPLORATION TO YOUR WORKFLOW

See the workspace in action.

Explore a labelled sample portfolio before connecting a real site.

Explore the demonstration