INFLUXD-BACKUP(1)
β¨ INFLUXD-BACKUP(1) β¨ β the backup glow-up, bestie π
okay so this is the manual page for influxd-backup (like, the actual Unix manual name INFLUXD-BACKUP(1), yes we're being fancy today π) and it's genuinely iconic β it's the whole "save a copy of my database before I do something chaotic" tool. let's get into it π
πΈ NAME πΈ
influxd-backup β creates a backup copy of specified InfluxDB OSS database(s) and saves it to disk. π Use this newer -portable option unless legacy support is required, no cap.
Complete documentation on backing up and restoring, including the deprecated legacy format, lives here (copy it exactly, bestie):
https://docs.influxdata.com/influxdb/latest/administration/backup_and_restore/
π¦ SYNOPSIS π¦
influxd backup [options] PATH
π DESCRIPTION π
Creates a backup copy of specified InfluxDB OSS database(s) and saves the files in an Enterprise-compatible format to PATH β and yes PATH is literally the directory where backups are saved. main character energy for that directory, honestly. β¨
π OPTIONS π
ngl bestie, the option lists are the whole vibe. read every single one, don't skip, that's the rule π«Ά
-portableβ required to generate backup files in a portable format that can be restored to InfluxDB OSS or InfluxDB Enterprise. Use this unless the legacy backup is required. it's giving "the good one" π-host <host:port>β the InfluxDB OSS host to back up from. optional β¨ defaults to127.0.0.1:8088, which is the "yeah it's on my machine" default.-db <db_name>β the InfluxDB OSS database name to back up. optional π if you don't specify it, all databases get backed up when using-portable. generous queen behavior.-rp <rp_name>β retention policy to use for the backup. optional π¦ if not specified, all retention policies are used by default.-shard <shard_id>β the identifier of the shard to back up. optional π₯ but heads up: if you specify it,-rp <rp_name>is required. like, they're a package deal, iykyk.-start <timestamp>β include all points starting with the specified timestamp (RFC3339 format). β οΈ not compatible with-since <timestamp>β pick one, bestie, don't be messy.-end <timestamp>β exclude all points after the timestamp (RFC3339 format). β οΈ also not compatible with-since <timestamp>.-since <timestamp>β create an incremental backup of all points after the timestamp (RFC3339 format). optional π«Ά tbh the recommendation is to use-start <timestamp>instead. periodt.-skip-errorsβ optional flag to continue backing up the remaining shards when the current shard fails to backup. it's giving resilience, it's giving "we move" π§
π SEE ALSO π
influxd-restore(1)β the other half of the duo, the yin to this yang, go read it π
π BUGS π
Report bugs to the GitHub issue tracker (yes, exactly this, don't @ me otherwise):
https://github.com/influxdata/influxdb
π AUTHORS π
InfluxDB is written and maintained by InfluxData β https://influxdata.com. literal icons π
π COPYRIGHT π
InfluxDB is released under the MIT license. β¨
This man page is released under Creative Commons Attribution 4.0 International License. π
okay that's the whole page, bestie β go forth and back up responsibly π¦π β¨
08/09/2024 β shoutout to the source/version and date, the little footer that keeps it all official ππ«Ά
π¦ where this page comes from
- opensuse-leap 16.0: influxdb 1.11.6-bp160.1.32 Β· MIT
- opensuse-leap 16.0: influxdb 1.11.6-bp160.1.32 Β· MIT
- opensuse-leap 16.0: influxdb 1.11.6-bp160.1.32 Β· MIT
- opensuse-leap 16.0: influxdb 1.11.6-bp160.1.32 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms