| blob | 5f2fa3c0159c88f3d027b83de1c4b0c32a705e9b |
1 '\" te
2 .\" Copyright (c) 2007, Sun Microsystems, Inc. All rights reserved.
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH IIADM 1M "Nov 26, 2017"
7 .SH NAME
8 iiadm \- command-line interface to control Sun StorageTek Availability Suite
9 Point-in-Time Copy operations
10 .SH SYNOPSIS
11 .LP
12 .nf
13 \fBiiadm\fR \fB-e\fR {ind | shd} \fImaster_vol\fR \fIshadow_vol\fR \fIbitmap_vol\fR
14 .fi
16 .LP
17 .nf
18 \fBiiadm\fR \fB-ne\fR ind \fImaster_vol\fR \fIshadow_vol\fR \fIbitmap_vol\fR
19 .fi
21 .LP
22 .nf
23 \fBiiadm\fR [\fB-p\fR] [\fB-n\fR] {\fB-c\fR | \fB-u\fR} {s | m} \fIvolume_set\fR
24 .fi
26 .LP
27 .nf
28 \fBiiadm\fR [\fB-adDilR\fR] \fIvolume_set\fR
29 .fi
31 .LP
32 .nf
33 \fBiiadm\fR [\fB-p\fR] [\fB-n\fR] \fB-w\fR \fIvolume_set\fR
34 .fi
36 .LP
37 .nf
38 \fBiiadm\fR [\fB-hilLv\fR]
39 .fi
41 .LP
42 .nf
43 \fBiiadm\fR \fB-P\fR \fIdelay\fR \fIunits\fR \fIvolume_set\fR
44 .fi
46 .LP
47 .nf
48 \fBiiadm\fR \fB-P\fR \fIvolume_set\fR
49 .fi
51 .LP
52 .nf
53 \fBiiadm\fR \fB-A\fR \fIoverflow_vol\fR \fIvolume_set\fR
54 .fi
56 .LP
57 .nf
58 \fBiiadm\fR [\fB-OQ\fR] \fIoverflow_vol\fR
59 .fi
61 .LP
62 .nf
63 \fBiiadm\fR \fB-E\fR \fIvolume_set\fR
64 .fi
66 .LP
67 .nf
68 \fBiiadm\fR [\fB-IJ\fR] \fIvolume_set\fR \fIbitmap\fR
69 .fi
71 .LP
72 .nf
73 \fBiiadm\fR \fB-g\fR \fIgroup_name\fR [\fB-aAcdDeEilLmPRuw\fR]
74 .fi
76 .LP
77 .nf
78 \fBiiadm\fR [\fB-C\fR] \fIcluster_tag\fR [\fIoptions\fR]
79 .fi
81 .SH DESCRIPTION
82 .LP
83 Point-in-Time Copy software is a point-in-time snapshot feature of the Solaris
84 operating system.
85 .sp
86 .LP
87 A Point-in-Time Copy snapshot is an instantly-available, time-fixed, replicated
88 view of a momentarily quiesced volume. Once a snapshot is taken, Point-in-Time
89 Copy software allows immediate read/write access to both the master and shadow
90 volume data.
91 .sp
92 .LP
93 Point-in-Time Copy software tracks the differences between the master and
94 shadow volumes (caused by writes) from the moment that the snapshot was
95 established. This capability allows applications accessing the master volume's
96 data to move forward in time independently of applications accessing the shadow
97 volume's data, and vice-versa.
98 .sp
99 .LP
100 The Point-in-Time Copy software's tracking of differences between the master
101 and shadow volumes facilitates a fast resynchronization or a full copy at a
102 later time. The volume resynchronization can occur from either shadow to master
103 or master to shadow.
104 .sp
105 .LP
106 Instantly after the point-in-time is (re-)established (either when the CLI
107 prompt returns or the next shell script command is read), the master volume can
108 be remounted or the applications using them can be resumed. Also, the shadow
109 volume can be mounted and immediately accessed.
110 .sp
111 .LP
112 The \fBiiadm\fR command line utility performs only one action per command
113 invocation. Because of this, you cannot combine multiple options, except in
114 combination with the following overall command modifiers:
115 .RS +4
116 .TP
117 .ie t \(bu
118 .el o
119 If no action item is entered, \fBiiadm\fR displays the list of Point-in-Time
120 Copy sets (non-suspended) currently configured. If more than one action item,
121 or an incorrectly specified action item is entered, \fBiiadm\fR displays the
122 specific error message to stderr, followed by a brief usage summary.
123 .RE
124 .RS +4
125 .TP
126 .ie t \(bu
127 .el o
128 For the Point-in-Time Copy options ENABLE (\fB-e\fR), COPY (\fB-c\fR) and
129 UPDATE (\fB-u\fR), there are two associated shadow volume selection qualifiers,
130 \fB{ind|dep}\fR, that are used to specify the type of Point-in-Time Copy volume
131 set to create.
132 .RE
133 .sp
134 .LP
135 An independent (\fBind\fR) snapshot causes Point-in-Time Copy software to
136 perform a full volume copy operation from the master to the shadow. When the
137 copy completes, the shadow volume data is identical to the master volume data
138 at the moment that it was established. Create an independent shadow if you
139 require two physical copies of the data. An independent shadow volume must be
140 the same size or greater than the size of the master volume. Sun recommends
141 that the master and shadow volumes be the same size for environments where
142 resynchronization from shadow to master is a consideration.
143 .sp
144 .LP
145 A dependent (\fBdep\fR) snapshot causes Point-in-Time Copy software not to
146 perform a full volume copy. The resulting shadow volume relies on the master
147 volume for all unmodified data blocks, which are not copied until requested.
148 Create a dependent shadow when you do not require two physical copies of the
149 data. A dependent shadow volume can be either the same size or smaller than the
150 master volume. A smaller shadow volume is called a \fBCompact Dependent Shadow
151 Volume\fR, and is typically used when the amount of change that occurs to a
152 Point-in-Time Copy volume set is small compared to the entire size of the
153 master volume.
154 .sp
155 .LP
156 The following syntax allows you to create an exportable independent shadow
157 volume in a Sun Cluster environment:
158 .sp
159 .in +2
160 .nf
161 # iiadm -ne ind master shadow bitmap
162 .fi
163 .in -2
164 .sp
166 .sp
167 .LP
168 An issue arises when using a Compact Dependent Shadow Volume in that its size
169 is established at the time that the Point-in-Time Copy volume set is enabled.
170 If the amount of change to the entire volume set over the duration of its usage
171 exceeds the space allocated for the shadow volume, the shadow volume is marked
172 as out of space. It is possible to read from the shadow volume even after it is
173 out of space, until a portion of the data for which there was no room is
174 requested. Once that happens, the read fails and the shadow volume is marked
175 offline.
176 .sp
177 .LP
178 To address this issue, Point-in-Time Copy supports the ability to associate an
179 \fBoverflow\fR volume to an existing Point-in-Time Copy dependent volume set.
180 Thus, if the size of the Compact Dependent Shadow Volume is too small, or an
181 unscheduled amount of change occurs to the volume set, changed data can be
182 redirected to the associated overflow volume. To facilitate efficient usage of
183 this overflow volume, it can be associated with multiple Point-in-Time Copy
184 volume sets on an as-needed basis.
185 .SS "Considerations"
186 .LP
187 Prior to invoking an Point-in-Time Copy \fBenable\fR, \fBcopy\fR or
188 \fBupdate\fR operation, Point-in-Time Copy assures that the shadow volume is
189 not mounted, to prevent a file system panic from occurring. Also, it is
190 suggested that you either unmount or suspend (quiesce) all applications using
191 the master volume, for only the instant when the point-in-time snapshot is
192 taken. This assures that an atomically consistent point-in-time snapshot is
193 taken.
194 .sp
195 .LP
196 It is suggested that, if the master volume was suspended rather than unmounted,
197 the new point-in-time shadow volume's integrity be validated using volume
198 validation utilities, such as \fBfsck\fR(1M). The reason is that Point-in-Time
199 Copy has made a point-in-time copy of a \fBmounted\fR master volume to an
200 \fBunmounted\fR shadow volume. During the mounting of the shadow volume, the
201 file system detects that it is in the \fBmounted\fR state. Typically this state
202 occurs only when a system crashes, so the file system attempts to validate the
203 integrity of the volume assuming a system failure occurred, not an
204 Point-in-Time Copy.
205 .SS "ENVIRONMENT OPTIONS"
206 .LP
207 The \fBii_bitmap\fR variable in the \fB/usr/kernel/drv/ii.conf\fR configuration
208 file determines the bitmap volume operational semantics as follows:
209 .sp
210 .ne 2
211 .na
212 \fB\fB0\fR\fR
213 .ad
214 .RS 13n
215 Indicates that the bitmap is maintained in memory only or resume operation.
216 .RE
218 .sp
219 .ne 2
220 .na
221 \fB\fB1\fR\fR
222 .ad
223 .RS 13n
224 Indicates that the bitmap is maintained in memory and on disk. This is the
225 default value.
226 .RE
228 .sp
229 .LP
230 If a system failure occurs while using \fBii_bitmap=0\fR, the shadow volume
231 might be inconsistent and fast resynchronization would not be possible.
232 .sp
233 .LP
234 If Point-in-Time Copy is used in conjunction with the Network Storage component
235 Remote Mirror or in a Sun Cluster, set \fBii_bitmap=1\fR.
236 .sp
237 .LP
238 The \fBii_debug\fR variable in the \fB/usr/kernel/drv/ii.conf\fR configuration
239 file determines the amount of information logging that is output to the system
240 console \fB/dev/console\fR during Point-in-Time Copy processing.
241 .sp
242 .ne 2
243 .na
244 \fB\fB0\fR\fR
245 .ad
246 .RS 13n
247 Indicates that no logging is sent to the system console.
248 .RE
250 .sp
251 .ne 2
252 .na
253 \fB\fB1\fR\fR
254 .ad
255 .RS 13n
256 Indicates that informational logging is sent to the system console.
257 .RE
259 .sp
260 .ne 2
261 .na
262 \fB\fB2\fR\fR
263 .ad
264 .RS 13n
265 Indicates that developmental logging is sent to the system console.
266 .RE
268 .SH OPTIONS
269 .LP
270 The \fBiiadm\fR utility supports the following options.
271 .sp
272 .ne 2
273 .na
274 \fB\fB-e\fR\fB{ind|dep}\fR \fImaster_vol shadow_vol bitmap_vol\fR\fR
275 .ad
276 .sp .6
277 .RS 4n
278 Enable Point-in-Time Copy for the specified master, shadow, and bitmap volumes.
279 .sp
280 The enable shadow set processing assures that the specified volumes are
281 accessible, that the \fIshadow_vol\fR is not mounted, and that the
282 \fIbitmap_vol\fR is correctly sized for the type of shadow set being created.
283 Additionally, it assures that the volumes are under control of the SV driver (
284 if they are not, it puts them there), initializes the bitmap volume, and, if
285 the volume set is an independent shadow set, a full copy operation is
286 initiated.
287 .sp
288 On a successful enable, Point-in-Time Copy stores the specified
289 \fImaster_vol\fR, \fIshadow_vol\fR and \fIbitmap_vol\fR names, plus the
290 enabling type (\fBind\fR or \fBdep\fR), into the Point-in-Time Copy
291 configuration store. The configuration store contains all currently configured
292 Point-in-Time Copy Volume Sets and their associated configuration attributes.
293 (See discussion above on independent and dependent shadow volume semantics.)
294 .sp
295 \fImaster_vol\fR is the volume from which a point-in-time snapshot is made.
296 .sp
297 \fIshadow_vol\fR is the volume that contains the point-in-time snapshot.
298 .sp
299 \fIbitmap_vol\fR is used for tracking differences between the shadow and master
300 volumes. When Point-in-Time Copy shadow operations are suspended or resumed,
301 the bitmap volume (maintained in kernel memory) can be stored in or retrieved
302 from permanent storage. The storage associated with the bitmap volume should be
303 as redundant as that of the shadow volume storage.
304 .sp
305 The \fIshadow_vol\fR name is the name that the Point-in-Time Copy Shadow Set is
306 known by for all \fBiiadm\fR options requiring specification of a
307 \fIvolume_set\fR name.
308 .RE
310 .sp
311 .ne 2
312 .na
313 \fB\fB-d\fR \fIvolume_set\fR\fR
314 .ad
315 .sp .6
316 .RS 4n
317 Disable the Point-in-Time Copy volume set associated with the specified
318 \fIvolume_set\fR.
319 .sp
320 If Point-in-Time Copy was running in \fBindependent\fR mode as specified in the
321 \fB-e\fR \fBind\fR options, above, the shadow volume data contains the same
322 data as it did before it was disabled (assuming no writes have occurred). Users
323 can access the master and shadow volumes, as they are now standalone
324 point-in-time copies.
325 .sp
326 During the time that the full copy is active, an \fBindependent\fR volume
327 operates as though it is a \fBdependent\fR volume. To assure that the volume is
328 no longer in full copy mode, issue the following command to wait for the full
329 copy to complete:
330 .sp
331 .in +2
332 .nf
333 # iiadm -w \fIvolume_set\fR
334 .fi
335 .in -2
336 .sp
338 .RE
340 .sp
341 .ne 2
342 .na
343 \fB[\fB-p\fR] \fB-u\fR \fBs\fR \fIvolume_set\fR\fR
344 .ad
345 .sp .6
346 .RS 4n
347 Update the shadow volume from the master.
348 .sp
349 Updates a point-in-time copy of the master volume to the shadow volume.
350 \fIvolume_set\fR is the Point-in-Time Copy shadow set containing the master and
351 shadow volumes. This option provides a fast resynchronization of the shadow
352 volume, creating an incremental copy of the master. This update copies all 32KB
353 segments flagged as different between the master and shadow volumes. It does
354 not copy all master volume data, only changed data. While the data is being
355 copied, the shadow is dependent upon the master volume.
356 .sp
357 Before using this option, momentarily quiesce the workload to the volumes; stop
358 the host application from writing to the volumes. This ensures that the
359 point-in-time data is consistent. You can visually check the status of this
360 copy or update operation with \fBiiadm\fR \fB-i\fR \fIvolume_set\fR, or
361 interactively (by means of a shell or script) with \fBiiadm\fR \fB-w\fR
362 \fIvolume_set\fR, before using the target volume for any other operations.
363 .sp
364 This command supports PID (Process IDentifier) locking, by using the option
365 \fB-p\fR, \fBiiadm\fR \fB-p\fR \fB-u\fR \fBs\fR. Enabling this option prevents
366 other processes from taking a new point-in-time snapshot, thus invalidating
367 prior point-in-time data.
368 .RE
370 .sp
371 .ne 2
372 .na
373 \fB[\fB-p\fR] [\fB-n\fR] \fB-u\fR \fBm\fR \fIvolume_set\fR\fR
374 .ad
375 .sp .6
376 .RS 4n
377 Updates a point-in-time copy of the master volume from the shadow.
378 \fIvolume_set\fR is the Point-in-Time Copy volume set containing the master and
379 shadow. This option provides a fast resynchronization of the master volume,
380 creating an incremental copy of the shadow. This update copies all 32KB
381 segments flagged as different between the master and shadow volumes. It does
382 not copy all shadow volume data, only changed data. While the data is being
383 copied, the master is dependent upon the shadow volume.
384 .sp
385 Before using this option, momentarily quiesce the workload to the volumes; stop
386 the host application from writing to the volumes. This ensures that the
387 point-in-time data is consistent. You can visually check the status of this
388 copy or update operation with \fBiiadm\fR \fB-i\fR \fIvolume_set\fR, or
389 interactively (by means of a shell or script) with \fBiiadm\fR \fB-w\fR
390 \fIvolume_set\fR, before using the target volume for any other operations.
391 .sp
392 This command is query enabled to prevent accidentally overwriting the data on a
393 master volume. When this command option is used in scripts, add the \fB-n\fR
394 option to prevent the query from occurring.
395 .sp
396 This command supports PID (Process IDentifier) locking, by using the option
397 \fB-p\fR, \fBiiadm\fR \fB-p\fR \fB-u\fR \fBm\fR. Enabling this option prevents
398 other processes from taking a new point-in-time snapshot, thus invalidating
399 prior point-in-time data.
400 .RE
402 .sp
403 .ne 2
404 .na
405 \fB[\fB-p\fR] \fB-c\fR s \fIvolume_set\fR\fR
406 .ad
407 .sp .6
408 .RS 4n
409 Copy the master volume to the shadow.
410 .sp
411 Creates a point-in-time copy of the master volume to the shadow volume.
412 \fIvolume_set\fR is the Point-in-Time Copy volume set containing the master and
413 shadow. This option writes all data in the point-in-time copy of the master
414 volume to the shadow volume. While the data is being copied from master to
415 shadow, the shadow is dependent on the master volume.
416 .sp
417 This option performs a full volume copy. Use \fBiiadm\fR \fB-u\fR \fBs\fR
418 unless the integrity of the data on the independent shadow volume is in doubt.
419 Otherwise, use this option to synchronize the master and shadow volumes; that
420 is, make the data on each volume match.
421 .sp
422 Before using this option, momentarily quiesce the workload to the volumes; stop
423 the host application from writing to the volumes. This ensures that the
424 point-in-time data is consistent. You can visually check the status of this
425 copy or update operation with \fBiiadm\fR \fB-i\fR \fIvolume_set\fR, or
426 interactively (by means of a shell or script) with \fBiiadm\fR \fB-w\fR
427 \fIvolume_set\fR, before using the target volume for any other operations.
428 .sp
429 This command supports PID (Process IDentifier) locking, by using the \fB-p\fR
430 option, \fBiiadm\fR \fB-p\fR \fB-c\fR \fBs\fR. Enabling this option prevents
431 other processes from taking a new point-in-time snapshot, thus invalidating
432 prior point-in-time data.
433 .RE
435 .sp
436 .ne 2
437 .na
438 \fB\fB-c\fR \fBm\fR \fIvolume_set\fR\fR
439 .ad
440 .sp .6
441 .RS 4n
442 Copy the shadow volume to the master.
443 .sp
444 Creates a point-in-time copy of the shadow volume to the master volume.
445 \fIvolume_set\fR is the Point-in-Time Copy volume set containing the master and
446 shadow volumes. This option writes all data in the point-in-time copy of the
447 shadow volume to the master volume. While the data is being copied from the
448 shadow to the master, the master is dependent upon the shadow volume.
449 .sp
450 This option performs a full volume copy. Use \fBiiadm\fR \fB-u\fR \fBm\fR
451 unless the integrity of the data on the independent master is in doubt.
452 Otherwise, use this option to synchronize the master and shadow volumes; that
453 is, make the data on each volume match.
454 .sp
455 Before using this option, momentarily quiesce the workload to the volumes; stop
456 the host application from writing to the volumes. This ensures that the
457 point-in-time data is consistent. You can visually check the status of this
458 copy or update operation with \fBiiadm\fR \fB-i\fR \fIvolume_set\fR, or
459 interactively (by means of a shell or script) with \fBiiadm\fR \fB-w\fR
460 \fIvolume_set\fR, before using the target volume for any other operations.
461 .sp
462 This command is query-enabled to prevent accidentally overwriting the data on a
463 master volume. When this command option is used in scripts, add the \fB-n\fR
464 option to prevent the query from occurring.
465 .sp
466 This command supports PID (Process IDentifier) locking, by using the \fB-p\fR
467 option, \fBiiadm\fR \fB-p\fR \fB-c\fR \fBm\fR. Enabling this option prevents
468 other processes from taking a new point-in-time snapshot, thus invalidating
469 prior point-in-time data.
470 .RE
472 .sp
473 .ne 2
474 .na
475 \fB\fB-a\fR \fIvolume_set\fR\fR
476 .ad
477 .sp .6
478 .RS 4n
479 Abort any current copy operation that might be active between the master and
480 shadow volumes. \fIvolume_set\fR is the Point-in-Time Copy volume set
481 containing the master and shadow volumes. After executing \fBiiadm\fR \fB-a\fR,
482 the update or copy to the target (master or shadow) volume is incomplete. The
483 target volume is now a dependent copy of the source volume. Reissue the update
484 or copy command option to resynchronize the volumes.
485 .RE
487 .sp
488 .ne 2
489 .na
490 \fB\fB[\fR\fB-p\fR\fB] [\fR\fB-n\fR\fB] \fR\fB-w\fR \fIvolume_set\fR\fR
491 .ad
492 .sp .6
493 .RS 4n
494 Wait until any in-progress copy or update operation completes or is aborted.
495 \fIvolume_set\fR is the Point-in-Time Copy volume set containing the master and
496 shadow volumes.
497 .sp
498 This option waits until the current Point-in-Time Copy operation is complete,
499 thus preventing a subsequent \fBiiadm\fR command (from a shell or script) from
500 executing. Use this command option when you need to be sure the copy or update
501 operation has completed.
502 .sp
503 This command supports PID (Process IDentifier) unlocking. If a prior copy or
504 update, using a command \fBiiadm\fR \fB-p\fR \fB{\fR\fB-c\fR\fB|\fR\fB-u\fR\fB}
505 {m|s}\fR, was invoked with the \fB-p\fR option, upon completion of the wait
506 processing, if the current PID was the PID that locked the point-in-time data,
507 this option unlocks the data.
508 .RE
510 .sp
511 .ne 2
512 .na
513 \fB\fB-i\fR \fIvolume_set\fR\fR
514 .ad
515 .sp .6
516 .RS 4n
517 Display status for the Point-in-Time Copy currently-enabled or -suspended
518 volume set. \fIvolume_set\fR is the Point-in-Time Copy volume set containing
519 the master and shadow volumes. If no \fIvolume_set\fR is specified, status is
520 displayed for all Point-in-Time Copy volume sets that are configured.
521 .RE
523 .sp
524 .ne 2
525 .na
526 \fB\fB-l\fR\fR
527 .ad
528 .sp .6
529 .RS 4n
530 List all currently configured Point-in-Time Copy volumes.
531 .RE
533 .sp
534 .ne 2
535 .na
536 \fB\fB-O\fR \fIoverflow_vol\fR\fR
537 .ad
538 .sp .6
539 .RS 4n
540 This option causes Point-in-Time Copy to initialize the specified
541 \fIoverflow_vol\fR for subsequent use as an overflow volume in conjunction with
542 Compact Dependent Shadow Volumes. To facilitate efficient, shared usage of this
543 overflow volume, it can be associated with multiple Point-in-Time Copy volume
544 sets on an as-needed basis.
545 .sp
546 During initialization of the \fIoverflow_vol\fR, the initiator of this option,
547 must answer the following question: "Initialize this overflow volume? yes/no" A
548 response of either "yes/no" is required before proceeding.
549 .sp
550 This option supports the \fB-n\fR option, so that the requested action is
551 performed without prompting. This option is useful for inclusion in a script.
552 The \fB-n\fR option must be specified first. For example, "\fBiiadm\fR
553 \fB-nO\fR \fBvol\fR" is valid; "\fBiiadm\fR \fB-On\fR \fBvol\fR" is not.
554 .sp
555 Make sure you want to initialize the data on the specified \fIoverflow_vol\fR,
556 especially when using the \fB-n\fR option.
557 .RE
559 .sp
560 .ne 2
561 .na
562 \fB\fB-A\fR \fIoverflow_vol\fR \fIvolume_set\fR\fR
563 .ad
564 .sp .6
565 .RS 4n
566 This option enables the specified \fIoverflow_vol\fR, for subsequent use as an
567 overflow volume in a situation where the size of the Compact Dependent Shadow
568 Volume is too small, or an unscheduled amount of change occurs to the volume
569 set. Overflow changed data would be redirected to the associated overflow
570 volume. \fIvolume_set\fR is the Point-in-Time Copy volume set containing the
571 master and shadow volumes.
572 .sp
573 If the \fIoverflow_vol\fR has not been initialized, this option initializes the
574 \fIoverflow_vol\fR (see \fB-O\fR option), then attaches the \fIoverflow_vol\fR
575 to the \fIvolume_set\fR.
576 .sp
577 If \fIoverflow_vol\fR was previously initialized, this option attaches the
578 \fIoverflow_vol\fR to the \fIvolume_set\fR.
579 .sp
580 This option supports the \fB-n\fR option, so that the requested action is
581 performed without prompting. This option is useful for inclusion in a script.
582 The \fB-n\fR option must be specified first. For example, "\fBiiadm\fR
583 \fB-nA\fR \fBvol\fR" is valid; "\fBiiadm\fR \fB-An\fR \fBvol\fR" is not.
584 .sp
585 Make sure you want to initialize the data on the specified \fIoverflow_vol\fR,
586 especially when using the \fB-n\fR option.
587 .RE
589 .sp
590 .ne 2
591 .na
592 \fB\fB-D\fR \fIvolume_set\fR\fR
593 .ad
594 .sp .6
595 .RS 4n
596 This option removes the overflow volume currently associated with the specified
597 \fIvolume_set\fR. If the overflow volume is currently in use by the
598 \fIvolume_set\fR, this operation fails with an "Overflow volume still in use"
599 error message. To resolve this situation, perform one of the operations
600 described below on the \fIvolume_set\fR. These operations momentarily clear out
601 all overflow writes that are associated with this volume set.
602 .sp
603 .ne 2
604 .na
605 \fB\fBabort\fR(\fB-a\fR)\fR
606 .ad
607 .sp .6
608 .RS 4n
609 Abort copy operation.
610 .RE
612 .sp
613 .ne 2
614 .na
615 \fB\fBdisable\fR(\fB-d\fR)\fR
616 .ad
617 .sp .6
618 .RS 4n
619 Dissolve the volume set.
620 .RE
622 .sp
623 .ne 2
624 .na
625 \fB\fBupdate\fR(\fB-u\fR)\fR
626 .ad
627 .sp .6
628 .RS 4n
629 Update the volume set.
630 .RE
632 .RE
634 .sp
635 .ne 2
636 .na
637 \fB\fB-L\fR\fR
638 .ad
639 .sp .6
640 .RS 4n
641 This option lists all overflow volumes which are associated with one or more
642 volume sets.
643 .RE
645 .sp
646 .ne 2
647 .na
648 \fB\fB-Q\fR \fIoverflow_vol\fR\fR
649 .ad
650 .sp .6
651 .RS 4n
652 This option displays the current status of the \fIoverflow_vol\fR.
653 .RE
655 .sp
656 .ne 2
657 .na
658 \fB\fB-E\fR \fIvolume_set\fR\fR
659 .ad
660 .sp .6
661 .RS 4n
662 Export the independent shadow volume of the Point-in-Time Copy volume set
663 specified by \fIvolume_set\fR. The shadow volume is to be made available to
664 another host for read/write access, by means of an enabling technology, such as
665 multi-ported devices. This other host is responsible for maintaining a bitmap
666 of differences that is used to merge with locally recorded differences to the
667 master when the shadow volume is rejoined to its master volume. While a shadow
668 volume is exported it must not be subject to an update or copy operation.
669 Perform an \fBiiadm\fR \fB-w\fR \fIvolume_set\fR command prior to invoking an
670 export command.
671 .RE
673 .sp
674 .ne 2
675 .na
676 \fB\fB-I\fR \fIvolume_set\fR \fIbitmap_vol\fR\fR
677 .ad
678 .sp .6
679 .RS 4n
680 Import the independent shadow volume of the Point-in-Time Copy volume set
681 specified by \fIvolume_set\fR. The shadow volume must have been previously
682 exported from a host by means of an enabling technology, such as multi-ported
683 devices. The import operation causes this host to start maintaining a bitmap of
684 differences as the volume is modified. The \fIbitmap_vol\fR should not be the
685 same as that used when the shadow volume was originally formed into a shadow
686 group.
687 .sp
688 After the exported/imported independent shadow volume is no longer needed by
689 the other node, you must enter a disable command so that the \fIbitmap_vol\fR
690 and its associated \fIshadow_vol\fR are consistent, prior to performing a join
691 operation. For example,
692 .sp
693 .in +2
694 .nf
695 # iiadm -d \fIvolume_set\fR
696 .fi
697 .in -2
698 .sp
700 .RE
702 .sp
703 .ne 2
704 .na
705 \fB\fB-J\fR \fIvolume_set\fR \fIbitmap_vol\fR\fR
706 .ad
707 .sp .6
708 .RS 4n
709 Join the \fIvolume_set\fR, using the \fIbitmap_vol\fR, with the master volume
710 set of the Point-in-Time Copy volume set. The bitmap volume supplied is read
711 and merged with the original volume to reconstruct the original volume set
712 consisting of the master, shadow, and bitmap volumes. The \fIbitmap_vol\fR to
713 be merged is the one obtained on the node that had imported the independent
714 shadow volume. There must be no write activity to the shadow volume on the
715 importing machine from the time the bitmap is copied over until the shadow is
716 once again imported.
717 .RE
719 .sp
720 .ne 2
721 .na
722 \fB\fB-g\fR \fIgroup_name\fR \fB-m\fR \fIvolume_set [volume_set2 ...]\fR\fR
723 .ad
724 .sp .6
725 .RS 4n
726 Add one or more existing Point-in-Time Copy \fIvolume_set(s)\fR into a user
727 specified \fIgroup_name\fR. This association of one or more Point-in-Time Copy
728 volume sets in a group allows the list of \fBiiadm\fR options shown below to be
729 performed on all volume sets within the \fIgroup_name\fR as a whole.
730 .sp
731 Only the commands \fBCOPY\fR (\fB-c\fR) and \fBUPDATE\fR (\fB-u\fR) are
732 performed atomically across all Point-in-Time Copy sets within the group. All
733 other grouped, \fBiiadm\fR commands are performed sequentially on each member
734 of the group.
735 .sp
736 The syntax of an \fBiiadm\fR group command is as follows:
737 .sp
738 .in +2
739 .nf
740 iiadm -g \fIgroup_name\fR [\fIoptions\fR]
741 .fi
742 .in -2
743 .sp
745 The \fIoptions\fR are as follows:
746 .sp
747 .ne 2
748 .na
749 \fB\fB-a\fR\fR
750 .ad
751 .sp .6
752 .RS 4n
753 Abort copy operation on all sets within \fIgroup_name\fR.
754 .RE
756 .sp
757 .ne 2
758 .na
759 \fB\fB-A\fR\fR
760 .ad
761 .sp .6
762 .RS 4n
763 Attach \fIoverflow_vol\fR to all sets within \fIgroup_name\fR.
764 .RE
766 .sp
767 .ne 2
768 .na
769 \fB\fB-c\fR \fB{s | m}\fR\fR
770 .ad
771 .sp .6
772 .RS 4n
773 Copy shadow/master for all sets within \fIgroup_name\fR.
774 .RE
776 .sp
777 .ne 2
778 .na
779 \fB\fB-D\fR\fR
780 .ad
781 .sp .6
782 .RS 4n
783 Detach \fIoverflow_vol\fR from all sets within \fIgroup_name\fR.
784 .RE
786 .sp
787 .ne 2
788 .na
789 \fB\fB-d\fR\fR
790 .ad
791 .sp .6
792 .RS 4n
793 Disable all sets within \fIgroup_name\fR.
794 .RE
796 .sp
797 .ne 2
798 .na
799 \fB\fB-E\fR\fR
800 .ad
801 .sp .6
802 .RS 4n
803 Export all volume sets within \fIgroup_name\fR.
804 .RE
806 .sp
807 .ne 2
808 .na
809 \fB\fB-i\fR\fR
810 .ad
811 .sp .6
812 .RS 4n
813 Status of all volume sets within \fIgroup_name\fR.
814 .RE
816 .sp
817 .ne 2
818 .na
819 \fB\fB-l\fR\fR
820 .ad
821 .sp .6
822 .RS 4n
823 List all volume sets within \fIgroup_name\fR.
824 .RE
826 .sp
827 .ne 2
828 .na
829 \fB\fB-L\fR\fR
830 .ad
831 .sp .6
832 .RS 4n
833 List all groups.
834 .RE
836 .sp
837 .ne 2
838 .na
839 \fB\fB-n\fR\fR
840 .ad
841 .sp .6
842 .RS 4n
843 Do not ask if an update of the master volume is what the user really intended.
844 .RE
846 .sp
847 .ne 2
848 .na
849 \fB\fB-P\fR\fR
850 .ad
851 .sp .6
852 .RS 4n
853 Set parameters on all volume sets within \fIgroup_name\fR.
854 .RE
856 .sp
857 .ne 2
858 .na
859 \fB\fB-R\fR\fR
860 .ad
861 .sp .6
862 .RS 4n
863 Reset all volume sets within \fIgroup_name\fR.
864 .RE
866 .sp
867 .ne 2
868 .na
869 \fB\fB-u\fR \fB{s | m}\fR\fR
870 .ad
871 .sp .6
872 .RS 4n
873 Update shadow/master for all sets within \fIgroup_name\fR.
874 .RE
876 .sp
877 .ne 2
878 .na
879 \fB\fB-w\fR\fR
880 .ad
881 .sp .6
882 .RS 4n
883 Wait for all volume sets within \fIgroup_name\fR.
884 .RE
886 .RE
888 .sp
889 .ne 2
890 .na
891 \fB\fB-g\fR \fB""\fR \fB-m\fR \fIvolume_set\fR [\fIvolume_set2 ...\fR]\fR
892 .ad
893 .sp .6
894 .RS 4n
895 Remove one or more existing Point-in-Time Copy \fIvolume_set(s)\fR from their
896 currently associated \fIgroup_name\fR. By default, or until moved into a user
897 specified \fIgroup_name\fR, all Point-in-Time Copy \fIvolume_set(s)\fR are in
898 the blank (\fB" "\fR) group. This association allows all the previously
899 documented \fBiiadm\fR group commands to be performed against the blank (\fB"
900 "\fR) \fBiiadm\fR \fIgroup_name\fR.
901 .RE
903 .sp
904 .ne 2
905 .na
906 \fB\fB-C\fR \fIcluster_tag\fR\fR
907 .ad
908 .sp .6
909 .RS 4n
910 This Point-in-Time Copy option is a modifier that limits configuration
911 operations to only those volumes belonging to a Sun Cluster Resource Group, or
912 Disk Group.
913 .sp
914 In a Sun Cluster where the volume manager is Sun Cluster-aware, \fBiiadm\fR
915 automatically obtains the correct Disk Group information, therefore this option
916 is typically not required unless the volumes are part of an encompassing
917 Resource Group.
918 .sp
919 In a Sun Cluster where the volumes are accessible on the local node only, the
920 special \fIcluster_tag\fR of \fBlocal\fR is used to indicate volumes that are
921 not part of a Sun Cluster Resource Group or Disk Group.
922 .sp
923 If "\fB-L\fR" is given as a the \fIcluster_tag\fR argument, then \fBiiadm\fR
924 lists all cluster tags associated with Point-in-Time Copy.
925 .sp
926 This option is invalid when used on a Solaris system on which the Sun Cluster
927 package has not been installed or configured.
928 .RE
930 .sp
931 .ne 2
932 .na
933 \fB\fB-h\fR\fR
934 .ad
935 .sp .6
936 .RS 4n
937 Prints the \fBiiadm\fR usage summary.
938 .RE
940 .sp
941 .ne 2
942 .na
943 \fB\fB-v\fR\fR
944 .ad
945 .sp .6
946 .RS 4n
947 Display the current version of the Point-in-Time Copy software components.
948 .RE
950 .sp
951 .LP
952 Contact Sun Enterprise Services for assistance in using the remaining commands
953 in this section.
954 .sp
955 .ne 2
956 .na
957 \fB\fB-P\fR \fIdelay\fR \fIunit\fR \fIvolume_set\fR\fR
958 .ad
959 .sp .6
960 .RS 4n
961 Alter the Point-in-Time Copy volume set tuning parameters for the specified
962 \fIvolume_set\fR to \fIdelay\fR ticks, every \fIunit\fR I/O's. Delay ranges
963 from 2 to 10000 inclusive; unit ranges from 100 to 60000 inclusive.
964 .RE
966 .sp
967 .ne 2
968 .na
969 \fB\fB-R\fR \fIvolume\fR\fR
970 .ad
971 .sp .6
972 .RS 4n
973 After a volume has failed, Point-in-Time Copy places it offline. After
974 replacing the volume, place it back online using this option. Associated
975 dependent volumes in the Point-in-Time Copy volume set are also placed online.
976 After the volume is placed online, this command also starts any necessary
977 point-in-time volume updates.
978 .RE
980 .SH EXIT STATUS
981 .ne 2
982 .na
983 \fB\fB0\fR\fR
984 .ad
985 .RS 13n
986 Command completed successfully.
987 .RE
989 .sp
990 .ne 2
991 .na
992 \fB\fB>0\fR\fR
993 .ad
994 .RS 13n
995 An error occurred.
996 .RE
998 .SH ATTRIBUTES
999 .LP
1000 See \fBattributes\fR(5) for descriptions of the following attributes:
1001 .sp
1003 .sp
1004 .TS
1005 box;
1006 c | c
1007 l | l .
1008 ATTRIBUTE TYPE ATTRIBUTE VALUE
1009 _
1010 Interface Stability Evolving
1011 .TE
1013 .SH SEE ALSO
1014 .LP
1015 \fBdscfg\fR(1M), \fBsvadm\fR(1M), \fBds.log\fR(4), \fBrdc.cf\fR(4),
1016 \fBattributes\fR(5), \fBii\fR(7D), \fBsv\fR(7D)