X-Git-Url: https://git.openafs.org/?p=openafs.git;a=blobdiff_plain;f=doc%2Fman-pages%2Fpod8%2Fbackup_volsetrestore.pod;h=4001038caa8565031a75a10ce5615d73037edd1c;hp=6f7aa2d140e65f728dc0eaf73fb57d4136031a22;hb=131cbaa0cf74a7b3ca24ec971a9495c8dbd73e6a;hpb=f64a78e7013ebafd9ce4a0a50822a6087ff62f6c diff --git a/doc/man-pages/pod8/backup_volsetrestore.pod b/doc/man-pages/pod8/backup_volsetrestore.pod index 6f7aa2d..4001038 100644 --- a/doc/man-pages/pod8/backup_volsetrestore.pod +++ b/doc/man-pages/pod8/backup_volsetrestore.pod @@ -1,17 +1,26 @@ =head1 NAME -backup volsetrestore - Restores all volumes in a volume set +backup_volsetrestore - Restores all volumes in a volume set =head1 SYNOPSIS -B [B<-name> >] - [B<-file> >] [B<-portoffset> >+] - [B<-extension> >] [B<-n>] - [B<-localauth>] [B<-cell> >] [B<-help>] +=for html +
-B [B<-na> >] [B<-f> >] - [B<-p> >+] [B<-e> >] - [B<-n>] [B<-l>] [B<-c> >] [B<-h>] +B S<<< [B<-name> >] >>> + S<<< [B<-file> >] >>> + S<<< [B<-portoffset> >+] >>> + S<<< [B<-extension> >] >>> [B<-dryrun>] + [B<-localauth>] S<<< [B<-cell> >] >>> [B<-help>] + +B S<<< [B<-na> >] >>> + S<<< [B<-f> >] >>> + S<<< [B<-p> >+] >>> + S<<< [B<-e> >] >>> + [B<-dryrun>] [B<-l>] S<<< [B<-c> >] >>> [B<-h>] + +=for html +
=head1 DESCRIPTION @@ -93,7 +102,7 @@ Coordinator can read, and so on. If dumps are on multiple incompatible tape types, use the B command to restore individual volumes, or use this command after defining new volume sets that group together volumes that were dumped to compatible tape types. For further -discussion, see the I. +discussion, see the I. By default, the Backup System overwrites the contents of an existing volume with the restored data. To create a new volume to house the @@ -103,10 +112,11 @@ the read/write base name, and creates a new VLDB entry. The command does not affect the existing volume in any way. However, if a volume with the specified extension also already exists, the command overwrites it. -The B<-n> flag produces a list of the volumes to be restored if the B<-n> -flag were not included, without actually restoring any volumes. See -L for a detailed description of the output, and suggestions on how -to combine it most effectively with the B<-file> and B<-name> arguments. +The B<-dryrun> flag produces a list of the volumes to be restored if the +B<-dryrun> flag were not included, without actually restoring any volumes. +See L for a detailed description of the output, and suggestions +on how to combine it most effectively with the B<-file> and B<-name> +arguments. The execution time for a B command depends on the number of volumes to be restored and the amount of data in them, but it @@ -153,7 +163,7 @@ and have the following format: [ ...] -where +where =over 4 @@ -215,10 +225,10 @@ Provide this argument unless the default value of 0 (zero) is appropriate for all dumps. If C<0> is just one of the values in the list, provide it explicitly in the appropriate order. -=item B<-n> +=item B<-dryrun> Displays a list of the volumes to be restored if the flag were not -included, without actually restoring them. L details the format of +included, without actually restoring them. L details the format of the output. When combined with the B<-name> argument, its output is easily edited for use as input to the B<-file> argument on a subsequent B command. @@ -245,8 +255,8 @@ ignored. =head1 OUTPUT -If the B<-n> flag is not provided, the command displays a unique task ID -number for the operation, in two places: +If the B<-dryrun> flag is not provided, the command displays a unique +task ID number for the operation, in two places: =over 4 @@ -266,13 +276,13 @@ B command when the B command is issued in interactive mode. The Backup System does not assign either type of ID number until the restoration process actually begins. -When the B<-n> flag is included, no task ID or job ID numbers are reported -because none are assigned. Instead, the output begins with a count of the -number of volumes to be restored, followed by a line for each dump of a -volume. For each volume, the line representing the most recent full dump -appears first, and lines for any subsequent incremental dumps follow, -ordered by dump level. The lines for a given volume do not necessarily -appear all together, however. +When the B<-dryrun> flag is included, no task ID or job ID numbers are +reported because none are assigned. Instead, the output begins with a +count of the number of volumes to be restored, followed by a line for +each dump of a volume. For each volume, the line representing the most +recent full dump appears first, and lines for any subsequent incremental +dumps follow, ordered by dump level. The lines for a given volume do not +necessarily appear all together, however. The format of each line is as follows (the output is shown here on two lines only for legibility reasons): @@ -331,8 +341,8 @@ The date and time when the volume was dumped. =back One way to generate a file for use as input to the B<-file> argument is to -combine the B<-name> and B<-n> options, directing the output to a -file. The I section on using the Backup +combine the B<-name> and B<-dryrun> options, directing the output to a +file. The I section on using the Backup System to restore data explains how to edit the file as necessary before using it as input to the B<-file> argument.