1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
3 <refentry id="vfs_shadow_copy2.8">
6 <refentrytitle>vfs_shadow_copy2</refentrytitle>
7 <manvolnum>8</manvolnum>
8 <refmiscinfo class="source">Samba</refmiscinfo>
9 <refmiscinfo class="manual">System Administration tools</refmiscinfo>
10 <refmiscinfo class="version">4.0</refmiscinfo>
15 <refname>vfs_shadow_copy2</refname>
16 <refpurpose>Expose snapshots to Windows clients as shadow copies.</refpurpose>
21 <command>vfs objects = shadow_copy2</command>
26 <title>DESCRIPTION</title>
28 <para>This VFS module is part of the
29 <citerefentry><refentrytitle>samba</refentrytitle>
30 <manvolnum>7</manvolnum></citerefentry> suite.</para>
32 <para>The <command>vfs_shadow_copy2</command> VFS module functionality
33 that is similar to Microsoft Shadow Copy services. When setup properly,
34 this module allows Microsoft Shadow Copy clients to browse
35 "shadow copies" on Samba shares.
38 <para>This is a 2nd implementation of a shadow copy module. This
39 version has the following features:</para>
40 <orderedlist continuation="restarts" inheritnum="ignore" numeration="arabic">
41 <listitem><para>You don't need to populate your shares with symlinks to the
42 snapshots. This can be very important when you have thousands of
43 shares, or use [homes].</para></listitem>
44 <listitem><para>The inode number of the files is altered so it is different
45 from the original. This allows the 'restore' button to work
46 without a sharing violation.</para></listitem>
49 <para>This module is stackable.</para>
54 <title>CONFIGURATION</title>
56 <para><command>vfs_shadow_copy2</command> relies on a filesystem
57 snapshot implementation. Many common filesystems have native
61 <para>Filesystem snapshots must be mounted on
62 specially named directories in order to be recognized by
63 <command>vfs_shadow_copy2</command>. The snapshot mount points must
64 be immediate children of a the directory being shared.</para>
66 <para>The snapshot naming convention is @GMT-YYYY.MM.DD-hh.mm.ss,
69 <listitem><para><command>YYYY</command> is the 4 digit year</para></listitem>
70 <listitem><para><command>MM</command> is the 2 digit month</para></listitem>
71 <listitem><para><command>DD</command> is the 2 digit day</para></listitem>
72 <listitem><para><command>hh</command> is the 2 digit hour</para></listitem>
73 <listitem><para><command>mm</command> is the 2 digit minute</para></listitem>
74 <listitem><para><command>ss</command> is the 2 digit second.</para></listitem>
78 <para>The <command>vfs_shadow_copy2</command> snapshot naming convention can be
79 produced with the following <citerefentry><refentrytitle>date</refentrytitle>
80 <manvolnum>1</manvolnum></citerefentry> command:
82 TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S
83 </programlisting></para>
88 <title>OPTIONS</title>
92 <term>shadow:snapdir = SNAPDIR
95 <para>Path to the directory where snapshots are kept.
101 <term>shadow:basedir = BASEDIR
104 <para>Path to the base directory that snapshots are from.
110 <term>shadow:sort = asc/desc, or not specified for unsorted (default)
113 <para>By this parameter one can specify that the shadow
114 copy directories should be sorted before they are sent to the
115 client. This can be beneficial as unix filesystems are usually
116 not listed alphabetically sorted. If enabled, you typically
117 want to specify descending order.
123 <term>shadow:localtime = yes/no
126 <para>This is an optional parameter that indicates whether the
127 snapshot names are in UTC/GMT or in local time. By default
134 <term>shadow:format = format specification for snapshot names
137 <para>This is an optional parameter that specifies the format
138 specification for the naming of snapshots. The format must
139 be compatible with the conversion specifications recognized
140 by str[fp]time. The default value is "@GMT-%Y.%m.%d-%H.%M.%S".
146 <term>shadow:fixinodes = yes/no
149 <para>If you enable <command moreinfo="none">shadow:fixinodes
150 </command> then this module will modify the apparent inode
151 number of files in the snapshot directories using a hash of the
152 files path. This is needed for snapshot systems where the
153 snapshots have the same device:inode number as the original
154 files (such as happens with GPFS snapshots). If you don't set
155 this option then the 'restore' button in the shadow copy UI
156 will fail with a sharing violation.
164 <title>EXAMPLES</title>
166 <para>Add shadow copy support to user home directories:</para>
168 <smbconfsection name="[homes]"/>
169 <smbconfoption name="vfs objects">shadow_copy2</smbconfoption>
170 <smbconfoption name="shadow:snapdir">/data/snapshots</smbconfoption>
171 <smbconfoption name="shadow:basedir">/data/home</smbconfoption>
172 <smbconfoption name="shadow:sort">desc</smbconfoption>
178 <title>CAVEATS</title>
180 <para>This is not a backup, archival, or version control solution.
183 <para>With Samba or Windows servers,
184 <command>vfs_shadow_copy2</command> is designed to be an end-user
185 tool only. It does not replace or enhance your backup and
186 archival solutions and should in no way be considered as
187 such. Additionally, if you need version control, implement a
188 version control system.</para>
195 <title>VERSION</title>
197 <para>This man page is correct for version 3.2.7 of the Samba suite.
202 <title>AUTHOR</title>
204 <para>The original Samba software and related utilities
205 were created by Andrew Tridgell. Samba is now developed
206 by the Samba Team as an Open Source project similar
207 to the way the Linux kernel is developed.</para>