marco/plugin-barman-cloud
1
0
Fork 0
mirror of https://github.com/cloudnative-pg/plugin-barman-cloud.git synced 2026-01-11 21:23:12 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: review the usage page (flipped the sections)

Browse Source 
Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
This commit is contained in:
Gabriele Bartolini 2025-09-12 16:10:48 +02:00 committed by Jonathan Battiato
parent 134b514a56
commit 577cd81d81
1 changed files with 27 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

55
web/docs/usage.md
View File

@ -81,34 +81,13 @@ This configuration enables both WAL archiving and data directory backups.
## Performing a Base Backup ## Performing a Base Backup
Once WAL archiving is enabled, the cluster is ready for backups. Once WAL archiving is enabled, the cluster is ready for backups. Backups can be
created either declaratively (with YAML manifests) or imperatively (with the
`cnpg` plugin).
### Using kubectl-cnpg plugin ### Declarative approach (YAML manifest)
The quickest way to create an on-demand backup is using the kubectl-cnpg plugin: Create a backup resource by applying a YAML manifest:
```bash
kubectl cnpg backup -n <namespace> <cluster-name> \
--method=plugin \
--plugin-name=barman-cloud.cloudnative-pg.io
```
:::note Migration from in-tree backup
If you're migrating from the in-tree backup system, note that the command has changed from:
```bash
# Old command (in-tree backup)
kubectl cnpg backup -n <namespace> <cluster-name> --method=barmanObjectStore
```
to:
```bash
# New command (plugin backup)
kubectl cnpg backup -n <namespace> <cluster-name> --method=plugin --plugin-name=barman-cloud.cloudnative-pg.io
```
:::
### Using YAML manifests
Alternatively, you can create a backup using a YAML manifest:
```yaml ```yaml
apiVersion: postgresql.cnpg.io/v1 apiVersion: postgresql.cnpg.io/v1
@ -123,8 +102,28 @@ spec:
name: barman-cloud.cloudnative-pg.io name: barman-cloud.cloudnative-pg.io
``` ```
:::note ### Imperative approach (using the `cnpg` plugin)
You can apply the same concept to the `ScheduledBackup` resource.
The quickest way to trigger an on-demand backup is with the `cnpg` plugin:
```bash
kubectl cnpg backup -n <namespace> <cluster-name> \
--method=plugin \
--plugin-name=barman-cloud.cloudnative-pg.io
```
:::note Migration from in-tree backups
If you are migrating from the in-tree backup system, note the change in syntax:
```bash
# Old command (in-tree backup)
kubectl cnpg backup -n <namespace> <cluster-name> --method=barmanObjectStore
# New command (plugin-based backup)
kubectl cnpg backup -n <namespace> <cluster-name> \
--method=plugin \
--plugin-name=barman-cloud.cloudnative-pg.io
```
::: :::
## Restoring a Cluster ## Restoring a Cluster