Kiu/VictoriaMetrics
Kiu/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-11-23 12:31:07 +01:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

docs/vmbackup.md: clarify documentation about -deleteAllObjectVersions command-line flag

Browse Source 
Updates 2fc7e9f47e
Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5121
This commit is contained in:
Aliaksandr Valialkin 2023-10-16 12:08:12 +02:00
parent b248413a07
commit 07150359b2
No known key found for this signature in database
GPG Key ID: A72BEC6CD3D0DED1
2 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
app/vmbackup/README.md
View File

@ -267,10 +267,11 @@ You have to add a custom url endpoint via flag:
### Permanent deletion of objects in S3 and compatible storages ### Permanent deletion of objects in S3 and compatible storages
By default, when using S3 compatible storages, `vmbackup` and `vmbackupmanager` will use the basic delete operation, `vmbackup` and [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager.html) use standard delete operation
which will delete current version of the object only. for S3-compatible object storage when pefrorming [incremental backups](#incremental-backups).
In order to enforce removing all versions of an object when object is deleted, you need to use `-deleteAllObjectVersions` flag. This operation removes only the current version of the object. This works OK in most cases.
Using this flag will enforce listing all versions of an object and deleting them one by one.
Sometimes it is needed to remove all the versions of an object. In this case pass `-deleteAllObjectVersions` command-line flag to `vmbackup`.
Alternatively, it is possible to use object storage lifecycle rules to remove non-current versions of objects automatically. Alternatively, it is possible to use object storage lifecycle rules to remove non-current versions of objects automatically.
Refer to the respective documentation for your object storage provider for more details. Refer to the respective documentation for your object storage provider for more details.

9
docs/vmbackup.md
View File

@ -278,10 +278,11 @@ You have to add a custom url endpoint via flag:
### Permanent deletion of objects in S3 and compatible storages ### Permanent deletion of objects in S3 and compatible storages
By default, when using S3 compatible storages, `vmbackup` and `vmbackupmanager` will use the basic delete operation, `vmbackup` and [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager.html) use standard delete operation
which will delete current version of the object only. for S3-compatible object storage when pefrorming [incremental backups](#incremental-backups).
In order to enforce removing all versions of an object when object is deleted, you need to use `-deleteAllObjectVersions` flag. This operation removes only the current version of the object. This works OK in most cases.
Using this flag will enforce listing all versions of an object and deleting them one by one.
Sometimes it is needed to remove all the versions of an object. In this case pass `-deleteAllObjectVersions` command-line flag to `vmbackup`.
Alternatively, it is possible to use object storage lifecycle rules to remove non-current versions of objects automatically. Alternatively, it is possible to use object storage lifecycle rules to remove non-current versions of objects automatically.
Refer to the respective documentation for your object storage provider for more details. Refer to the respective documentation for your object storage provider for more details.