This page explains how to view and monitor Backup and DR jobs in the
Google Cloud console to track backup and restore status.

The jobs feature in the Backup and DR lets you view the status of
jobs, and failed backup and restore or point-in-time restore (PITR) jobs of
resources such as Compute Engine instances or Cloud SQL instances. You
can view the total number of jobs run, succeeded, failed, skipped, and
running in a particular period of time. By default, the **Jobs** page displays
jobs from the last 24 hours. You can change the time range
to 1 hour, 6 hours, 12 hours, 7 days, or 14 days. You can configure a
log-based alert to receive notifications when an alert occurs. For
instructions, see [Configure a log-based alert for vaulted
backups](https://docs.cloud.google.com/backup-disaster-recovery/docs/monitor-reports/configure-alerts-vault).

The jobs feature displays the jobs status only for data resources protected
through the Google Cloud console. If you want to view the jobs of other
resources such as Google Cloud VMware Engine, file systems, or database
resources that use appliance-based backup templates, go to the **Jobs** page
in the appliance management console. For more information, see [Monitor
jobs](https://docs.cloud.google.com/backup-disaster-recovery/docs/monitor-reports/monitor-jobs).

## Before you begin

Before you begin, ensure that you have completed the following tasks:

- [Assign permissions required to manage buckets](https://docs.cloud.google.com/logging/docs/buckets.md.txt#before-you-begin)
- [Upgrade a bucket to use Observability Analytics](https://docs.cloud.google.com/logging/docs/buckets.md.txt#upgrade-bucket)

## View backup and restore jobs

To view backup and restore jobs, including point-in-time restore jobs, do the following:

### Console

1. In the Google Cloud console, go to the **Jobs** page.

   [Go to Jobs](https://console.cloud.google.com/backupdr/jobs)
2. From the analysis section, click **Jobs**.

> [!NOTE]
> **Note:** The same dashboard displays both Backup and DR and Backup for GKE jobs.

### gcloud

To view backup and restore jobs for Backup and DR, use the following
instructions:

1. View backup and restore jobs.

   ```
   gcloud logging read 'logName=~"bdr_backup_restore_jobs"' --project=PROJECT_ID
   ```

   Add the [`--freshness` flag](https://docs.cloud.google.com/sdk/gcloud/reference/logging/read.md.txt#--freshness)
   to your command to read jobs that are more than 1 day old.

   Replace the following:
   - `PROJECT_ID`: the name of the project.

To view backup and restore jobs for Backup for GKE, use the following
instructions:

1. View backup and restore jobs.

   ```
   gcloud logging read 'logName=~"bfg_backup_restore_jobs"' --project=PROJECT_ID
   ```

   Add the [`--freshness` flag](https://docs.cloud.google.com/sdk/gcloud/reference/logging/read.md.txt#--freshness)
   to your command to read jobs that are more than 1 day old.

   Replace the following:
   - `PROJECT_ID`: the name of the project.

## Current backup job failures

The current failures section lets you view the details of unresolved backup job
failures, specifically for resources whose backups have failed since
their last successful backup. The **Current failures** section displays the following information.

| Field | Description |
|---|---|
| **Error type** | The description of the error. For example, `PERMISSION_DENIED`. |
| **Source project name** | The name of the project where the protected resource exists. |
| **Current failures** | The total number of resources in the source project for which the last backup job failed due to a particular error type. |
| **Error code** | The error code that is associated with the error type. |
| **Error message** | The error message for the failed job. |
| **Resource ID** | The list of IDs of the resources for which the last backup job failed. |

To resolve failed backup jobs, see:

- For resources protected by Backup and DR backup vault jobs: [Troubleshoot backup failure issues](https://docs.cloud.google.com/backup-disaster-recovery/docs/backup-vault-issues.md.txt)
- For resources protected by GKE clusters: [Overview of backup for GKE error codes](https://docs.cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/troubleshoot/backup-error-codes.md.txt)

## Backup and restore job details

The **Backup and restore job details** section displays the following information.

| Field | Description |
|---|---|
| **Job ID** | The ID associated with the job. |
| **Job category** | The type of job, which can be scheduled backup, on-demand backup, restore, or point-in-time restore (PiTR). |
| **Job status** | The status of the job, which can be successful, failed, skipped, or running. |
| **Resource name** | The name of the protected resource. |
| **Source project name** | The name of the project where the source exists. |
| **Resource location** | The location of the protected resource. |
| **Backup plan name** | The name of the backup plan associated with the resource. The backup plan name field remains `Null` for the restore jobs. |
| **backup vault location** | The location of the backup vault where the backups are stored. |
| **Backup rule** | The name of the backup rule that triggered the backup job. |
| **Backup vault name** | The name of the backup vault where the backups are stored. |
| **Backup project name** | The name of the backup project where your backup vault and backup plan exist. |
| **Incremental backup size GiB** | The amount of incremental backup data copied in GiB. |
| **Start time** | The start time of the job. The start time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **Duration** | The duration to complete the job. |
| **Error type** | The name of the error type. For example, `PERMISSION_DENIED`. The error type is displayed as `Null` if no error occurred for the job. |
| **Error message** | The error message for the failed job. The error message is displayed as `Null` if no error occurred for the job. |
| **Error code** | The error code associated for the failed job. The error code is displayed as `Null` if no error occurred for the job. |
| **End time** | The end time of the job. The end time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **Backup name** | For backup jobs, the backup name is a system generated name for the backup in the form of UUID. For restore jobs, the backup name is the name of the backup used to perform the restore. |
| **Restore project name** | The name of the project where you are restoring the backup. |
| **Restore resource name** | The name of the resource that gets created after the successful restoration. |
| **Resource type** | The type of resource. |
| **Resource ID** | The ID of the resource. |
| **Recovery Point Time** | For PiTR, restore is done to a point-in-time instead of restoring just a backup. This field captures the user provided recovery point. |
| **Datasource** | Name of the Data source in backup vault where the backups are stored. PiTR is triggered on data source not backups. |

> [!NOTE]
> **Note:** The **Backup rule** field is not applicable for resources managed by Backup for GKE. The field has a Null value in the dashboard.

## View system jobs

To view system jobs, do the following:

### Console

1. In the Google Cloud console in Backup and DR, go to the **Jobs** page.

   [Go to Jobs](https://console.cloud.google.com/backupdr/jobs)
2. From the analysis section, click **System Jobs**.

> [!NOTE]
> **Note:** The same dashboard displays both Backup and DR and Backup for GKE jobs.

### gcloud

To view system jobs for Backup and DR, use the following instructions:

1. View system jobs.

   ```
   gcloud logging read 'logName=~"LOG_NAME"' --project=PROJECT_ID
   ```

   Add the [`--freshness` flag](https://docs.cloud.google.com/sdk/gcloud/reference/logging/read.md.txt#--freshness)
   to your command to read jobs that are more than 1 day old.

   Replace the following:
   - `LOG_NAME`: the name of the log, either:

     - `bdr_backup_plan_jobs`: jobs related to a backup plan
     - `bdr_backup_plan_association_jobs`: jobs related to backup plan association in the administrator project, in case of cross-project protection.
     - `bdr_backup_plan_association_source_jobs`: jobs related to backup plan association in the workload project.
     - `bdr_auto_protection_policy_jobs`: jobs related to an auto protection policy.
     - `bdr_auto_protection_policy_binding_jobs`: jobs related to auto protection policy binding.
   - `PROJECT_ID`: the name of the project.

To view system jobs for Backup for GKE, use the following instructions:

1. View system jobs.

   ```
   gcloud logging read 'logName=~"bfg_backup_plan_jobs"' --project=PROJECT_ID
   ```

   Add the [`--freshness` flag](https://docs.cloud.google.com/sdk/gcloud/reference/logging/read.md.txt#--freshness)
   to your command to read jobs that are more than 1 day old.

   Replace the following:
   - `PROJECT_ID`: the name of the project.

### Backup plan system job details

The **Backup plan** section displays the following information.

| Field | Description |
|---|---|
| **Job ID** | The ID associated with the job. |
| **Job category** | The type of job (only **update** jobs are shown). |
| **Job status** | The status of the job, which can be successful, failed, skipped, or running. |
| **Resource type** | The type of the protected resource. |
| **Backup plan name** | The name of the backup plan. |
| **Previous backup plan revision ID** | The previous revision ID of the backup plan. |
| **Previous backup plan revision name** | The name of the previous revision of the backup plan. |
| **New backup plan revision ID** | The new revision ID of the backup plan. |
| **New backup plan revision name** | The name of the new revision of the backup plan. |
| **Start time** | The start time of the job. The start time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **End time** | The end time of the job. The end time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **Number of workloads affected** | The number of workloads affected by the job. |
| **Previous backup plan rules** | A list of the backup rules in the previous revision of the backup plan. |
| **Revised backup plan rules** | A list of the backup rules in the new revision of the backup plan. |
| **Error code** | The error code associated for the failed job. The error code is displayed as `Null` if no error occurred for the job. |
| **Error type** | The name of the error type. For example, `PERMISSION_DENIED`. The error type is displayed as `Null` if no error occurred for the job. |
| **Error message** | The error message for the failed job. The error message is displayed as `Null` if no error occurred for the job. |

> [!NOTE]
> **Note:** The following fields are not applicable for resources managed by Backup for GKE: **Backup rule** , **Backup plan revision name** , and **Backup plan revision ID**. They appear as Null values in the dashboard.

### Backup plan association system job details

The **Backup plan association** section displays the following information.

| Field | Description |
|---|---|
| **Job ID** | The ID associated with the job. |
| **Job category** | The type of job, (update). |
| **Job status** | The status of the job, which can be successful, queued, failed, skipped, or running. |
| **Resource name** | The name of the protected resource. |
| **Resource ID** | The ID of the resource. |
| **Resource location** | The location of the protected resource. |
| **Resource type** | The type of resource. |
| **Backup plan association name** | The name of the backup plan association. |
| **Name of the previous backup plan** | The name of the previous backup plan. |
| **Previous backup plan revision ID** | The previous revision ID of the backup plan. |
| **Previous backup plan revision name** | The name of the previous revision of the backup plan. |
| **Name of the new backup plan** | The name of the new backup plan. |
| **New backup plan revision ID** | The new revision ID of the backup plan. |
| **New backup plan revision name** | The name of the new revision of the backup plan. |
| **Start time** | The start time of the job. The start time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **End time** | The end time of the job. The end time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **Duration** | The duration to complete the job. |
| **Error code** | The error code associated for the failed job. The error code is displayed as `Null` if no error occurred for the job. |
| **Error type** | The name of the error type. For example, `PERMISSION_DENIED`. The error type is displayed as `Null` if no error occurred for the job. |
| **Error message** | The error message for the failed job. The error message is displayed as `Null` if no error occurred for the job. |

### Auto protection policy system job details

The **Auto protection policy** section displays the following information.

| Field | Description |
|---|---|
| **Job ID** | The ID associated with the job. |
| **Job category** | The type of job, which can be create, update, or delete. |
| **Job status** | The status of the job, which can be running, successful, or failed. |
| **Auto protection policy name** | The name of the auto protection policy. |
| **Current backup plan name** | The name of the current backup plan. |
| **Current backup plan revision ID** | The revision ID of the current backup plan. |
| **Previous backup plan name** | The name of the previous backup plan. |
| **Previous backup plan revision ID** | The revision ID of the previous backup plan. |
| **Current criteria** | The matching criteria associated with the policy. |
| **Previous criteria** | The matching criteria previously associated with the policy. |
| **Location** | The location of the auto protection policy. |
| **Start time** | The start time of the job. The start time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **End time** | The end time of the job. The end time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **Duration** | The duration to complete the job. |
| **Error code** | The error code associated with the failed job. The error code is displayed as `Null` if no error occurred for the job. |
| **Error type** | The name of the error type. For example, `PERMISSION_DENIED`. The error type is displayed as `Null` if no error occurred for the job. |
| **Error message** | The error message for the failed job. The error message is displayed as `Null` if no error occurred for the job. |

### Auto protection policy binding system job details

The **Auto protection policy binding** section displays the following
information.

| Field | Description |
|---|---|
| **Job ID** | The ID associated with the job. |
| **Job category** | The type of job, which can be create, delete, or protection run. |
| **Job status** | The status of the job, which can be running, successful, failed, or partially successful. |
| **Auto protection policy binding name** | The name of the auto protection policy binding. |
| **Auto protection policy name** | The name of the associated auto protection policy. |
| **Auto protection policy project** | The project ID where the associated auto protection policy resides. |
| **Location** | The location of the auto protection policy binding. |
| **Scope** | The scope, such as the target project ID, where the binding is applied. |
| **Matching resources** | The total number of matching resources found during evaluation. |
| **Protected resources** | The total number of protected resources resulting from evaluation. |
| **Failed resources** | The total number of resources that failed to be protected during evaluation. |
| **Criteria** | The matching criteria used for the run. |
| **Start time** | The start time of the job. The start time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **End time** | The end time of the job. The end time is in `YYYY-MM-DD HH:MM:SS.SSS` UTC format. |
| **Duration** | The duration to complete the job. |
| **Error code** | The error code associated with the failed job. The error code is displayed as `Null` if no error occurred for the job. |
| **Error type** | The name of the error type. For example, `PERMISSION_DENIED`. The error type is displayed as `Null` if no error occurred for the job. |
| **Error message** | The error message for the failed job. The error message is displayed as `Null` if no error occurred for the job. |

## Current system job failures

The current system job failures section lets you view the details of
unresolved system job failures, specifically for resources whose system events
have failed. The **Current system job failures** section displays the following information.

| Field | Description |
|---|---|
| **Error type** | The description of the error. For example, `PERMISSION_DENIED`. |
| **Source project name** | The name of the project where the protected resource exists. |
| **Current failures** | The total number of system events that have failed pertaining to that job. |
| **Error code** | The error code that is associated with the error type. |
| **Error message** | The error message for the failed job. |
| **Resource ID** | The ID of the resource, which can be one of the following depending on the resource type: **Backup plan association** (the list of IDs of the protected resources), **Backup plan** (the name of the backup plan), **Auto protection policy** (the name of the auto protection policy), or **Auto protection policy binding** (the name of the auto protection policy binding). |

## What's next

- [Automate protection of Compute Engine instances](https://docs.cloud.google.com/backup-disaster-recovery/docs/create-plan/dynamic-protection.md.txt)
- [Monitor jobs in the appliance management console](https://docs.cloud.google.com/backup-disaster-recovery/docs/monitor-reports/monitor-jobs)
- [Configure a log-based alert for vaulted backups](https://docs.cloud.google.com/backup-disaster-recovery/docs/monitor-reports/configure-alerts-vault.md.txt)