[Failed] BIRGIT-DELL - Friday, 23 October 2026 10:47:02
TRM Supplies cc
Jordan
critical
Escalate
Critical
0.8h estimated
Summary
Veeam Endpoint Backup failed on BIRGIT-DELL workstation on 2026-10-23 at 10:47; user is out of country until 2026-11-06.
Root cause
Cannot determine without full Veeam error message; truncated note prevents visibility into actual failure. Likely candidates: network unavailability (user travelling), agent service failure, insufficient backup destination space, or endpoint offline. Recurring pattern (July 13 and Oct 23 on same machine) suggests either persistent infrastructure issue or machine-specific configuration problem.
Progress
2026-10-23T10:51: Alert forwarded to ticket system with Veeam error details (truncated). 2026-10-23T12:36: Noted that user is out of country with re-arm date 2026-11-06T16:17. No technical troubleshooting steps logged.
Remaining work
Retrieve and review full Veeam error message from truncated note to identify specific failure reason. 2. Determine if BIRGIT-DELL is network-reachable or offline. 3. Check Veeam agent service status and logs on BIRGIT-DELL remotely if possible. 4. Resolve identified cause or defer remote actions until user returns on 2026-11-06. 5. Verify backup succeeds to trigger auto-closure per ticket system configuration.
20261023-17
[Cloud-09 | Octagon] Alert: Low free disk space
Octagon Business Solutions (Pty) Ltd
Jordan
critical
Escalate
Medium
1.0h estimated
Summary
Kerio Control firewall (Cloud-09) /logs directory critically low on free space (10.43 MB remaining)
Root cause
Log files in /logs directory on Kerio Control firewall have accumulated to near-capacity with only 10.43 MB free remaining. Most probable causes: (1) log rotation disabled or misconfigured, (2) excessive logging due to firewall misconfiguration or high-volume traffic, or (3) logs not cleaned up over extended retention period.
Progress
No prior work logged.
Remaining work
Immediately investigate and remediate disk space on Cloud-09 firewall /logs directory
Identify which logs are consuming space and verify log rotation configuration
Archive or safely delete old logs to restore safe free space threshold (minimum 1 GB recommended)
Verify firewall continues logging new events and services remain stable
Implement or repair log rotation policy to prevent recurrence
Root-cause why account has experienced three space-exhaustion tickets in seven days (20261016-4, 20261012-12, this ticket)
Veeam backup job for ChrisPretoriusLPT workstation failed on 24-Oct at 07:49:43; truncated failure details prevent root cause determination.
Root cause
Cannot determine — critical failure details are truncated. However, the pattern of recurring backup failures across three separate workstations (ChrisPretoriusLPT, STIANLPT, CharlJansenVanRensburgLPT) in past 10 days suggests infrastructure-level issue (repository connectivity, storage capacity, network/firewall blocking, or Veeam service unavailability) rather than workstation-specific problem.
Progress
2026-10-24: Automated LISA Backup Check v4.0 detected failure and created ticket assigned to Jordan. No manual investigation or time entries logged yet.
Remaining work
Review full truncated note containing Veeam error details/log output from backup job
Check Veeam backup repository connectivity and available storage space
Verify backup destination is reachable from ChrisPretoriusLPT workstation (network/firewall)
Confirm Veeam Agent service status and health on affected workstation
Cross-check recent infrastructure changes (network, storage, firewall rules) given pattern of recurring failures
Determine if issue is workstation-specific or account-wide infrastructure problem
20261023-21
Spanning Backup for Office 365 - Daily Backup Summary for Octagon Business Solutions
RITO Technologies
Jordan
critical
Needs human
Critical
0.8h estimated
Summary
Spanning Backup for Office 365 has failed three consecutive days (Oct 23-25) for Octagon Business Solutions; automated ticket filed but specific error messages are truncated in available notes.
Root cause
Cannot determine — actual error messages from Spanning notification emails are truncated. Most probable categories: (1) Office 365 credential/authentication failure, (2) backup destination connectivity/quota issue, (3) Spanning service account permissions in O365, or (4) network/DNS resolution failure. Requires review of full error logs.
Progress
No prior work logged. Ticket auto-created 2026-10-23 by LISA monitoring v4.0, assigned to Jordan. Three backup failure notifications received: 2026-10-23 18:37, 2026-10-24 18:36, 2026-10-25 18:36. No technician time entries recorded.
Remaining work
Retrieve and review full backup failure email content from Spanning (notes truncated, actual error codes/messages not visible)
Check Spanning Backup console for job status, error details, and last successful backup date for Octagon Business Solutions
Verify Office 365 connectivity and backup service account authentication status
Check backup destination storage quota and network connectivity
Review if this is specific to Octagon or part of broader account issue (other similar tickets were Completed)
20261023-22
Spanning Backup for Office 365 - Daily Backup Summary for Nkunzi Pharmaceuticals
RITO Technologies
Jordan
critical
Escalate
Critical
0.8h estimated
Summary
Office 365 backup failing for 3 consecutive days (Oct 23–25) on Nkunzi Pharmaceuticals machine; marked critical, unaddressed by technician.
Root cause
Cannot be determined; backup failure error messages are not visible due to truncated note content.
Progress
2026-10-23: Initial backup failure reported by monitoring system (LISA). 2026-10-24: Subsequent failure reported. 2026-10-25: Another subsequent failure reported. No technician work logged; ticket remains unaddressed.
Remaining work
Retrieve full backup failure error messages from Spanning backup logs (notes are truncated, preventing diagnosis)
Determine root cause category: authentication, network connectivity, quota exhaustion, Office 365 service issue, or backup client problem
Contact Nkunzi Pharmaceuticals to verify recent changes to Office 365 environment or backup configuration
Implement corrective action based on root cause
Verify successful backup completion
Route customer in BMS system (currently on default account)
20261023-23
Spanning Backup for Office 365 - Daily Backup Summary for ChilliBlu Consulting
RITO Technologies
Jordan
critical
Escalate
Critical
1.5h estimated
Summary
Spanning Office 365 backup is failing repeatedly for ChilliBlu Consulting customer, with backup failures occurring on 2026-10-23, 2026-10-24, and 2026-10-25.
Root cause
Cannot determine — diagnostic information in ticket notes is truncated. Most probable categories: (1) Office 365 permission/authentication failure for this tenant, (2) Spanning backup service connectivity issue, (3) Recurring network outage at customer site during backup window, (4) Backup agent configuration or credential corruption.
Progress
No prior work logged. Ticket created 2026-10-23 after automated backup failure alert. Three consecutive daily backup failures documented via MSPPortal notes (2026-10-23, 2026-10-24, 2026-10-25), but no technician investigation initiated. Ticket assigned to Jordan but no time entries exist.
Remaining work
Retrieve and review full backup failure logs from Spanning console (notes are truncated and actual error details are not visible)
Verify Office 365 connectivity and authentication for ChilliBlu Consulting tenant
Check Spanning backup agent status and configuration on affected workstation
Determine if this is customer-specific or part of service-wide issue (note: multiple other customers showed backup failures on 2026-10-23, suggesting possible account-level problem)
Review Spanning service status page for any ongoing incidents
If Office 365 permission issue, remediate and trigger manual backup retry
Veeam Agent backup job 'RITO-DC' has failed on three consecutive days (2026-10-23 through 2026-10-25), with no investigation activity logged.
Root cause
Cannot determine with confidence — the ticket notes are truncated and do not expose the actual Veeam error messages. Most probable causes for recurring Veeam Agent failures: (1) Agent service crashed/not running, (2) Network connectivity loss between workstation and backup repository, (3) Backup storage exhausted or offline, (4) Authentication/permissions failure, (5) License expiration.
Progress
2026-10-23 23:21: Initial backup failure alert received for Job RITO-DC (Veeam Agent for Microsoft Windows). 2026-10-24 23:36: Subsequent backup failure reported. 2026-10-25 23:21: Third consecutive failure. No technician time entries recorded; ticket remains unassigned investigation-wise.
Remaining work
Retrieve untruncated Veeam backup job logs and error codes for Job RITO-DC
Verify RITO-DC workstation is online and network-accessible
Check Veeam Agent service status (running/stopped) on the workstation
Validate backup repository/storage accessibility and free space
Confirm Veeam Agent license validity
Test backup job execution manually
Document root cause and implement remediation
Confirm successful backup completion before ticket closure
20261024-11
CRAIGCOR | Xneelo stack - Old Dev Server | 40.14
RITO Technologies
Jordan
critical
Needs human
Critical
0.8h estimated
Summary
Automated backup job failed on CRAIGCOR Old Dev Server (40.14); specific error details are truncated in the ticket notes.
Root cause
Cannot determine — the job run report containing error details and logs is truncated in the provided notes. Technical root cause is unknown without seeing the actual failure message.
Progress
2026-10-24 05:52: Automated backup check (LISA v4.0) created critical ticket reporting backup failure with job run report from 2026-10-24 08:49 UTC+3. No technician work logged.
Remaining work
Retrieve and review complete job run report from truncated note (currently cut off)
Identify specific backup failure reason (connectivity, credentials, storage, job configuration, or application error)
Verify which backup system is managing this machine (VeeAM, Spanning, or other) and check its logs
Confirm whether 'critical' designation is accurate for a dev server, and whether SLA applies
Test backup job retry and validate successful completion
20261024-12
No Backup Received - __Kratos.jhb.service-first-gp (plan Nakivo Cloud Backup) on 2026-10-23
RITO Technologies
Jordan
critical
Needs human
Critical
0.8h estimated
Summary
Scheduled Nakivo Cloud Backup for __Kratos.jhb.service-first-gp failed to run on 2026-10-23, detected by automated monitoring.
Root cause
Cannot determine root cause without investigation. Most probable: backup agent service not running on client, schedule disabled, network connectivity failure, or authentication/credential issue.
Progress
No prior work logged.
Remaining work
Verify Nakivo backup agent is running on __Kratos.jhb.service-first-gp
Check Nakivo console job history and error logs for 2026-10-23 scheduled backup
Confirm backup job schedule is enabled and configured for weekdays (Mon-Fri)
Verify network connectivity from client to Nakivo Cloud infrastructure
Check for authentication failures, credential issues, or licensing quota problems
Test manual backup trigger if configuration issues are found and remedied
Confirm backup completion and data transmission to cloud storage
20261025-2
No Backup Received - __iProfiler PC.fancourt.hot-1027 (plan Nakivo Cloud Backup) on 2026-10-24
RITO Technologies
Jordan
critical
Escalate
Critical
0.8h estimated
Summary
Nakivo Cloud Backup for IPROFILERPC failed on 2026-10-24 with indication of subsequent failure on 2026-10-25; root cause undetermined due to truncated Job Run Report.
Root cause
Cannot determine with confidence — Job Run Report is truncated. Probable causes in priority order: (1) Network/firewall blocking cloud service communication, (2) Expired or revoked API credentials, (3) IPROFILERPC offline during scheduled backup window, (4) Backup plan misconfiguration, (5) Cloud-side service degradation or quota exceeded.
Progress
2026-10-25T08:00: Automated backup status check created ticket for 2026-10-24 backup failure. 2026-10-26T05:51: Job Run Report added via MSPPortal indicating 'Subsequent backup failure' but content truncated. No technician investigation or time entries logged.
Remaining work
Retrieve full untruncated Job Run Report from 2026-10-26T05:51 note to identify specific error code/message
Verify IPROFILERPC online status and reachable during backup execution window
Check Nakivo backup agent logs on IPROFILERPC (Event Viewer, agent application logs) for 2026-10-24 to 2026-10-26
Verify Nakivo cloud API credentials are current and not expired in backup plan configuration
Test network path from IPROFILERPC to Nakivo cloud service (firewall, proxy, connectivity)
Confirm backup plan 'Nakivo Cloud Backup (id 12)' configuration is valid in Nakivo console
Run manual backup from Nakivo console to reproduce error and capture live diagnostics
Validate Nakivo cloud service status (check for incidents or maintenance)
20261025-3
No Backup Received - Andrew Payne LPT.parktown.drew-architects (plan VeeAM EndPoint Backup) on 2026-10-24
RITO Technologies
Jordan
critical
Needs human
Critical
0.8h estimated
Summary
Automated backup monitoring detected that the scheduled VeeAM EndPoint Backup failed to run on machine AndrewPayneLPT on 2026-10-24; no investigation work has been logged yet.
Root cause
Unknown pending investigation. Most probable candidates: VeeAM agent service stopped or crashed, network connectivity loss between endpoint and backup server, backup window missed due to scheduling conflict, job configuration corruption, or invalid credentials. Cannot determine root cause without agent status checks and logs review.
Progress
No prior work logged.
Remaining work
Verify AndrewPayneLPT machine is powered on and network-accessible
Check VeeAM agent service status on the endpoint
Review VeeAM agent logs and event logs for 2026-10-24 backup window to identify failure reason
Verify VeeAM agent can communicate with backup server (network connectivity, firewall rules, credentials)
Check backup job configuration in VeeAM console (verify job not disabled, schedule correct)
If agent service stopped or failed, restart it and trigger manual backup to validate fix
Confirm backup completes successfully before resolving ticket