From ab6f94b0244768a8d46a88a72afdd9e02e76d94c Mon Sep 17 00:00:00 2001 From: Ivo Oskamp Date: Sun, 8 Feb 2026 19:50:38 +0100 Subject: [PATCH] Remove Complete Workflow Example from Approving Backups Removed entire 'Complete Workflow Example' section (Day 1-15 scenario) as the stage-by-stage descriptions (Stage 1-7) are clearer and more focused. The detailed example was redundant and made the page too long. The stage descriptions already provide sufficient detail for understanding the backup review workflow. Co-Authored-By: Claude Sonnet 4.5 --- .../backup-review/approving-backups.html | 115 ------------------ 1 file changed, 115 deletions(-) diff --git a/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html b/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html index 89fb69c..6a4c320 100644 --- a/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html +++ b/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html @@ -241,121 +241,6 @@

This is especially useful for successful backups where no investigation is needed - you can quickly clear them to keep the Run Checks page empty.

-

Complete Workflow Example

- -

Here's how a typical backup review scenario unfolds using the Run Checks page (the primary daily workflow):

- -

Day 1: New Customer Onboarding

- -
    -
  1. 09:00: Customer's first Veeam backup email arrives
    2. -
  2. 09:15: Auto-import runs, email appears in Inbox
    3. -
  3. 09:30: You review Inbox, see new email from customer
    4. -
  4. 09:31: Click on email, verify it's legitimate, click "Approve"
    5. -
  5. 09:31: Select customer from dropdown, confirm
    6. -
  6. 09:31: Email disappears from Inbox, job is now active
    7. -
  7. 09:32: Job run appears in Run Checks page (unreviewed)
    8. -
- -

Day 2: First Daily Review

- -
    -
  1. 08:00: Open Run Checks page (your daily starting point)
    2. -
  2. 08:01: Customer's job shows with green "Success" badge
    3. -
  3. 08:02: Click on the run to review details (or select multiple successful runs)
    4. -
  4. 08:03: Everything looks good - click "Mark as reviewed"
    5. -
  5. 08:03: Run disappears from Run Checks page
    6. -
  6. 08:04: Continue reviewing other runs until Run Checks page is empty
    7. -
- -

Day 5: Warning Appears

- -
    -
  1. 08:00: Open Run Checks page
    2. -
  2. 08:01: Customer's job shows yellow "Warning" badge
    3. -
  3. 08:02: Click on the warning run to investigate
    4. -
  4. 08:03: Review backup objects - one VM shows "Retry succeeded"
    5. -
  5. 08:04: Read email body - retry was successful, backup completed
    6. -
  6. 08:05: Determine: This warning is acceptable
    7. -
  7. 08:05: Click "Mark as reviewed"
    8. -
  8. 08:05: Run disappears from Run Checks page
    9. -
- -

Day 8: Warning Repeats - Create Override

- -
    -
  1. 08:00: Open Run Checks page
    2. -
  2. 08:01: Same customer job shows yellow "Warning" again
    3. -
  3. 08:02: Click on the warning run - same "Retry succeeded" warning
    4. -
  4. 08:03: Decide: This will keep happening, create an override
    5. -
  5. 08:04: Go to Overrides page
    6. -
  6. 08:05: Create object-level override: -
      -
    • Job: Select this customer's job
      • -
    • Status: Warning
      • -
    • Error text contains: "Retry succeeded"
      • -
    • Treat as success: Checked
      • -
    • Comment: "Retry warnings acceptable - backup completes successfully"
      • -
    -
    7. -
  7. 08:06: Override created - return to Run Checks
    8. -
  8. 08:07: The run now shows with a blue override indicator
    9. -
  9. 08:08: Mark the run as reviewed (still required even with override!)
    10. -
  10. 08:08: Run disappears from Run Checks page
    11. -
  11. Future "Retry succeeded" warnings will show with blue badge and can be quickly marked as reviewed
    12. -
- -

Day 12: Failure Occurs - Create Ticket

- -
    -
  1. 08:00: Open Run Checks page
    2. -
  2. 08:01: Customer job shows red "Failed" badge
    3. -
  3. 08:02: Click on the failed run to investigate
    4. -
  4. 08:03: Review objects - one VM shows "Disk full"
    5. -
  5. 08:04: Determine: Customer needs to free up space
    6. -
  6. 08:05: Click "Create Ticket" in the Run Checks modal
    7. -
  7. 08:06: Fill in ticket: -
      -
    • Ticket code: CUST-789 (from PSA)
      • -
    • Description: "Backup fails - server disk full"
      • -
    -
    8. -
  8. 08:07: Ticket created - now shows 🎫 indicator on this run
    9. -
  9. 08:08: Mark run as reviewed (required even after creating ticket!)
    10. -
  10. 08:08: Run disappears from Run Checks page
    11. -
  11. 08:09: Create PSA ticket externally (or use Autotask integration)
    12. -
- -

Day 13-14: Issue Still Present

- -
    -
  1. 08:00: Open Run Checks page
    2. -
  2. 08:01: Same customer job shows red "Failed" with 🎫 indicator
    3. -
  3. 08:02: Click on run - still "Disk full" error, ticket CUST-789 visible
    4. -
  4. 08:03: No new action needed - ticket already created
    5. -
  5. 08:03: Mark as reviewed (must review each day even with active ticket!)
    6. -
  6. 08:03: Run disappears from Run Checks page
    7. -
- -

Day 15: Issue Resolved

- -
    -
  1. 08:00: Open Run Checks page
    2. -
  2. 08:01: Customer job shows green "Success" with 🎫 indicator
    3. -
  3. 08:02: Click on run - backup succeeded, disk space resolved
    4. -
  4. 08:03: Check previous runs - success for 2+ days
    5. -
  5. 08:04: Go to Tickets page
    6. -
  6. 08:05: Find ticket CUST-789, click "Resolve"
    7. -
  7. 08:06: Return to Run Checks - 🎫 indicator now removed
    8. -
  8. 08:07: Mark run as reviewed
    9. -
  9. 08:07: Run disappears - Run Checks page empty again ✅
    10. -
- -
- 💡 Run Checks is Your Daily Workflow:
- The Run Checks page is your primary daily tool - start here every morning. Daily Jobs is mainly for viewing which jobs exist and their schedules, but Run Checks is where all daily review work happens. Your goal is to have the Run Checks page completely empty by the end of your review session. -
-

Best Practices