8 Storage pool type: `cifs`
10 The CIFS backend is based on the directory backend, so it shares most
11 properties. The directory layout and the file naming conventions are
12 the same. The main advantage is that you can directly configure the
13 CIFS server, so the backend can mount the share automatically in
14 the hole cluster. There is no need to modify `/etc/fstab`. The backend
15 can also test if the server is online, and provides a method to query
16 the server for exported shares.
21 The backend supports all common storage properties, except the shared
22 flag, which is always set. Additionally, the following properties are
23 used to configure the CIFS server:
27 Server IP or DNS name. To avoid DNS lookup delays, it is usually
28 preferable to use an IP address instead of a DNS name - unless you
29 have a very reliable DNS server, or list the server in the local
34 CIFS share (as listed by `pvesm cifsscan`).
40 If not presents, "guest" is used.
45 It will be saved in a private directory (/etc/pve/priv/<STORAGE_ID>.cred).
49 sets the domain (workgroup) of the user
53 SMB protocol Version (default is `3`).
54 SMB1 is not supported due to security issues.
58 The local mount point (defaults to `/mnt/pve/<STORAGE_ID>/`).
60 .Configuration Example (`/etc/pve/storage.cfg`)
75 CIFS does not support snapshots, but the backend uses `qcow2` features
76 to implement snapshots and cloning.
78 .Storage features for backend `nfs`
79 [width="100%",cols="m,m,3*d",options="header"]
80 |==============================================================================
81 |Content types |Image formats |Shared |Snapshots |Clones
82 |images rootdir vztmpl iso backup |raw qcow2 vmdk subvol |yes |qcow2 |qcow2
83 |==============================================================================
88 You can get a list of exported CIFS shares with:
90 # pvesm cifsscan <server> [--username <username>] [--password]
97 * link:/wiki/Storage[Storage]