pgo backup

pgo backup

Backup cluster

Synopsis

Backup allows you to backup a PostgreSQL cluster either by using the current “spec.backups.pgbackrest.manual” settings on the PostgreSQL cluster or by using flags to write your settings. Overwriting those settings may require the –force-conflicts flag.

RBAC Requirements

Resources                                           Verbs
---------                                           -----
postgresclusters.postgres-operator.crunchydata.com  [get patch]

Usage

pgo backup CLUSTER_NAME [flags]

Examples

# Trigger a backup on the 'hippo' postgrescluster using the current spec options
# Note: "spec.backups.pgbackrest.manual.repoName" has to exist for the backup to begin
pgo backup hippo

# Update the 'backups.pgbackrest.manual.repoName' and 'backups.pgbackrest.manual.options' fields
# on the 'hippo' postgrescluster and trigger a backup
pgo backup hippo --repoName="repo1" --options="--type=full"

# Resolve ownership conflict
pgo backup hippo --force-conflicts

Example output

postgresclusters/hippo backup initiated

Options

      --force-conflicts       take ownership and overwrite the backup settings
  -h, --help                  help for backup
      --options stringArray   options for taking a backup; can be used multiple times
      --repoName string       repoName to backup to

Options inherited from parent commands

      --as string                      Username to impersonate for the operation. User could be a regular user or a service account in a namespace.
      --as-group stringArray           Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
      --as-uid string                  UID to impersonate for the operation.
      --cache-dir string               Default cache directory (default "$HOME/.kube/cache")
      --certificate-authority string   Path to a cert file for the certificate authority
      --client-certificate string      Path to a client certificate file for TLS
      --client-key string              Path to a client key file for TLS
      --cluster string                 The name of the kubeconfig cluster to use
      --context string                 The name of the kubeconfig context to use
      --insecure-skip-tls-verify       If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
      --kubeconfig string              Path to the kubeconfig file to use for CLI requests.
  -n, --namespace string               If present, the namespace scope for this CLI request
      --request-timeout string         The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
  -s, --server string                  The address and port of the Kubernetes API server
      --tls-server-name string         Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
      --token string                   Bearer token for authentication to the API server
      --user string                    The name of the kubeconfig user to use

SEE ALSO

• pgo - pgo is a kubectl plugin for PGO, the open source Postgres Operator