influxdata / influxdata/docs-v2
InfluxDB 3 backup and restore
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
# InfluxDB 3 backup and restore
## Finding
Neither the docs nor the v3 CLI describe any full or incremental backup/restore workflow, so the bot could only tell users the feature appears missing and advise caution, without giving commands, file paths, or recommended snapshot strategies.
## Suggestion
Add official backup/restore docs for v3 (Core, Enterprise, Clustered): supported strategies, CLI syntax, incremental vs snapshot semantics, object-storage workflows, and upgrade notes; link prominently from the admin guide.
## Conversations
- I use OSS v1 and v2 across various projects and am now looking to consolidate on v3. I backup my v1 with influxd backup -portable, v2 with influx backup which work well. I can't find documentation on how to backup my v3, the CLI doesn't have the backup command. Various searches tell me to export the data, or just 'do filesystem backups', but these don't seem to be official. What's the right way to backup/restore a v3 instance? Am I adopting too early?
- how can I do incremental back ups in InfluxDb version 3?
- influxdb 3 支持增量备份吗
–––
Explore user conversations on:
https://app.kapa.ai/720100f9-ce93-4305-88fd-5fcf71effad7/coverage-gaps/clusters/82e15d70-1819-4cb9-aaf9-fc474981db1e
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing InfluxDB 3 admin guide and v3 CLI documentation, then determine the supported backup and restore workflows for Core, Enterprise, and Clustered deployments. Document full and incremental or snapshot semantics, object-storage workflows, and upgrade notes, with prominent admin-guide links; done means users can find official commands and recovery guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100