SaBackup vs. Competitors: Features, Pricing, and Performance

SaBackup Troubleshooting: Common Issues and Quick Fixes

1. Backup jobs fail to start

• Likely causes: Scheduler disabled, service not running, corrupt job configuration.
• Quick fixes:
  1. Ensure the SaBackup service is running (restart if needed).
  2. Verify scheduler settings and system time sync.
  3. Recreate the job from a known-good template.

2. Backups complete but files are missing

• Likely causes: Exclusions set, file locks, permissions, incremental snapshot problems.
• Quick fixes:
  1. Check job include/exclude filters and remove unintended exclusions.
  2. Run backup with file-level logging to identify skipped files.
  3. Ensure backup account has read access to all source files.
  4. For locked files, enable VSS (or SaBackup’s snapshot option) or quiesce applications before backup.

3. Slow backup performance

• Likely causes: Network congestion, disk I/O bottleneck, CPU/memory limits, inefficient retention or encryption settings.
• Quick fixes:
  1. Run a network speed test and schedule backups during off-peak hours.
  2. Check source and target disk health and I/O metrics; move target to faster storage if needed.
  3. Reduce concurrency or adjust thread counts in SaBackup settings.
  4. Temporarily disable heavy encryption/compression to compare throughput.

4. Authentication or permission errors

• Likely causes: Changed passwords, expired service account, insufficient privileges.
• Quick fixes:
  1. Confirm service/account credentials and re-enter them in SaBackup.
  2. Grant required privileges (read/list for sources; write/create for targets).
  3. If using domain accounts, ensure the machine is domain-joined and time sync is correct.

5. Repository or target storage full

• Likely causes: Retention/cleanup misconfiguration, logs accumulating, multiple full backups retained.
• Quick fixes:
  1. Review retention policies and run immediate cleanup if safe.
  2. Archive older backups to secondary storage.
  3. Increase target capacity or enable deduplication to save space.

6. Corrupted backup sets or failed restores

• Likely causes: Interrupted writes, hardware errors, software bugs.
• Quick fixes:
  1. Validate backups after completion using SaBackup’s integrity check.
  2. Attempt restore to an alternate location to rule out target issues.
  3. If corruption persists, isolate faulty storage and replace hardware.

7. Alerts or notifications not received

• Likely causes: SMTP settings wrong, webhook endpoints blocked, alert rules misconfigured.
• Quick fixes:
  1. Test SMTP/webhook configuration from SaBackup settings.
  2. Check firewall rules and allowlist SaBackup IPs or endpoints.
  3. Review alert thresholds and ensure notification templates are enabled.

8. Incremental backups growing unexpectedly

• Likely causes: Changed file timestamps, synthetic full failures, snapshot/manifest drift.
• Quick fixes:
  1. Run a manual full backup to reset the chain.
  2. Check for processes touching files and adjust backup filters.
  3. Review SaBackup’s incremental settings and manifest health.

9. Encryption key or passphrase lost

• Likely causes: Key not exported, admin turnover, mismanaged key vault.
• Quick fixes:
  1. Restore key from secure backup or key management system.
  2. If key is irretrievable, recover from unencrypted copies or archived exports.
  3. Implement key rotation and centralized key vault for future safety.

10. UI is unresponsive or web console errors

• Likely causes: Service crash, database lock, resource exhaustion, browser caching.
• Quick fixes:
  1. Restart SaBackup services and associated database.
  2. Clear browser cache or try an alternate browser/incognito mode.
  3. Inspect logs for exceptions and apply relevant patches or hotfixes.

Preventive checklist

• Enable daily integrity checks and periodic full backups.
• Monitor storage, I/O, CPU/memory, and network metrics.
• Keep SaBackup and OS patched; subscribe to release notes.
• Maintain documented service-account credentials and key backups.
• Test restores quarterly and log outcomes.

When to contact support

• Persistent corruption, hardware failure, or bugs after updating.
• Repeated authentication failures after credential/permission checks.
  Provide SaBackup version, logs (last 24 hours), job IDs, and error messages when opening a ticket.