summarize-backups

Description

Print summary information for full and split backups grouped by group-by flag.

The output is human readable, with JSON as an alternative format.

Examples:

sdb-admin summarize-backups --repository azure://foo/bar
sdb-admin summarize-backups -r azure://foo/bar --no-cache
sdb-admin summarize-backups -r "s3://foo/bar?region=eu-central-1"

Usage

Usage:
  sdb-admin summarize-backups [flags]

  For flags that can accept multiple values (indicated by VALUES after the name of the flag),
  separate each value with a comma.

Flags:
      --after TIME            Select backups created after the specified TIME. TIME should be in the ISO 8601 format or a duration relative to the current time ('2006-01-02T15:04:05-0700', '2006-01-02', '-3h30m'). Time zone is optional but recommended. If TIME is specified without the time zone, a local time zone will be used
      --before TIME           Select backups created before the specified TIME. TIME should be in the ISO 8601 format or a duration relative to the current time ('2006-01-02T15:04:05-0700', '2006-01-02', '-3h30m'). Time zone is optional but recommended. If TIME is specified without the time zone, a local time zone will be used
      --cluster-id VALUES     Select backups with the specified cluster id. This flag can be provided multiple times
      --cluster-name VALUES   Select backups with the specified cluster name. This flag can be provided multiple times
      --database VALUES       Select backups for the specified database(s). This flag can be provided multiple times
  -h, --help                  Help for summarize-backups
      --no-cache              Forces reads directly from the repositories, bypassing the cache. The cache will be updated
      --no-region             Do not use region-specific endpoints for S3-compatible repositories
  -r, --repository STRING     Path to the repository in the URL format. See https://docs.singlestore.com/toolbox-redir/memsql-backup-repository for examples

Global Flags:
      --backup-cache FILE_PATH                File path for the backup cache
      --cache-file FILE_PATH                  File path for the Toolbox node cache
  -c, --config FILE_PATH                      File path for the Toolbox configuration
      --disable-colors                        Disable color output in console, which some terminal sessions/environments may have difficulty with
      --disable-spinner                       Disable the progress spinner, which some terminal sessions/environments may have issues with
  -j, --json                                  Enable JSON output
      --parallelism POSITIVE_INTEGER          Maximum number of operations to run in parallel
      --runtime-dir DIRECTORY_PATH            Where to store Toolbox runtime data
      --ssh-control-persist SECONDS           Enable SSH ControlPersist and set it to the specified duration in seconds
      --ssh-max-sessions POSITIVE_INTEGER     Maximum number of SSH sessions to open per host, must be at least 3
      --ssh-strict-host-key-checking          Enable strict host key checking for SSH connections
      --ssh-user-known-hosts-file FILE_PATH   Path to the user known_hosts file for SSH connections. If not set, /dev/null will be used
      --state-file FILE_PATH                  Toolbox state file path
  -v, --verbosity count                       Increase logging verbosity: valid values are 1, 2, 3. Usage -v=count or --verbosity=count
  -y, --yes                                   Enable non-interactive mode and assume the user would like to move forward with the proposed actions by default

Remarks

This command is interactive unless you use either --yes or --json flag to override interactive behavior.

Last modified: October 3, 2023

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK