5
0
mirror of git://git.proxmox.com/git/pve-docs.git synced 2025-03-11 16:58:18 +03:00

add documentation for the prune-backups option

adapted from the PBS docs, and mention that maxfiles is deprecated.

Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
This commit is contained in:
Fabian Ebner 2020-11-24 11:02:00 +01:00 committed by Thomas Lamprecht
parent 08e75d1ab0
commit 3a97636641
2 changed files with 98 additions and 4 deletions

View File

@ -226,7 +226,13 @@ You can use this flag to disable the storage completely.
maxfiles::
Maximum number of backup files per VM. Use `0` for unlimited.
Deprecated, please use `prune-backups` instead. Maximum number of backup files
per VM. Use `0` for unlimited.
prune-backups::
Retention options for backups. For details, see
xref:vzdump_retention[Backup Retention].
format::

View File

@ -143,9 +143,9 @@ backup time into the filename, for example
vzdump-lxc-105-2009_10_09-11_04_43.tar
That way it is possible to store several backup in the same
directory. The parameter `maxfiles` can be used to specify the
maximum number of backups to keep.
That way it is possible to store several backup in the same directory. You can
limit the number of backups that are kept with various retention options, see
the xref:vzdump_retention[Backup Retention] section below.
Backup File Compression
-----------------------
@ -180,6 +180,94 @@ If the backup file name doesn't end with one of the above file extensions, then
it was not compressed by vzdump.
[[vzdump_retention]]
Backup Retention
----------------
With the `prune-backups` option you can specify which backups you want to keep
in a flexible manner. The following retention options are available:
`keep-all <boolean>` ::
Keep all backups. If this is `true`, no other options can be set.
`keep-last <N>` ::
Keep the last `<N>` backups.
`keep-hourly <N>` ::
Keep backups for the last `<N>` hours. If there is more than one
backup for a single hour, only the latest is kept.
`keep-daily <N>` ::
Keep backups for the last `<N>` days. If there is more than one
backup for a single day, only the latest is kept.
`keep-weekly <N>` ::
Keep backups for the last `<N>` weeks. If there is more than one
backup for a single week, only the latest is kept.
NOTE: Weeks start on Monday and end on Sunday. The software uses the
`ISO week date`-system and handles weeks at the end of the year correctly.
`keep-monthly <N>` ::
Keep backups for the last `<N>` months. If there is more than one
backup for a single month, only the latest is kept.
`keep-yearly <N>` ::
Keep backups for the last `<N>` years. If there is more than one
backup for a single year, only the latest is kept.
The retention options are processed in the order given above. Each option
only covers backups within its time period. The next option does not take care
of already covered backups. It will only consider older backups.
Specify the retention options you want to use as a
comma-separated list, for example:
# vzdump 777 --prune-backups keep-last=3,keep-daily=13,keep-yearly=9
While you can pass `prune-backups` directly to `vzdump`, it is often more
sensible to configure the setting on the storage level, which can be done via
the web interface.
NOTE: The old `maxfiles` option is deprecated and should be replaced either by
`keep-last` or, in case `maxfiles` was `0` for unlimited retention, by
`keep-all`.
Retention Settings Example
~~~~~~~~~~~~~~~~~~~~~~~~~~
The backup frequency and retention of old backups may depend on how often data
changes, and how important an older state may be, in a specific work load.
When backups act as a company's document archive, there may also be legal
requirements for how long backups must be kept.
For this example, we assume that you are doing daily backups, have a retention
period of 10 years, and the period between backups stored gradually grows.
`keep-last=3` - even if only daily backups are taken, an admin may want to
create an extra one just before or after a big upgrade. Setting keep-last
ensures this.
`keep-hourly` is not set - for daily backups this is not relevant. You cover
extra manual backups already, with keep-last.
`keep-daily=13` - together with keep-last, which covers at least one
day, this ensures that you have at least two weeks of backups.
`keep-weekly=8` - ensures that you have at least two full months of
weekly backups.
`keep-monthly=11` - together with the previous keep settings, this
ensures that you have at least a year of monthly backups.
`keep-yearly=9` - this is for the long term archive. As you covered the
current year with the previous options, you would set this to nine for the
remaining ones, giving you a total of at least 10 years of coverage.
We recommend that you use a higher retention period than is minimally required
by your environment; you can always reduce it if you find it is unnecessarily
high, but you cannot recreate backups once they have been removed.
[[vzdump_restore]]
Restore
-------