Import Upstream version 1.8.5
[hcoop/debian/openafs.git] / doc / man-pages / pod1 / vos_restore.pod.in
CommitLineData
805e021f
CE
1=head1 NAME
2
3vos_restore - Converts an ASCII dump file into an AFS volume
4
5=head1 SYNOPSIS
6
7=for html
8<div class="synopsis">
9
10B<vos restore> S<<< B<-server> <I<machine name>> >>>
11 S<<< B<-partition> <I<partition name>> >>>
12 S<<< B<-name> <I<name of volume to be restored>> >>>
13 S<<< [B<-file> <I<dump file>>] >>>
14 S<<< [B<-id> <I<volume ID>>] >>>
15 S<<< [B<-overwrite> (abort | full | incremental)] >>>
16 [B<-offline>] [B<-readonly>]
17 S<<< [B<-creation> (dump | keep | new)] >>>
18 S<<< [B<-lastupdate> (dump | keep | new)] >>>
19 [B<-nodelete>] S<<< [B<-cell> <I<cell name>>] >>>
20 [B<-noauth>] [B<-localauth>]
21 [-verbose] [B<-encrypt>] [B<-noresolve>]
22 S<<< [B<-config> <I<config directory>>] >>>
23 [B<-help>]
24
25B<vos res> S<<< B<-s> <I<machine name>> >>>
26 S<<< B<-p> <I<partition name>> >>>
27 S<<< B<-na> <I<name of volume to be restored>> >>>
28 S<<< [B<-f> <I<dump file>>] >>>
29 S<<< [B<-i> <I<volume ID>>] >>>
30 S<<< [B<-ov> (a | f | i)] >>>
31 [B<-of>] [B<-r>]
32 S<<< [B<-cr> (d | k | n)] >>>
33 S<<< [B<-la> (d | k | n)] >>>
34 [B<-nod>] S<<< [B<-c> <I<cell name>>] >>>
35 [B<-noa>] [B<-lo>] [B<-v>] [B<-e>] [B<-nor>]
36 S<<< [B<-co> <I<config directory>>] >>>
37 [B<-h>]
38
39=for html
40</div>
41
42=head1 DESCRIPTION
43
44The B<vos restore> command converts a volume dump file previously created
45with the B<vos dump> command from ASCII into the volume format appropriate
46for the machine type indicated by the B<-server> argument, and restores it
47as a read/write volume to the partition named by the B<-partition>
48argument on that machine. The Volume Server assigns the volume name
49indicated with the B<-name> argument, and resets the volume's creation
50timestamp to the time at which the restore operation begins (the creation
51timestamp is stored in the volume header and reported in the C<Creation>
52field in the output from the B<vos examine> and B<vos listvol> commands.)
53
54Use the B<-file> argument to name the dump file, or omit the argument to
55provide the file via the standard input stream, presumably through a
56pipe. The pipe can be named, which enables interoperation with third-party
57backup utilities.
58
59As described in the following list, the command can create a completely
60new volume or overwrite an existing volume. In all cases, the full dump of
61the volume must be restored before any incremental dumps. If there are
62multiple incremental dump files, they must be restored in the order they
63were created.
64
65=over 4
66
67=item *
68
69To create a new read/write volume, use the B<-name> argument to specify a
70volume name that does not already exist in the Volume Location Database
71(VLDB), and the B<-server> and B<-partition> arguments to specify the new
72volume's site. It is best to omit the B<-id> argument so that the Volume
73Location (VL) Server allocates a volume ID automatically. Do not include
74the B<-overwrite> argument, because there is no existing volume to
75overwrite.
76
77=item *
78
79To overwrite an existing volume at its current site, specify its name and
80site with the B<-name>, B<-server>, and B<-partition> arguments. The
81volume retains its current volume ID number unless the B<-id> argument is
82provided. Specify the value C<f> or C<i> for the B<-overwrite> argument to
83indicate whether the dump file is full or incremental, respectively.
84
85=item *
86
87To overwrite an existing volume and move it to a new site, specify its
88name and the new site with the B<-name>, B<-server>, and B<-partition>
89arguments. The volume retains its current volume ID number unless the
90B<-id> argument is provided. The volume is removed from its original
91site. Specify the value C<f> for the B<-overwrite> argument to indicate
92that the dump file is a full dump (it is not possible to restore an
93incremental dump and move the volume at the same time).
94
95=back
96
97If the volume named by the B<-name> argument already exists and the
98B<-overwrite> argument is omitted, the command interpreter produces the
99following prompt:
100
101 Do you want to do a full/incremental restore or abort? [fia](a):
102
103Respond by entering one of the following values:
104
105=over 4
106
107=item *
108
109C<f> if restoring a full dump file
110
111=item *
112
113C<i> if restoring an incremental dump file
114
115=item *
116
117C<a> or Return to cancel the restore operation
118
119=back
120
121=head1 CAUTIONS
122
123If the B<-file> argument is omitted, the issuer must provide all other
124necessary arguments, because the standard input stream is unavailable for
125responding to the command interpreter's prompts for missing
126information. In particular, the issuer must provide the B<-overwrite>
127argument if overwriting an existing volume.
128
129=head1 OPTIONS
130
131=over 4
132
133=item B<-server> <I<server name>>
134
135Identifies the file server machine onto which to restore the
136volume. Provide the machine's IP address or its host name (either fully
137qualified or using an unambiguous abbreviation). For details, see
138L<vos(1)>.
139
140=item B<-partition> <I<partition name>>
141
142Identifies the partition (on the file server machine specified by the
143B<-server> argument) onto which to restore the volume. Provide the
144partition's complete name with preceding slash (for example, F</vicepa>)
145or use one of the three acceptable abbreviated forms. For details, see
146L<vos(1)>.
147
148=item B<-name> <I<name of volume>>
149
150Specifies the name under which to restore the volume. It can be up to 22
151characters long, but cannot end with a C<.readonly> or C<.backup>
152extension. If the volume already exists, it is overwritten subject to the
153value of the B<-overwrite> argument.
154
155=item B<-file> <I<dump file>>
156
157Names the dump file to restore. Incomplete pathnames are interpreted
158relative to the current working directory. Omit this argument to provide
159the dump file via the standard input stream.
160
161=item B<-id> <I<volume ID>>
162
163Specifies the volume ID number to assign to the restored volume.
164
165=item B<-overwrite> (a | f | i)
166
167Specifies which type of dump file is being restored when overwriting an
168existing volume. Provide one of the following values:
169
170=over 4
171
172=item *
173
174C<a> to terminate the restore operation.
175
176=item *
177
178C<f> if restoring a full dump file.
179
180=item *
181
182C<i> if restoring an incremental dump file. This value is not acceptable
183if the B<-server> and B<-partition> arguments do not indicate the volume's
184current site.
185
186=back
187
188This argument is mandatory if the B<-file> argument is not provided.
189
190=item B<-offline>
191
192Leaves the new volume flagged as off-line in the volume database.
193
194=item B<-readonly>
195
196Flags the new volume as read-only in the volume database.
197
198=item B<-creation> <I<dump | keep | new>>
199
200Set the creation date of the new volume to the timestamp from the
201dumped volume (dump), from the target volume, if there is one (keep),
202or generate a new one using the current time (new).
203
204=item B<-lastupdate> <I<dump | keep | new>>
205
206Set the last updated date of the new volume to the timestamp from the
207dumped volume (dump), from the target volume, if there is one (keep),
208or generate a new one using the current time (new).
209
210=item B<-nodelete>
211
212This option is available in OpenAFS clients 1.4.7 or
213later and 1.5.31 or later. This option can be used with OpenAFS server
214versions 1.4.1 or later and 1.5.0 or later.
215
216=include fragments/vos-common.pod
217
218=back
219
220=head1 EXAMPLES
221
222The following command restores the contents of the dump file
223F</afs/example.com/common/dumps/terry.dump> to the F</vicepc> partition on the
224file server machine C<fs3.example.com>. The restored volume is named
225C<user.terry>.
226
227 % cd /afs/example.com/common/dumps
228 % vos restore -file terry.dump -server fs3.example.com -partition c \
229 -name user.terry
230
231=head1 PRIVILEGE REQUIRED
232
233The issuer must be listed in the F</usr/afs/etc/UserList> file on the
234machine specified with the B<-server> argument and on each database server
235machine. If the B<-localauth> flag is included, the issuer must instead be
236logged on to a server machine as the local superuser C<root>.
237
238=head1 SEE ALSO
239
240L<restorevol(1)>,
241L<vos(1)>,
242L<vos_dump(1)>,
243L<vos_examine(1)>,
244L<vos_listvol(1)>
245
246=head1 COPYRIGHT
247
248IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
249
250This documentation is covered by the IBM Public License Version 1.0. It was
251converted from HTML to POD by software written by Chas Williams and Russ
252Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.