This document contains the steps you must follow to install and configure the
components that are necessary to backup and restore your workloads in Google Distributed Cloud (GDC) air-gapped.

## Before you begin

Ensure you have the following items pre-configured:

- An S3 endpoint and bucket on GDC object storage with an S3 access key ID and secret access key.
- A working cluster. ### Request IAM roles

To verify and work with backup and restore components, ask your IAM
Org Admin or IAM Project Admin to grant you one of the following roles:

- **User Cluster Backup Admin** (`user-cluster-backup-admin`): creates, gets, lists,
  watches, updates, patches, and deletes backup resources such as backup plans, restore
  plans, and backup repositories in user clusters. Contact your IAM Org Admin
  to request
  this role.

- **Backup Creator** (`backup-creator`): creates, gets, lists, watches, updates, patches,
  and deletes manual backup requests and manual restore requests. Contact your
  IAM Project Admin to
  request this role.

## Verify backup and restore installation

Verify that the `gpcbackup` control plane and
agent are both running for the cluster you want to back up:

```bash
kubectl get pods -n gpc-backup-system
```

After running the command, the output looks like the following example. There
should be two pods running, a control plane pod and an agent pod:

    NAME                                                READY   STATUS    RESTARTS   AGE
    gpcbackup-agent-0                                   1/1     Running   2          64m
    gpcbackup-controlplane-controller-6fc9485ff-jdk95   1/1     Running   0          64m

## What's next

- [Add a backup repository](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/platform-application/pa-ao-operations/cluster-backup/add-backup-repository.md.txt)