Reading a run report
What a finished backup did: the result, six counters, four tabs, the timeline and the destination, and the three buttons that act on a list.
On this page
Every run leaves a report. If the run page is open when the run ends, it turns into the report. Later, Open report on Home's Recent activity, a row in Activity, or the job's Runs tab opens it.
The result#
| Result | Meaning |
|---|---|
| Completed | every file stored and, if verification is on, checked |
| Completed with skipped files | the run finished, but some files could not be read or stored; the Skipped and Errors tabs list them |
| Failed | the run could not finish; the banner names the error, its code and what to do |
| Stopped | you stopped it. Stopped while backing up, nothing from it is kept; stopped while verifying or applying retention, the set was complete and is kept |
| Interrupted | GBM AI or the PC stopped during the run; nothing from it is kept, and the next run starts from the last complete backup |
Beside the result: how long it took, the bytes written, the compression ratio (62% of original) and the set's folder name. Any result other than Completed has Retry, which runs the whole job again.
The six counters#
New, Updated, Unchanged, Deleted, Skipped, Errors. Unchanged is large and normal on an incremental run: those files were checked and did not need copying. Deleted counts files that were in the source last time and are gone now; they stay in earlier sets until retention removes those.
The four tabs#
| Tab | Lists |
|---|---|
| Skipped | each file that could not be read, with the reason, such as In use by another program, Access denied or Deleted or moved before it could be read |
| Deleted | files that left the source since the previous run; a long list continues in the set's gbm-ai-deleted.json |
| All changes | every file this run stored |
| Errors | the run's own error, and each file that was not stored or failed its check, such as The stored copy failed verification |
The report opens on Errors when a run has errors and nothing skipped. See Skipped files: why a run finished amber.
Under the list, three buttons act on the files in the open tab:
| Button | Does |
|---|---|
| Add a rule for these | opens the job in the wizard with an exclude rule for each listed file, to stop a noisy folder appearing in every report |
| Ask Genie why | opens Ask Genie with a question already typed, naming the job, how many files were skipped and the first file's path (for a failed run, the error code and message). Nothing is sent until you press Ask; then it uses one prompt. |
| Retry just these | a run that tries only the listed files, for example after you have closed Outlook |
Ask Genie needs a sign-in; signed out, the question is typed in for you and waits. What Genie is sent is listed in What is sent to Genie, and what never is.
This run#
The card on the right: the job, the type, the destination, the set, compression, encryption, Open files (On, Off, Off: needs administrator (the service has it), or the drives that had no snapshot: On, except T: (FAT32 and exFAT drives have no snapshots), as on an SD card or most USB sticks), Verify, and when it started and finished.
The Verify line reads OK, 2,943 files checked after a clean check, Failed when a stored file did not match, Stopped by you after 1,200 files — the rest is unverified, Nothing new was written, so nothing to verify, or Off. Verification runs on every kind of destination, S3 buckets included. See Verification failed.
Timeline and Destination#
Timeline: Queued, Started, Scanned the source, Wrote the set, Verified, Retention, Notified, Done, each with its time and how long it took.
Destination: the path, the free space after the run, the set's manifest file, what retention did (Deleted 2 old sets, freed 3.1 GB or Nothing purged), and the sets now on the destination.
The buttons at the top#
- Open folder: opens the set's folder in File Explorer.
- Export log: saves the run's full log as a text file.
- Restore from this run: opens Restore on this exact set.
Which notifications the run sent (Windows, email, webhook) is shown when you select the run in Activity: see The Activity page: every run and restore.