Why Is My Backup Not Running or Taking So Long?
Open Overview for the affected domain, then History > Backup History. Note the most recent start time, result, and error message. This separates a job that never started from a running job or one that finished with errors.
There Is No Recent Backup
Check the following with your administrator:
- Server: The computer running JitBackup is powered on, awake, and its service is running. Closing your browser is fine; a sleeping or stopped server cannot run scheduled backups.
- Schedule: The domain's backup interval was saved and the next backup time is what you expect. A weekdays-only schedule will not run on weekends.
- Existing job: A new backup does not start until the previous one finishes.
- Coverage: The required users and apps are enabled, and Shared Drives are selected separately.
- Subscription: Overview has no expired trial, expired license, invalid license, or user allowance message preventing backup.
Once the cause is resolved, use Backup on Overview to start a job and verify its result. Saving settings alone is not enough. See Backup scope and schedule.
The Backup Is Running but Slow
The first backup has more data to collect. Large mailboxes, many small files, changed files, Google request limits, and storage or network speed can all affect duration. There is no fixed completion time that fits every organization.
Check whether progress and job details are changing before cancelling. Ask IT to examine the backup server's network connection, disk activity, free space, and access to the storage provider. A website loading normally on your laptop does not confirm that the backup server can reach Google or write backups.
Avoid repeatedly stopping the service to refresh a slow-looking page. Refresh the console first. If progress remains unchanged and errors repeat, record the time and message for investigation.
The Job Reports Errors
Click the error count in Backup History to identify the affected user or Shared Drive, app, and message.
| Error wording or symptom | Next check |
|---|---|
| Unauthorized, forbidden, invalid scope, or permission denied by Google | Ask the Workspace administrator to check service account authorization, required APIs, and access to the affected account or item |
| Account suspended, deleted, or service unavailable for the user | Ask the Workspace administrator to check that user's status and access to the relevant Google service |
| Rate limit, quota exceeded, or too many requests | Ask IT to identify the named Google or storage quota and review load; do not start repeated jobs while the limit persists |
| Timeout, connection failure, or name resolution failure | Check the backup server's network, proxy, DNS, and access to the named service |
| Access denied to storage or a path | Check the configured storage credentials and the permissions used by the JitBackup service |
| Disk full or insufficient storage | Check both the local index disk and the backup destination |
| Invalid or expired license | Review the subscription message on Overview and follow the licensing FAQ |
The same HTTP status can have different causes. Keep the complete error text and the service that produced it; a bare 403 does not identify the fix.
After Fixing the Cause
Run another backup, check the affected user and app, and browse or export a sample item. Keep any previously usable recovery points while investigating. For repeated errors, use What to include when asking for help.