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