]> git.proxmox.com Git - pve-docs.git/blame_incremental - pve-storage-cifs.adoc
backup: clarify that CLI means FS-level and highlight retention-note
[pve-docs.git] / pve-storage-cifs.adoc
... / ...
CommitLineData
1[[storage_cifs]]
2CIFS Backend
3-----------
4ifdef::wiki[]
5:pve-toplevel:
6:title: Storage: CIFS
7endif::wiki[]
8
9Storage pool type: `cifs`
10
11The CIFS backend extends the directory backend, so that no manual
12setup of a CIFS mount is needed. Such a storage can be added directly
13through the {pve} API or the WebUI, with all our backend advantages,
14like server heartbeat check or comfortable selection of exported
15shares.
16
17Configuration
18~~~~~~~~~~~~~
19
20The backend supports all common storage properties, except the shared
21flag, which is always set. Additionally, the following CIFS special
22properties are available:
23
24server::
25
26Server IP or DNS name. Required.
27
28TIP: To avoid DNS lookup delays, it is usually preferable to use an IP
29address instead of a DNS name - unless you have a very reliable DNS
30server, or list the server in the local `/etc/hosts` file.
31
32share::
33
34CIFS share to use (get available ones with `pvesm scan cifs <address>` or the
35WebUI). Required.
36
37username::
38
39The username for the CIFS storage. Optional, defaults to `guest'.
40
41password::
42
43The user password. Optional.
44It will be saved in a file only readable by root
45(`/etc/pve/priv/storage/<STORAGE-ID>.pw`).
46
47domain::
48
49Sets the user domain (workgroup) for this storage. Optional.
50
51smbversion::
52
53SMB protocol Version. Optional, default is `3`.
54SMB1 is not supported due to security issues.
55
56path::
57
58The local mount point. Optional, defaults to `/mnt/pve/<STORAGE_ID>/`.
59
60.Configuration Example (`/etc/pve/storage.cfg`)
61----
62cifs: backup
63 path /mnt/pve/backup
64 server 10.0.0.11
65 share VMData
66 content backup
67 username anna
68 smbversion 3
69
70----
71
72Storage Features
73~~~~~~~~~~~~~~~~
74
75CIFS does not support snapshots on a storage level. But you may use
76`qcow2` backing files if you still want to have snapshots and cloning
77features available.
78
79.Storage features for backend `cifs`
80[width="100%",cols="m,m,3*d",options="header"]
81|==============================================================================
82|Content types |Image formats |Shared |Snapshots |Clones
83|images rootdir vztmpl iso backup snippets |raw qcow2 vmdk |yes |qcow2 |qcow2
84|==============================================================================
85
86Examples
87~~~~~~~~
88
89You can get a list of exported CIFS shares with:
90
91----
92# pvesm scan cifs <server> [--username <username>] [--password]
93----
94
95Then you could add this share as a storage to the whole {pve} cluster
96with:
97
98----
99# pvesm add cifs <storagename> --server <server> --share <share> [--username <username>] [--password]
100----
101
102ifdef::wiki[]
103
104See Also
105~~~~~~~~
106
107* link:/wiki/Storage[Storage]
108
109endif::wiki[]