fix #4319: use corred port range for corosync v3.x

[pve-docs.git] / pve-storage-pbs.adoc

diff --git a/pve-storage-pbs.adoc b/pve-storage-pbs.adoc
index a3d7da18347174b161291750bac4167f619d5bd8..1006a64099e87cd3605663e693d519129371d275 100644 (file)
--- a/pve-storage-pbs.adoc
+++ b/pve-storage-pbs.adoc
@@ -11,7 +11,7 @@ Storage pool type: `pbs`
 This backend allows direct integration of a Proxmox Backup Server into {pve}
 like any other storage.
 A Proxmox Backup storage can be added directly through the {pve} API, CLI or
-the webinterface.
+the web interface.
 
 Configuration
 ~~~~~~~~~~~~~
@@ -71,7 +71,7 @@ pbs: backup
         server enya.proxmox.com
         content backup
         fingerprint 09:54:ef:..snip..:88:af:47:fe:4c:3b:cf:8b:26:88:0b:4e:3c:b2
-        maxfiles 0
+        prune-backups keep-all=1
         username archiver@pbs
 ----
 
@@ -82,7 +82,7 @@ Proxmox Backup Server only supports backups, they can be block-level or
 file-level based. {pve} uses block-level for virtual machines and file-level for
 container.
 
-.Storage features for backend `cifs`
+.Storage features for backend `pbs`
 [width="100%",cols="m,4*d",options="header"]
 |===============================================================
 |Content types |Image formats |Shared |Snapshots |Clones