The CIFS backend extends the directory backend, so that no manual
setup of a CIFS mount is needed. Such a storage can be added directly
-through the {pve} API or the WebUI, with all our backend advantages,
+through the {pve} API or the web UI, with all our backend advantages,
like server heartbeat check or comfortable selection of exported
shares.
share::
-CIFS share to use (get available ones with `pvesm cifsscan` or the WebUI).
-Required.
+CIFS share to use (get available ones with `pvesm scan cifs <address>` or the
+web UI). Required.
username::
The user password. Optional.
It will be saved in a file only readable by root
-(`/etc/pve/priv/<STORAGE_ID>.cred`).
+(`/etc/pve/priv/storage/<STORAGE-ID>.pw`).
domain::
The local mount point. Optional, defaults to `/mnt/pve/<STORAGE_ID>/`.
+content-dirs::
+
+Overrides for the default directory layout. Optional.
+
+options::
+
+Additional CIFS mount options (see `man mount.cifs`). Some options are set
+automatically and shouldn't be set here. {pve} will always set the option
+`soft`. Depending on the configuration, these options are set automatically:
+`username`, `credentials`, `guest`, `domain`, `vers`.
+
+subdir::
+
+The subdirectory of the share to mount. Optional, defaults to the root directory
+of the share.
+
.Configuration Example (`/etc/pve/storage.cfg`)
----
cifs: backup
server 10.0.0.11
share VMData
content backup
+ options noserverino,echo_interval=30
username anna
smbversion 3
+ subdir /data
----
You can get a list of exported CIFS shares with:
----
-# pvesm cifsscan <server> [--username <username>] [--password]
+# pvesm scan cifs <server> [--username <username>] [--password]
----
Then you could add this share as a storage to the whole {pve} cluster