.Available storage types
-[width="100%",cols="<d,1*m,4*d",options="header"]
+[width="100%",cols="<2d,1*m,4*d",options="header"]
|===========================================================
|Description |PVE type |Level |Shared|Snapshots|Stable
|ZFS (local) |zfspool |file |no |yes |yes
|Directory |dir |file |no |no^1^ |yes
+|BTRFS |btrfs |file |no |yes |technology preview
|NFS |nfs |file |yes |no^1^ |yes
|CIFS |cifs |file |yes |no^1^ |yes
-|Proxmox Backup |pbs |both |yes |n/a |beta
+|Proxmox Backup |pbs |both |yes |n/a |yes
|GlusterFS |glusterfs |file |yes |no^1^ |yes
|CephFS |cephfs |file |yes |yes |yes
|LVM |lvm |block |no^2^ |no |yes
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::
Default image format (`raw|qcow2|vmdk`)
+preallocation::
+
+Preallocation mode (`off|metadata|falloc|full`) for `raw` and `qcow2` images on
+file-based storages. The default is `metadata`, which is treated like `off` for
+`raw` images. When using network storages in combination with large `qcow2`
+images, using `off` can help to avoid timeouts.
WARNING: It is not advisable to use the same storage pool on different
{pve} clusters. Some storage operation need exclusive access to the
* link:/wiki/Storage:_CIFS[Storage: CIFS]
-* link:/wiki/Storage:_CIFS[Storage: Proxmox Backup Server]
+* link:/wiki/Storage:_Proxmox_Backup_Server[Storage: Proxmox Backup Server]
* link:/wiki/Storage:_RBD[Storage: RBD]
include::pve-storage-cephfs.adoc[]
+include::pve-storage-btrfs.adoc[]
+
+include::pve-storage-zfs.adoc[]
ifdef::manvolnum[]