klio backup run v0.0.12
This is documentation for a Tech Preview of EDB's Enterprise Data Protection for CloudNativePG™ (Klio) solution. It is made available AS IS for testing and early evaluation purposes ONLY! Is is not to be used in production environments. For details, please refer to EULA section 9.4.
Backup the PostgreSQL cluster to the opened Klio server
klio backup run [flags]
Options
--enable-tier2-backup When enabled, require the backup to be sent to tier2
-h, --help help for run
-n, --name string The backup name
--wait-for-wals When enabled, wait until all the required WAL files have been archived in tier1 before declaring the backup completed. (default true)Options inherited from parent commands
--config string config file (default is $HOME/.klio.yaml)
--debug enable debug logging
--log-destination string where the log stream will be written
--log-field-level string JSON log field to report severity in (default: level)
--log-field-timestamp string JSON log field to report timestamp in (default: ts)
--log-level string the desired log level, one of error, info, debug and trace (default "info")
--pprof-server string enable the PPROF server using the specified address
--zap-devel Development Mode defaults(encoder=consoleEncoder,logLevel=Debug,stackTraceLevel=Warn). Production Mode defaults(encoder=jsonEncoder,logLevel=Info,stackTraceLevel=Error)
--zap-encoder encoder Zap log encoding (one of 'json' or 'console')
--zap-log-level level Zap Level to configure the verbosity of logging. Can be one of 'debug', 'info', 'error', 'panic'or any integer value > 0 which corresponds to custom debug levels of increasing verbosity
--zap-stacktrace-level level Zap Level at and above which stacktraces are captured (one of 'info', 'error', 'panic').
--zap-time-encoding time-encoding Zap time encoding (one of 'epoch', 'millis', 'nano', 'iso8601', 'rfc3339' or 'rfc3339nano'). Defaults to 'epoch'.SEE ALSO
- klio backup - Manage physical backups