SupInsight Logo SupInsight by Jumborca
AI Service Connected
JD
John Doe

AI Analysis

Comprehensive AI-powered insights for your backup infrastructure

Last analyzed: April 13, 2025 08:45 AM

Analyzed Tasks

148 +23 this week

Detected Anomalies

7 ↑ 2 from last week

Prediction Accuracy

94.3% ↑ 1.7%

Active Monitors

12 All systems

Backup Performance Analysis

Error Pattern Analysis

VSS Writer Failures
42% (↑12%)
Network Connectivity
28% (↓5%)
Storage I/O
18% (↑3%)
Other Errors
12% (↓2%)

Root Cause Identification

Exchange-Incremental Backup Failure

VSS Writer timeout during snapshot creation. This issue has occurred 3 times in the past week.

AI Root Cause Analysis:
  • Microsoft Exchange VSS Writer service instability
  • Insufficient timeout value in registry (currently set to 10 minutes)
  • Large transaction logs accumulation (>50GB)

VM-Cluster-Daily Warning

CBT (Changed Block Tracking) inconsistency detected. Full backup recommended.

AI Root Cause Analysis:
  • Storage vMotion operation performed during backup window
  • VMware ESXi host 4 underwent maintenance during CBT initialization
  • Snapshot consolidation failed on 2 VMs in the cluster

Anomaly Detection

Detected Anomalies

  • Apr 10, 2025 - Unusual backup duration spike

    SQL-Daily-Full backup took 3.2x longer than average

  • Apr 8, 2025 - Unexpected storage consumption

    FileServer-Nightly backup size increased by 45% without changes

  • Apr 5, 2025 - Network throughput degradation

    Transfer rate dropped by 32% on vbr-dr-02 server

Resource Utilization

CPU Usage 65%
Peak: 87% during SQL backup
Memory Usage 78%
Peak: 92% during parallel jobs
Network I/O 42%
Peak: 76% during replication
Storage I/O 83%
Peak: 98% - bottleneck detected

Predictive Maintenance Timeline

Critical: Storage Repository Capacity

Estimated: 3 days

Primary backup repository projected to reach 95% capacity in 3 days based on current growth rate. Immediate action required.

Confidence: 96%

Warning: Exchange VSS Writer

Estimated: 7 days

Exchange VSS Writer predicted to fail within 7 days based on increasing error frequency pattern. Preventative maintenance recommended.

Confidence: 87%

Notice: VM-Cluster Backup Window

Estimated: 14 days

VM-Cluster-Daily backup window projected to exceed allocated time within 2 weeks due to VM growth. Consider job splitting or optimization.

Confidence: 82%

AI Analysis Configuration

Analysis Sensitivity

Error Detection Threshold Medium
Low High
Anomaly Detection Sensitivity High
Low High
Prediction Confidence Minimum 75%
50% 99%

Analysis Features

Analysis Schedule

Analysis Frequency

AI Insights

Real-time Notifications

Live

Storage repository repo-01 filling faster than expected. Current growth rate: 8.7% daily.

2 minutes ago

Network throughput anomaly detected on vbr-dr-02 during replication jobs.

18 minutes ago

Optimization applied: Backup window for SQL-Daily-Full reduced by 18% after schedule adjustment.

42 minutes ago

Priority Recommendations

Critical: Storage Expansion

Add minimum 2TB to primary repository within 72 hours to prevent backup failures.

High: Exchange Maintenance

Schedule Exchange maintenance window to restart services and clear transaction logs.

Medium: VM Backup Job Split

Split VM-Cluster-Daily into two separate jobs to optimize backup window.

Risk Assessment

Overall Backup Risk Medium
Storage Capacity
High (82%)
Job Reliability
Medium (58%)
Recovery Readiness
Low (24%)

Historical Trends

Success rate trend over past 90 days

Configuration Suggestions

Optimize SQL backup compression level
Increase network throttling during peak hours
Implement synthetic full backups for large VMs