1 07/21/87 restore
2
3
4 Syntax as a command:
5 restore -set CF_1 ... CF_N -set CF_1 ... CF_N
6 -restart_set CF_1 ... CF_N
7 or
8 restore -display_info_tape TAPE_DEVICE
9
10
11 Function: used to restore the contents of physical volumes from tape.
12 It can be used only at BCE boot command level.
13
14
15 Arguments:
16 CF_1 ... CF_N
17 defines the name of a control file or set of control files that will
18 makeup a restore set. See "List of control file requests" below.
19 At least one and up to 32 control file names may be defined per
20 restore.
21
22 TAPE_DEVICE
23 defines the device which should be used to read the "Info" tape
24 e.g. tapa_01.
25
26
27 Control arguments:
28 -display_info_tape, -dit
29 used to display the information contained on the "Info" tape, which
30 is the last tape written as part of the save process. This argument
31 should not be used in combination with any other control arguments.
32
33 -set
34 used to prefix a set of control file names. The first set of
35 control files do not require this prefix, but it is acceptable. Up
36 to four control file sets may be defined. This may be used in
37 combination with the -restart_set control argument.
38
39 -restart_set, -restart, -rt
40 used to prefix a set of control file names that are to be restarted.
41 This may be used in combination with the -set control argument.
42
43
44 List of control file requests:
45 tape_set tape_set_name,
46 ts tape_set_name
47 where "tape_set_name" is the name of the collection of tapes that
48 are to be used for the restore. The name can be up to 32
49 characters. There must be one of these requests per set. Names
50 might be defined by the color of the tape reel e.g. the "blue" set
51 or the "red" set. This name is part of the tape label and is
52 checked during at each tape mount. This name will also appear in
53 parenthesis after the program name in all output messages.
54
55 tape_device tape_device density,
56 td tape_device density
57 where "tape_device" is the standard device identifier i.e.
58 tapa_05 and "density" is in the form "d=NNNN", "den=NNNN",
59 "-density NNNN", "-den NNNN" or "-d NNNN". The density is only
60 needed during a save. During a restore the save tape will define
61 the density. The order the devices are entered defines the sequence
62 for using them. Up to 16 devices can be defined per restore set.
63
64 physical_volume pv_name disk_device,
65 pv pv_name disk_device
66 where "pv_name" is the name of the physical volume to be restored.
67 The "disk_device" would be the standard name "dska_02" or "dske_02c"
68 for sub-volumes. Up to 63 volumes can be restored per set.
69
70 partition pv_name disk_device part_name ... part_name,
71 part pv_name disk_device part_name ... part_name
72 where "pv_name" and "disk_device" are as described in the "pv"
73 request. "part_name" is the name of the partition to be restored or
74 "-all" to restore all the partitions that were saved. If "-all" is
75 specified then all partitions defined on the volume that are not
76 restored will be zero filled, except for any "alt" or "hc"
77 partitions and the "bce" partition on the rpv. Up to 64 partitions
78 may be defined per restore set.
79
80 control_file control_file,
81 cf control_file
82 where "control_file" defines another control file to be examined.
83 This enables control files to be linked together. For instance ONE
84 control file could define all the tape devices for the restore. The
85 other control files could be broken down into logical volumes that
86 only reference the tape device control file and then define the
87 physical volumes. Up to 32 control file names may be defined per
88 restore.
89
90
91 Notes on control file requests: Only one request may be given per
92 line. Any lines in a control file that begin with /, & or " are
93 treated as comments. All white space prior to a request in a line is
94 trimmed before processing.
95
96 Partitions on a physical volume can be restored without having to
97 restore the vtoc and paging regions by only defining a partition
98 request. This can also be used to copy a partition from one volume to
99 another, even of different types.
100
101 The control files can be edited using the BCE qedx request, or edited
102 while the system is running and updated in the file partition by either
103 using bootload_fs or regeneration of the MST.
104
105
106 Notes on restore: The first tape read during a restore is always the
107 "Info" tape, which was the last tape written when the set was saved.
108 This gives the restore information necessary to properly locate items
109 without wasting time spinning tape.
110
111
112 Notes on operator interrupts: A restore can be interrupted by use of
113 the console "request" key. When depressed while a restore is in
114 progress, the message "restore: Abort request:" will appear. The
115 operator will be required to input one of the following responses.
116
117 no, n
118 This causes the program to ignore the request and resume the
119 restore.
120
121 abort
122 This causes the program to abort the entire restore and return to
123 BCE command level.
124
125 restart TAPE_SET
126 This allows the operator to restart the specified TAPE_SET, using
127 its current tape device. The operator is then required to mount the
128 "restart" tape on the device, which is the tape that the operator
129 wishs to restart from. Once the SET has been restarted, the
130 remaining SETs will continue operation.
131
132 stop TAPE_SET
133 This causes the program to abort the specified TAPE_SET, by marking
134 it complete, and resume the restore of the other sets.
135
136 help, ?
137 This causes the program to display the above possible responses,
138 with a small description of each.
139
140
141 Notes on tape error recovery: During a restore there are times when
142 errors occur which require special handling. Read data errors are
143 retried by the program up to eight times. If unable to read the data,
144 the error becomes unrecoverable. The recovery procedure will be
145 selected by the operator. One choice would be to perform the retry
146 attempts again. Another would be to skip this record and try to read
147 the next. The full list of possibilities are listed below.
148
149 When an unrecoverable error occurs a message will be displayed that
150 shows the error interpreted in english, with detailed status in hex if
151 required. The operator will be queried as to the course of action that
152 the program should take. Listed below is an example error output and
153 the possible responses and their meanings.
154
155
156 0423.6 restoreblue: Device Attention, Handler check on tapa_12.
157 detailed status: 20 8C 2B 6D 0A 01 16 00 00 16 48 87 24
158 18 06 00 00 0C 00 00 08 08 80 00 00 00
159 restore: Action:
160
161 abort
162 This causes the program to abort the entire restore and return to
163 BCE command level.
164
165 retry, r
166 For errors that are retryable this will force the retry process to
167 be redone. It is invalid for non-retryable errors.
168
169 skip, s
170 This is only valid for unrecoverable data alert errors detected
171 while doing a restore. The unreadable record is skipped and the
172 program continues by attempting to read the next record.
173
174 stop_set, stop
175 This will cause this SET to be aborted, but all other SETs will
176 continue.
177
178 restart_set, restart, rt
179 This allows the operator to restart this SET, using the current tape
180 device. The operator is then required to mount the "restart" tape
181 on the device. Once the SET has been restarted, the remaining SETs
182 will continue operation.
183
184 remove_device_from_set, remove
185 Works like the "restart_set" request above, but removes the current
186 tape device from the SET and sequences to the next device before
187 going through the restart process. This is not a valid response if
188 this is the only tape device left in the SET.
189
190 help, ?
191 This causes the program to display the above possible responses,
192 with a small description of each.