Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge branch 'master' into 6020-add-code-placeholders-core-ent-examples

pull/6055/head
Jameelah Mercer 2025-05-14 16:15:07 -07:00 committed by GitHub
parent 58f98b0f2a 249553d00d
commit b84ab2cb60
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 20 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-docs/influxdb3/enterprise/v3/ref.yml
View File

@ -157,7 +157,7 @@ tags:
1. [Create an admin token](#section/Authentication) for the InfluxDB 3 Enterprise API. 1. [Create an admin token](#section/Authentication) for the InfluxDB 3 Enterprise API.
```bash ```bash
curl -X POST "http://localhost:8181/api/v3/enterprise/configure/token/admin" curl -X POST "http://localhost:8181/api/v3/configure/token/admin"
``` ```
2. [Check the status](#section/Server-information) of the InfluxDB server. 2. [Check the status](#section/Server-information) of the InfluxDB server.

22
content/influxdb3/clustered/admin/backup-restore.md
View File

@ -57,6 +57,11 @@ timestamp on the Parquet file entry in the Catalog.
The Parquet file is no The Parquet file is no
longer queryable, but remains intact in the object store. longer queryable, but remains intact in the object store.
> [!Note]
> Soft deletes are a mechanism of the {{% product-name %}} Catalog, not of the
> underlying object storage provider. Soft deletes do not modify objects in the
> object store; only Catalog entries that reference objects in the object store.
## Hard delete ## Hard delete
A _hard delete_ refers to when a Parquet file is actually deleted from object A _hard delete_ refers to when a Parquet file is actually deleted from object
@ -219,6 +224,15 @@ written on or around the beginning of the next hour.
Use the following process to restore your InfluxDB cluster to a recovery point Use the following process to restore your InfluxDB cluster to a recovery point
using Catalog store snapshots: using Catalog store snapshots:
> [!Warning]
>
> #### Use the same InfluxDB Clustered version used to generate the snapshot
>
> When restoring an InfluxDB cluster to a recovery point, use the same version
> of InfluxDB Clustered used to generate the Catalog store snapshot.
> You may need to [downgrade to a previous version](/influxdb3/clustered/admin/upgrade/)
> before restoring.
1. **Install prerequisites:** 1. **Install prerequisites:**
- `kubectl` CLI for managing your Kubernetes deployment. - `kubectl` CLI for managing your Kubernetes deployment.
@ -273,7 +287,8 @@ using Catalog store snapshots:
metadata: metadata:
name: influxdb name: influxdb
namespace: influxdb namespace: influxdb
pause: true spec:
pause: true
# ... # ...
``` ```
@ -331,7 +346,8 @@ using Catalog store snapshots:
metadata: metadata:
name: influxdb name: influxdb
namespace: influxdb namespace: influxdb
pause: false spec:
pause: false
# ... # ...
``` ```
@ -349,8 +365,6 @@ Your InfluxDB cluster is now restored to the recovery point.
When the Garbage Collector runs, it identifies what Parquet files are not When the Garbage Collector runs, it identifies what Parquet files are not
associated with the recovery point and [soft deletes](#soft-delete) them. associated with the recovery point and [soft deletes](#soft-delete) them.
## Resources ## Resources
### prep\_pg\_dump.awk ### prep\_pg\_dump.awk