3 vbackup, vcat, vftp, vmount, vnfs \-
4 back up Unix file systems to Venti
63 These programs back up and restore standard
64 Unix file system images stored in
70 which consist of a file system type followed
71 by a colon and forty hexadecimal digits, as in:
74 ffs:0123456789abcdef0123456789abcdef01234567
77 (The hexadecimal data is the SHA1 hash of the Venti
78 root block representing the file system image.)
80 These programs expect the environment variable
82 to be set to the network address of the Venti server to use
86 .BR tcp!yourhost!venti ).
89 copies the file system stored on
91 to the Venti server and prints the
92 score for the newly-stored image.
95 should be a disk or disk partition device
96 that would be appropriate to pass to
101 is the score of a previous backup of the disk image.
106 will not write to Venti any blocks that have not changed
107 since the previous backup.
108 This is only a speed optimization: since the blocks are already
109 stored on Venti they need not be sent to the Venti server again.
116 Turn on debugging output.
119 Trace interactions with Venti server.
123 this name is used in the printed
126 The default is the name returned by
132 No-op mode: do not write any blocks to the server
135 Print verbose output.
138 Write parallelism: keep
140 writes to the server in progress at a time.
143 Status interval: every
145 seconds, print a line tracking progress of the backup.
150 finishes, it prints a single line of the form
153 mount /\fImntname\fL/\fIyyyy\fL/\fImmdd\fL/\fImntpath\fL \fIscore\fL \fIyyyy\fL/\fImmdd\fL/\fIhhmm
156 This line is a valid configuration line for
162 is currently mounted.
165 writes the named disk image to standard output.
166 Unused file system blocks are printed zeroed regardless
167 of their actual content.
171 will assume that its standard output is seekable
173 it has been redirected to a file or disk)
174 and seek over unused blocks instead of writing to them.
179 to zero unused blocks instead.
184 interface to a physical or backed-up disk image.
185 It is used mainly for debugging.
190 prompt for a list of commands.
193 mounts the NFS service at the network connection
197 On most operating systems,
199 must be run by the user
204 NFS version 3 protocol,
205 one or more disk images in a synthetic tree defined
206 by the configuration file
209 serves both NFS mount protocol
218 Disable `encrypted' handles.
219 By default handles are encrypted with a random key to avoid
220 leaking information about the backed-up file systems.
221 If encryption is disabled, the NFS handles exposed to the client
222 may leak information about the root scores of the disks as well
226 Local service only: serve only requests from the loopback interface (127.0.0.1).
229 Local service only, with paranoia: serve only requests from loopback,
230 and only from the first source port that sends a request.
231 This option is intended to be used to make sure that once the local
232 host has mounted the service, no other local users can access it.
235 Print all NFS and NFS mount RPCs to standard error.
238 Print all Venti transactions to standard error.
246 Set block size used by the in-memory venti block cache.
247 Must be as large as the maximum block size in any
248 file system mentioned in the configuration.
251 Set the number of blocks stored by the in-memory venti cache.
254 Respond to all requests with a Sun RPC rejection.
255 This is useful during debugging.
259 is a text file describing the
263 Lines beginning with a sharp
266 The rest of the file is a sequence of commands, one per line.
269 .BI mount " mtpt score time
270 Add the file system with the given
272 to the tree at the mount point
274 The path to the mount point will be created
278 is given as the score, an empty file system is mounted at
284 is the modification time to return for the directory
286 either a decimal number of seconds since the epoch
287 or a string of the form
288 .IB yyyy / mmdd / hhmm
289 giving the year, month, day, hour, and minute.
291 does not use the modification time of the root in order
292 to avoid accessing every mounted file system on common
296 .BR /dump/sys/2005 .)
298 .BI allow " ip\fR[\fL/\fImask\fR]
300 .BI deny " ip\fR[\fL/\fImask\fR]
301 These two commands define access permissions based on IP address.
304 can be a decimal number (24) or an equivalent IP mask (255.255.255.0).
305 Each request is filtered through the rules listed in the configuration file.
306 The first rule that matches is used.
311 rules are given, the default action is to reject the request.
312 In the absence of any rules, the default action is to accept all requests.
316 Running on the server
318 back up the file system stored on
324 % vbackup /dev/da0s1a
325 mount /bob/2005/0510/home ffs:0123456789abcdef\fI...\fP 2005/0510/0831
329 Serve that backup and a few others in a tree reminiscent
330 of Plan 9's dump file system, but hide each day's contents of
335 mount /bob/2005/0510 ffs:0123456789abcdef\fI...\fP 2005/0510/0829
336 mount /bob/2005/0510/home ffs:0123456789abcdef\fI...\fP 2005/0510/0831
337 mount /bob/2005/0510/tmp /dev/null 1
338 mount /bob/2005/0511 ffs:0123456789abcdef\fI...\fP 2005/0511/0827
339 mount /bob/2005/0511/home ffs:0123456789abcdef\fI...\fP 2005/0511/0828
340 mount /bob/2005/0511/tmp /dev/null 1
341 % vnfs -b 16k -c 1k config
345 Mount the backups on a client machine using
349 # vmount udp!yourserver!nfs /dump
356 (Users of fancy shells may need to quote the address argument.)
