general

Cloud Backup Failed

Resolution Checklist

  • 1 Understand Cloud Backup Failures
  • 2 Resolve Windows VSS and Network Issues
  • 3 Fix macOS Backup Daemons and APFS Conflicts
  • 4 Optimize Client Configuration and Folder Inclusion
  • 5 Summary Quick Reference Checklist

Cloud Backup Failed

A “Cloud Backup Failed” message or warning icon indicates that the automated backup process of the client (such as OneDrive Backup, Google Drive Desktop Sync, Dropbox Backup, or Backblaze) has terminated unexpectedly or cannot start. This leaves local documents, desktop files, or system folders unprotected.

This guide provides troubleshooting procedures and commands to resolve database lockouts, service failures, and file system blockages on both Windows and macOS.


1. Primary Causes of Cloud Backup Failures

Common triggers for cloud backup failures include:

  • Volume Shadow Copy (VSS) Failures (Windows): The service that takes snapshots of open files before backup crashes or becomes misconfigured.
  • APFS Snapshot or Disk Permissions Errors (macOS): macOS security constraints or file system database errors prevent background daemons from reading files.
  • Insufficient Cloud Storage: The backup payload exceeds the remaining storage quota in your subscription tier.
  • Service Daemon Crashing: Background client engines crash because of circular symbolic links, corrupted cache databases, or locked databases.

2. Resolve Windows VSS and Network Issues

On Windows, cloud backup clients rely heavily on the Volume Shadow Copy Service (VSS) to copy files that are currently open in other applications.

A. Reset the Volume Shadow Copy (VSS) Services

If VSS is stalled, backups of system-linked folders (Desktop, Documents, Pictures) will fail.

  1. Search for Command Prompt in the Start Menu, right-click, and select Run as Administrator.
  2. Run the following commands to restart and register VSS dlls:
    :: Restart VSS and system provider services
    net stop vss
    net start vss
    net stop swprv
    net start swprv

B. Verify VSS Writer Health

Verify that VSS writers are in a stable, non-failed state:

vssadmin list writers

If any writers show “State: [9] Failed” or “Last error: Retryable error”, restart your computer to release the locked writers.

C. Repair System File Corruption

Corrupted system files can block cloud backup hooks. Run the System File Checker:

sfc /scannow

3. Fix macOS Backup Daemons and APFS Conflicts

On macOS, backup daemons must navigate FileVault encryption, sandbox containers, and APFS snapshot locks.

A. Force Restart System Backup and Cloud Daemons

If your cloud client backup process is frozen, terminate it to force macOS to launch a clean daemon instance:

  1. Open Terminal (via Spotlight).
  2. Run the following command (adjust application process name as needed):
    # Kill cloud storage helper and file provider services
    killall FileProviderDomains; killall -9 "Google Drive"; killall -9 "OneDrive"

B. Clear System Cache Database for File Provider

Sometimes the macOS FileProvider database becomes corrupted, halting cloud backups. Reset it:

# Force macOS to rebuild the FileProvider database
sudo killall -9 fileproviderd

C. Check APFS Disk Container Health

Use the command line disk utility to scan and repair APFS directory trees that could be blocking backups:

# Check filesystem consistency without unmounting
diskutil verifyVolume /

If errors are found, reboot into macOS Recovery Mode (Cmd + R at boot) and run Disk Utility First Aid.


4. Optimize Client Configuration and Folder Inclusion

To prevent backup failures from recurring, adjust client settings to handle heavy payloads.

Exclude Large Cache Files and Virtual Machines

Most backup clients fail when attempting to sync volatile, active files like VM disks (.vhdx, .vmdk), local databases (.sql), or developer dependencies (node_modules).

  1. Open your cloud client Preferences.
  2. Under Sync Options or Backup, locate exclusions/selective sync.
  3. Exclude directories containing node modules, build targets, or heavy cache files.

5. Summary Quick Reference Checklist

Action TargetOperating SystemTerminal Command / PathExpected Outcome
Restart VSS ServiceWindowsnet stop vss && net start vssRestores ability to back up open or locked files.
Check VSS WritersWindowsvssadmin list writersPinpoints VSS failures blocking backup agents.
Kill Cloud DaemonsmacOSkillall FileProviderDomainsForce-quits stalled system sync engines.
Verify Disk IntegritymacOSdiskutil verifyVolume /Evaluates disk format errors blocking file reads.
Run System ScanWindowssfc /scannowRestores corrupted system DLLs required for backup.
Exclude Temp FilesWindows/macOSClient PreferencesPrevents locks on volatile system or database files.