Support Case #9856 - Silverline Brands Backup Window Exceeded
Support will escalate Silverline backup issue and push agent update before follow-up call
Dominic Flores reported nightly backup jobs running up to five hours past their 1-5 AM window for two weeks, causing performance degradation during business hours. David Kim found SQL backups averaging eight hours with throughput down from around 800 MB/s to 180-220 MB/s. He suspected backend routing changes from an Aegis Detect incident and will escalate to Protect engineering as P1. David will deploy agent 4.2.0, adjust backup priorities, and set an alert, with a follow-up call scheduled for tomorrow at 10 AM Central.
How the call went
Customer expressed frustration over slow response and unresolved backup issue, though call ended with constructive agreement on next steps.
Opening
-1Close
011 scored turns of 41. Hover a point for the model's reason, or read the transcript.
How the conversation ran?Talk share is measured from speech time in the captured portion of the transcript.
- Questions we asked
- 14
- Questions they asked
- 7
- Turns
- 41
- Longest silence
- 1s
Who was on the call
AegisCloud
Customer
- Dominic Flores?Matched on an initial rather than a full name, so attribution is weaker.
What happened8
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Issue raised3?A problem was brought up on the call.
Dominic reports nightly backups running well past their scheduled window for two weeks, causing production slowdowns.
Dominic says the backup window is 1-5 AM but jobs now run until 9-9:30 AM, with SQL Server instances the worst offenders.
David identifies a throughput collapse on SQLPROD01, from about 800 MB/s to 180-220 MB/s, and notes the backup duration averaging eight hours.
Commitment2?Someone committed to doing something.
David apologizes for the slow response and commits to escalating to Protect infrastructure as a P1.
David will deploy agent 4.2.0 within the hour, adjust priority settings, set an alert, and book a 10 AM follow-up with an engineer.
Decision1?A decision was reached.
Dominic agrees to deprioritize file-server backups so SQL workloads get more bandwidth tonight.
Risk1?A risk to the account, project, or system was surfaced.
David suspects backend routing changes from an Aegis Detect incident may be affecting backup transfer paths; Dominic finds this alarming.
Recap1?A summary of what was agreed.
Dominic says he is still frustrated but appreciates the transparency; confirms tomorrow's call.
What was promised6
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Escalate case to Protect infrastructure team as P1 and confirm whether backend routing changes caused throughput drop | David KimAegisCloud | 12 Apr 2026said “today” | escalate case?Raise the priority or visibility of a ticket, case, incident, or request to a higher-tier team, manager, or leadership, including P1/P2 designation and formal escalation paths. | ||
| Deploy backup agent 4.2.0 as a manual deployment via console | David KimAegisCloud | 12 Apr 2026said “within the hour” | engineering or configuration change?Implement, deploy, fix, configure, activate, enable, migrate, backfill, or decommission a product, system, or infrastructure, including code changes and environment configuration. | ||
| Adjust backup job priorities and throttle lower-priority file-server jobs to prioritize SQL workloads | David KimAegisCloud | 12 Apr 2026said “now” | engineering or configuration change?Implement, deploy, fix, configure, activate, enable, migrate, backfill, or decommission a product, system, or infrastructure, including code changes and environment configuration. | ||
| Set an alert so David is paged if SQL job duration exceeds six hours | David KimAegisCloud | No date given | engineering or configuration change?Implement, deploy, fix, configure, activate, enable, migrate, backfill, or decommission a product, system, or infrastructure, including code changes and environment configuration. | ||
| Send calendar invite for follow-up call tomorrow at 10 AM Central with a Protect platform engineer | David KimAegisCloud | 12 Apr 2026said “within the next 30 minutes” | schedule session?Arrange, coordinate, or block time for a meeting, call, demo, working session, or walkthrough, including inviting participants and confirming attendance. | ||
| Check in on tonight's backup run tomorrow morning before the follow-up call | David KimAegisCloud | 13 Apr 2026said “tomorrow morning before our call” | follow up?Check on the status of a prior action, open question, or pending deliverable, or chase and reconnect with someone to keep an item moving. |
Left unanswered2
Did backend network routing changes from the Aegis Detect incident cause the backup throughput drop?
AegisCloudIncident ResponseWill the 4.2.0 agent update fully resolve the throughput issue?
AegisCloudIncident Response
Themes and issues5
What the call was about, and the specific issue recorded under each theme.
| Theme | As the model phrased it?The wording the model used before mapping it to the shared taxonomy. | Issue | |
|---|---|---|---|
| Backup & Recovery?Calls about backing up data and restoring data after loss or corruption. | backup | backup window exceeded | |
| Reliability?Calls about overall system reliability, availability, resilience, capacity, and performance, excluding specific outages or incident response. | performance | backup throughput drop | |
| Support?Calls about customer support interactions, escalations, workarounds, and support experience. | support | slow initial response | |
| Incident Response?Calls about detecting, responding to, and reviewing incidents, including post-mortems and root cause analysis. | incident | backend routing changes | |
| other?No shared value fits; the raw string is preserved in the fact table. | agent | backup agent version outdated |
Numbers stated on this call6
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Backup throughput before regression | “around 800 megabytes per second” | throughput | David Kim | |
| Backup throughput after regression | “around 180 to 220” | throughput | David Kim | |
| Average SQLPROD01 backup job duration over last ten days | “about eight hours over the last ten days” | duration | David Kim | |
| Backup overrun into business hours | “four to five hours of overage” | duration | Dominic Flores | |
| Duration issue has been occurring | “about two weeks” | duration | Dominic Flores | |
| Alert threshold for SQL backup job duration | “six hours” | threshold | David Kim |
Coaching4
How the AegisCloud side handled the call.
Strengths (4)
Acknowledged the slow initial response and apologised directly instead of deflecting.
Asked targeted diagnostic questions to isolate affected workloads and backup type.
Moved to concrete action: P1 escalation, agent update, priority adjustments, alert, and scheduled engineering follow-up.
Shared suspected internal cause transparently before confirming it.
Improvement notes (0)
Nothing recorded.
How far to trust this call
Every fact above was extracted from the captured portion of the transcript only.
10 min captured of 28 min stated. Anything said in the remaining 18 min is absent from this page.
0 turns flagged low-confidence.
- Clocks unaligned(warning)
1 participant(s) speak before joining — transcript and events are on different clocks. Do NOT derive absolute timestamps by joining these two sources.
- Partial transcript(warning)
transcript covers 34.1% of a 28.4min meeting; 17.9min after the final turn is unaccounted for
The model's own note: Transcript covers only a 10.3-minute segment of the support call; partial transcript may omit start or end. No competitor mentions.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 23,088 tokens