FoundationDB 7.3 (v7.3.79) Usage: backup_agent [OPTIONS] -C CONNFILE The path of a file containing the connection string for the FoundationDB cluster. The default is first the value of the FDB_CLUSTER_FILE environment variable, then `./fdb.cluster', then `/etc/foundationdb/fdb.cluster'. --log Enables trace file logging for the CLI session. --logdir PATH Specifes the output directory for trace files. If unspecified, defaults to the current directory. Has no effect unless --log is specified. --loggroup LOG_GROUP Sets the LogGroup field with the specified value for all events in the trace output (defaults to `default'). --trace-format FORMAT Select the format of the trace files. xml (the default) and json are supported. Has no effect unless --log is specified. -m SIZE, --memory SIZE Memory limit. The default value is 8GiB. When specified without a unit, MiB is assumed. --tls-certificate-file CERTFILE The path of a file containing the TLS certificate and CA chain. --tls-ca-file CERTAUTHFILE The path of a file containing the CA certificates chain. --tls-key-file KEYFILE The path of a file containing the private key corresponding to the TLS certificate. --tls-password PASSCODE The passphrase of encrypted private key --tls-verify-peers CONSTRAINTS The constraints by which to validate TLS peers. The contents and format of CONSTRAINTS are plugin-specific. --build-flags Print build information and exit. -v, --version Print version information and exit. -h, --help Display this help and exit. BLOB CREDENTIALS Blob account secret keys can optionally be omitted from blobstore:// URLs, in which case they will be loaded, if possible, from 1 or more blob credentials definition files. These files can be specified with the --blob-credentials argument described above or via the environment variable FDB_BLOB_CREDENTIALS, whose value is a colon-separated list of files. The command line takes priority over over the environment but all files from both sources are used. At connect time, the specified files are read in order and the first matching account specification (user@host) will be used to obtain the secret key. The JSON schema is: { "accounts" : { "user@host" : { "secret" : "SECRETKEY" }, "user2@host2" : { "secret" : "SECRET" } } }