Skip to main content

Backup Status Page

CloudM Backup

Understanding the Backup Status Page

Overview

The Backup Status page gives administrators a centralised view of all backup activity across their Google Workspace environment. Monitor user and Shared Drive backups, review history, identify failures, and take corrective action from a single screen. The page header always shows two key stats: Users with backup policy (assigned vs. total) and Total data storage used.

๐Ÿ“Œ  Chat backup was added in Release 1.10 (August 2025). Navigate to: Backup > Backup Status.

Navigating the Status Page

The page has two tabs โ€” User Backups and Shared Drives. Each tab shows the latest backup for every item, including Policy assigned, Latest Backup date/time per data type, and Status. Clicking any row opens a detail panel on the right showing the full backup history log, per-data-type initial backup summary, and Retry / Accept action buttons where applicable.

Filters

Filters apply to both tabs and can be combined. The Status filter lets you select all statuses or choose a specific one:

  • Search โ€” filter by email address (Users) or Shared Drive name.
  • Status โ€” select all, or filter by a specific status. To use bulk retry, you must select the Failed Initial Backup status.
  • Policy โ€” filter by assigned backup policy.
  • OU โ€” filter by Organisational Unit.

Backup Status Reference

The Status column reflects the most recent backup outcome per data type.

StatusDescription
CompleteThe backup for this data type finished successfully with no errors.
In ProgressA backup is currently running for this data type.
FailedThe backup encountered errors and did not complete successfully.
PausedThe backup policy for this data type has been paused by an administrator.
PendingThe backup is queued and waiting to start.
UndefinedNo backup has been attempted yet for this data type, typically when only one data type has been backed up so far.
PartialThe backup completed but with some items not backed up successfully.
๐Ÿ’ก  Release 1.9+ introduced more granular status filter options on the User Backups tab.

Auto retry failed Initial Backups after 24 hours

๐Ÿ†•  Introduced in CloudM Backup v1.12 (10th March 2026).

CloudM Backup will automatically retry a failed initial backup after 24 hours, provided no manual intervention has taken place. This reduces the need for administrators to monitor and manually resubmit failed jobs, while still giving administrators the ability to take control when needed.

This behaviour is handled in the backend and runs silently โ€” no notification is shown on the Backup Status page when an auto retry takes place.

How Auto Retry Works

When an initial backup job fails, CloudM evaluates whether a retry should be scheduled automatically. The following logic applies:

  • If the job fails and no manual action is taken, an auto retry will be triggered after 24 hours.
  • If the job fails and an administrator manually intervenes (e.g. retries or accepts via the UI), the auto retry is cancelled. Manual action always takes precedence.
  • If the job cannot be retried due to a blocking error, no further attempts will be made. The sidebar will update to indicate that no future attempts will be submitted, and the logs will record the reason for the failure.
  • If a user is assigned a new or different policy, a fresh initial backup is triggered regardless of the previous state.

Scenario Reference

ScenarioBehaviour
Policy triggers initial backupBackup job runs automatically when a policy is assigned.
Job fails, no manual interventionAuto retry is scheduled and will run after 24 hours.
Job fails, manual intervention takenAuto retry is cancelled. Manual action takes precedence.
User changes policyA new initial backup is triggered regardless of previous state.
Retry cannot proceedNo further attempts will be made. The sidebar updates to reflect this and the logs record the reason.

What Administrators Will See

Auto retry runs silently in the background. The following applies to visibility on the Backup Status page:

  • No notification or indicator is shown on the Backup Status page when an auto retry has taken place.
  • If a retry cannot proceed, the sidebar will update to confirm no further attempts will be made.
  • The backup logs will always record the reason a job has failed, providing an audit trail for investigation.
โš ๏ธ  Note: Auto retry activity is intentionally not surfaced on the Backup Status page. If you need to confirm whether a retry has occurred, refer to the backup logs in the user detail panel.

Retry, Accept & Bulk Retry

Retry and Accept (Individual)

Retry and Accept buttons appear in the detail panel only when an initial backup completed with errors. Retry triggers a new initial backup attempt. Accept acknowledges the failure and allows delta backups to proceed from the next scheduled run โ€” use this when a retry is not appropriate.

Bulk Retry for Failed Initial Backups

When multiple initial backups have failed, you can retry them all at once. A failed initial backup blocks delta backups from starting and marks the overall job as failed.

  1. Apply the Initial Failed Backups filter.
  2. Select items individually, or check the header checkbox to select all.
  3. Click Retry Backup โ€” the button shows a live count of selected items. Use Clear Selection to start over.
  • Bulk retry uses the same logic as a manual retry and applies to initial backups only.
  • Certain error types will block continuous retries. Contact CloudM Support for guidance on specific error codes.
๐Ÿงช  CloudM Labs Feature: Bulk retry was introduced in CloudM Backup v1.12 (Due in March 2026). Enable it via the Settings tab in CloudM. Feedback is welcome via the same route.

Exporting to CSV

๐Ÿ†•  Introduced in CloudM Backup v1.12 (10th March 2026).

Backup status data can be exported to CSV from either tab, capped at 10,000 rows. The export respects all active filters โ€” verify your filters before exporting to ensure the file matches what you see on screen.

Permissions

  • User Backups tab โ€” Export button visible to users with Global Restore permission.
  • Shared Drives tab โ€” Export button visible to users with Global Restore Shared Drives permission.
  • The button shows or hides automatically when switching tabs based on your permissions.

How to Export

  1. Apply filters to scope the data, then click Export.
  2. Choose Export via Email (CSV sent to your account address) or Export to Drive (file saved to Google Drive). An email is generated for both options.
โ„น๏ธ  If the Export button is not visible, your role may not include the required permission for that tab. Contact your CloudM administrator.

 


 

Was this article helpful?
0 out of 0 found this helpful