1iiadm(1M) System Administration Commands iiadm(1M)
2
6 iiadm - command-line interface to control Sun StorageTek Availability
7 Suite Point-in-Time Copy operations
8
10 iiadm -e {ind | shd} master_vol shadow_vol bitmap_vol
11 iiadm -ne ind master_vol shadow_vol bitmap_vol
14 iiadm [-p] [-n] {-c | -u} {s | m} volume_set
17 iiadm [-adDilR] volume_set
20 iiadm [-p] [-n] -w volume_set
23 iiadm [-hilLv]
26 iiadm -P delay units volume_set
29 iiadm -P volume_set
32 iiadm -A overflow_vol volume_set
35 iiadm [-OQ] overflow_vol
38 iiadm -E volume_set
41 iiadm [-IJ] volume_set bitmap
44 iiadm -g group_name [-aAcdDeEilLmPRuw]
47 iiadm [-C] cluster_tag [options]
50
53 Point-in-Time Copy software is a point-in-time snapshot feature of the
54 Solaris operating system.
55 A Point-in-Time Copy snapshot is an instantly-available, time-fixed,
58 replicated view of a momentarily quiesced volume. Once a snapshot is
59 taken, Point-in-Time Copy software allows immediate read/write access
60 to both the master and shadow volume data.
61 Point-in-Time Copy software tracks the differences between the master
64 and shadow volumes (caused by writes) from the moment that the snapshot
65 was established. This capability allows applications accessing the mas‐
66 ter volume's data to move forward in time independently of applications
67 accessing the shadow volume's data, and vice-versa.
68 The Point-in-Time Copy software's tracking of differences between the
71 master and shadow volumes facilitates a fast resynchronization or a
72 full copy at a later time. The volume resynchronization can occur from
73 either shadow to master or master to shadow.
74 Instantly after the point-in-time is (re-)established (either when the
77 CLI prompt returns or the next shell script command is read), the mas‐
78 ter volume can be remounted or the applications using them can be
79 resumed. Also, the shadow volume can be mounted and immediately
80 accessed.
81 The iiadm command line utility performs only one action per command
84 invocation. Because of this, you cannot combine multiple options,
85 except in combination with the following overall command modifiers:
86 o If no action item is entered, iiadm displays the list of
88 Point-in-Time Copy sets (non-suspended) currently config‐
89 ured. If more than one action item, or an incorrectly speci‐
90 fied action item is entered, iiadm displays the specific
91 error message to stderr, followed by a brief usage summary.
92 o For the Point-in-Time Copy options ENABLE (-e), COPY (-c)
94 and UPDATE (-u), there are two associated shadow volume
95 selection qualifiers, {ind|dep}, that are used to specify
96 the type of Point-in-Time Copy volume set to create.
97 An independent (ind) snapshot causes Point-in-Time Copy software to
100 perform a full volume copy operation from the master to the shadow.
101 When the copy completes, the shadow volume data is identical to the
102 master volume data at the moment that it was established. Create an
103 independent shadow if you require two physical copies of the data. An
104 independent shadow volume must be the same size or greater than the
105 size of the master volume. Sun recommends that the master and shadow
106 volumes be the same size for environments where resynchronization from
107 shadow to master is a consideration.
108 A dependent (dep) snapshot causes Point-in-Time Copy software not to
111 perform a full volume copy. The resulting shadow volume relies on the
112 master volume for all unmodified data blocks, which are not copied
113 until requested. Create a dependent shadow when you do not require two
114 physical copies of the data. A dependent shadow volume can be either
115 the same size or smaller than the master volume. A smaller shadow vol‐
116 ume is called a Compact Dependent Shadow Volume, and is typically used
117 when the amount of change that occurs to a Point-in-Time Copy volume
118 set is small compared to the entire size of the master volume.
119 The following syntax allows you to create an exportable independent
122 shadow volume in a Sun Cluster environment:
123 # iiadm -ne ind master shadow bitmap
125 An issue arises when using a Compact Dependent Shadow Volume in that
130 its size is established at the time that the Point-in-Time Copy volume
131 set is enabled. If the amount of change to the entire volume set over
132 the duration of its usage exceeds the space allocated for the shadow
133 volume, the shadow volume is marked as out of space. It is possible to
134 read from the shadow volume even after it is out of space, until a por‐
135 tion of the data for which there was no room is requested. Once that
136 happens, the read fails and the shadow volume is marked offline.
137 To address this issue, Point-in-Time Copy supports the ability to asso‐
140 ciate an overflow volume to an existing Point-in-Time Copy dependent
141 volume set. Thus, if the size of the Compact Dependent Shadow Volume is
142 too small, or an unscheduled amount of change occurs to the volume set,
143 changed data can be redirected to the associated overflow volume. To
144 facilitate efficient usage of this overflow volume, it can be associ‐
145 ated with multiple Point-in-Time Copy volume sets on an as-needed
146 basis.
147 Considerations
149 Prior to invoking an Point-in-Time Copy enable, copy or update opera‐
150 tion, Point-in-Time Copy assures that the shadow volume is not mounted,
151 to prevent a file system panic from occurring. Also, it is suggested
152 that you either unmount or suspend (quiesce) all applications using the
153 master volume, for only the instant when the point-in-time snapshot is
154 taken. This assures that an atomically consistent point-in-time snap‐
155 shot is taken.
156 It is suggested that, if the master volume was suspended rather than
159 unmounted, the new point-in-time shadow volume's integrity be validated
160 using volume validation utilities, such as fsck(1M). The reason is that
161 Point-in-Time Copy has made a point-in-time copy of a mounted master
162 volume to an unmounted shadow volume. During the mounting of the shadow
163 volume, the file system detects that it is in the mounted state. Typi‐
164 cally this state occurs only when a system crashes, so the file system
165 attempts to validate the integrity of the volume assuming a system
166 failure occurred, not an Point-in-Time Copy.
167 ENVIRONMENT OPTIONS
169 The ii_bitmap variable in the /usr/kernel/drv/ii.conf configuration
170 file determines the bitmap volume operational semantics as follows:
171 0 Indicates that the bitmap is maintained in memory only or
173 resume operation.
174 1 Indicates that the bitmap is maintained in memory and on
177 disk. This is the default value.
178 If a system failure occurrs while using ii_bitmap=0, the shadow volume
182 might be inconsistent and fast resynchronization would not be possible.
183 If Point-in-Time Copy is used in conjunction with the Network Storage
186 component Remote Mirror or in a Sun Cluster, set ii_bitmap=1.
187 The ii_debug variable in the /usr/kernel/drv/ii.conf configuration file
190 determines the amount of information logging that is output to the sys‐
191 tem console /dev/console during Point-in-Time Copy processing.
192 0 Indicates that no logging is sent to the system console.
194 1 Indicates that informational logging is sent to the system
197 console.
198 2 Indicates that developmental logging is sent to the system
201 console.
202
205 The iiadm utility supports the following options.
206 -e{ind|dep} master_vol shadow_vol bitmap_vol
208 Enable Point-in-Time Copy for the specified master, shadow, and
210 bitmap volumes.
211 The enable shadow set processing assures that the specified volumes
213 are accessible, that the shadow_vol is not mounted, and that the
214 bitmap_vol is correctly sized for the type of shadow set being cre‐
215 ated. Additionally, it assures that the volumes are under control
216 of the SV driver ( if they are not, it puts them there), initial‐
217 izes the bitmap volume, and, if the volume set is an independent
218 shadow set, a full copy operation is initiated.
219 On a successful enable, Point-in-Time Copy stores the specified
221 master_vol, shadow_vol and bitmap_vol names, plus the enabling type
222 (ind or dep), into the Point-in-Time Copy configuration store. The
223 configuration store contains all currently configured Point-in-Time
224 Copy Volume Sets and their associated configuration attributes.
225 (See discussion above on independent and dependent shadow volume
226 semantics.)
227 master_vol is the volume from which a point-in-time snapshot is
229 made.
230 shadow_vol is the volume that contains the point-in-time snapshot.
232 bitmap_vol is used for tracking differences between the shadow and
234 master volumes. When Point-in-Time Copy shadow operations are sus‐
235 pended or resumed, the bitmap volume (maintained in kernel memory)
236 can be stored in or retrieved from permanent storage. The storage
237 associated with the bitmap volume should be as redundant as that of
238 the shadow volume storage.
239 The shadow_vol name is the name that the Point-in-Time Copy Shadow
241 Set is known by for all iiadm options requiring specification of a
242 volume_set name.
243 -d volume_set
246 Disable the Point-in-Time Copy volume set associated with the spec‐
248 ified volume_set.
249 If Point-in-Time Copy was running in independent mode as specified
251 in the -e ind options, above, the shadow volume data contains the
252 same data as it did before it was disabled (assuming no writes have
253 occurred). Users can access the master and shadow volumes, as they
254 are now standalone point-in-time copies.
255 During the time that the full copy is active, an independent volume
257 operates as though it is a dependent volume. To assure that the
258 volume is no longer in full copy mode, issue the following command
259 to wait for the full copy to complete:
260 # iiadm -w volume_set
262 [-p] -u s volume_set
267 Update the shadow volume from the master.
269 Updates a point-in-time copy of the master volume to the shadow
271 volume. volume_set is the Point-in-Time Copy shadow set containing
272 the master and shadow volumes. This option provides a fast resyn‐
273 chronization of the shadow volume, creating an incremental copy of
274 the master. This update copies all 32KB segments flagged as differ‐
275 ent between the master and shadow volumes. It does not copy all
276 master volume data, only changed data. While the data is being
277 copied, the shadow is dependent upon the master volume.
278 Before using this option, momentarily quiesce the workload to the
280 volumes; stop the host application from writing to the volumes.
281 This ensures that the point-in-time data is consistent. You can
282 visually check the status of this copy or update operation with
283 iiadm -i volume_set, or interactively (by means of a shell or
284 script) with iiadm -w volume_set, before using the target volume
285 for any other operations.
286 This command supports PID (Process IDentifier) locking, by using
288 the option -p, iiadm -p -u s. Enabling this option prevents other
289 processes from taking a new point-in-time snapshot, thus invalidat‐
290 ing prior point-in-time data.
291 [-p] [-n] -u m volume_set
294 Updates a point-in-time copy of the master volume from the shadow.
296 volume_set is the Point-in-Time Copy volume set containing the mas‐
297 ter and shadow. This option provides a fast resynchronization of
298 the master volume, creating an incremental copy of the shadow. This
299 update copies all 32KB segments flagged as different between the
300 master and shadow volumes. It does not copy all shadow volume data,
301 only changed data. While the data is being copied, the master is
302 dependent upon the shadow volume.
303 Before using this option, momentarily quiesce the workload to the
305 volumes; stop the host application from writing to the volumes.
306 This ensures that the point-in-time data is consistent. You can
307 visually check the status of this copy or update operation with
308 iiadm -i volume_set, or interactively (by means of a shell or
309 script) with iiadm -w volume_set, before using the target volume
310 for any other operations.
311 This command is query enabled to prevent accidentally overwriting
313 the data on a master volume. When this command option is used in
314 scripts, add the -n option to prevent the query from occurring.
315 This command supports PID (Process IDentifier) locking, by using
317 the option -p, iiadm -p -u m. Enabling this option prevents other
318 processes from taking a new point-in-time snapshot, thus invalidat‐
319 ing prior point-in-time data.
320 [-p] -c s volume_set
323 Copy the master volume to the shadow.
325 Creates a point-in-time copy of the master volume to the shadow
327 volume. volume_set is the Point-in-Time Copy volume set containing
328 the master and shadow. This option writes all data in the point-in-
329 time copy of the master volume to the shadow volume. While the data
330 is being copied from master to shadow, the shadow is dependent on
331 the master volume.
332 This option performs a full volume copy. Use iiadm -u s unless the
334 integrity of the data on the independent shadow volume is in doubt.
335 Otherwise, use this option to synchronize the master and shadow
336 volumes; that is, make the data on each volume match.
337 Before using this option, momentarily quiesce the workload to the
339 volumes; stop the host application from writing to the volumes.
340 This ensures that the point-in-time data is consistent. You can
341 visually check the status of this copy or update operation with
342 iiadm -i volume_set, or interactively (by means of a shell or
343 script) with iiadm -w volume_set, before using the target volume
344 for any other operations.
345 This command supports PID (Process IDentifier) locking, by using
347 the -p option, iiadm -p -c s. Enabling this option prevents other
348 processes from taking a new point-in-time snapshot, thus invalidat‐
349 ing prior point-in-time data.
350 -c m volume_set
353 Copy the shadow volume to the master.
355 Creates a point-in-time copy of the shadow volume to the master
357 volume. volume_set is the Point-in-Time Copy volume set containing
358 the master and shadow volumes. This option writes all data in the
359 point-in-time copy of the shadow volume to the master volume. While
360 the data is being copied from the shadow to the master, the master
361 is dependent upon the shadow volume.
362 This option performs a full volume copy. Use iiadm -u m unless the
364 integrity of the data on the independent master is in doubt. Other‐
365 wise, use this option to synchronize the master and shadow volumes;
366 that is, make the data on each volume match.
367 Before using this option, momentarily quiesce the workload to the
369 volumes; stop the host application from writing to the volumes.
370 This ensures that the point-in-time data is consistent. You can
371 visually check the status of this copy or update operation with
372 iiadm -i volume_set, or interactively (by means of a shell or
373 script) with iiadm -w volume_set, before using the target volume
374 for any other operations.
375 This command is query-enabled to prevent accidentally overwriting
377 the data on a master volume. When this command option is used in
378 scripts, add the -n option to prevent the query from occurring.
379 This command supports PID (Process IDentifier) locking, by using
381 the -p option, iiadm -p -c m. Enabling this option prevents other
382 processes from taking a new point-in-time snapshot, thus invalidat‐
383 ing prior point-in-time data.
384 -a volume_set
387 Abort any current copy operation that might be active between the
389 master and shadow volumes. volume_set is the Point-in-Time Copy
390 volume set containing the master and shadow volumes. After execut‐
391 ing iiadm -a, the update or copy to the target (master or shadow)
392 volume is incomplete. The target volume is now a dependent copy of
393 the source volume. Reissue the update or copy command option to
394 resynchronize the volumes.
395 [-p] [-n] -w volume_set
398 Wait until any in-progress copy or update operation completes or is
400 aborted. volume_set is the Point-in-Time Copy volume set containing
401 the master and shadow volumes.
402 This option waits until the current Point-in-Time Copy operation is
404 complete, thus preventing a subsequent iiadm command (from a shell
405 or script) from executing. Use this command option when you need to
406 be sure the copy or update operation has completed.
407 This command supports PID (Process IDentifier) unlocking. If a
409 prior copy or update, using a command iiadm -p {-c|-u} {m|s}, was
410 invoked with the -p option, upon completion of the wait processing,
411 if the current PID was the PID that locked the point-in-time data,
412 this option unlocks the data.
413 -i volume_set
416 Display status for the Point-in-Time Copy currently-enabled or
418 -suspended volume set. volume_set is the Point-in-Time Copy volume
419 set containing the master and shadow volumes. If no volume_set is
420 specified, status is displayed for all Point-in-Time Copy volume
421 sets that are configured.
422 -l
425 List all currently configured Point-in-Time Copy volumes.
427 -O overflow_vol
430 This option causes Point-in-Time Copy to initialize the specified
432 overflow_vol for subsequent use as an overflow volume in conjunc‐
433 tion with Compact Dependent Shadow Volumes. To facilitate effi‐
434 cient, shared usage of this overflow volume, it can be associated
435 with multiple Point-in-Time Copy volume sets on an as-needed basis.
436 During initialization of the overflow_vol, the initiator of this
438 option, must answer the following question: "Initialize this over‐
439 flow volume? yes/no" A response of either "yes/no" is required
440 before proceeding.
441 This option supports the -n option, so that the requested action is
443 performed without prompting. This option is useful for inclusion in
444 a script. The -n option must be specified first. For example,
445 "iiadm -nO vol" is valid; "iiadm -On vol" is not.
446 Make sure you want to initialize the data on the specified over‐
448 flow_vol, especially when using the -n option.
449 -A overflow_vol volume_set
452 This option enables the specified overflow_vol, for subsequent use
454 as an overflow volume in a situation where the size of the Compact
455 Dependent Shadow Volume is too small, or an unscheduled amount of
456 change occurs to the volume set. Overflow changed data would be
457 redirected to the associated overflow volume. volume_set is the
458 Point-in-Time Copy volume set containing the master and shadow vol‐
459 umes.
460 If the overflow_vol has not been initialized, this option initial‐
462 izes the overflow_vol (see -O option), then attaches the over‐
463 flow_vol to the volume_set.
464 If overflow_vol was previously initialized, this option attaches
466 the overflow_vol to the volume_set.
467 This option supports the -n option, so that the requested action is
469 performed without prompting. This option is useful for inclusion in
470 a script. The -n option must be specified first. For example,
471 "iiadm -nA vol" is valid; "iiadm -An vol" is not.
472 Make sure you want to initialize the data on the specified over‐
474 flow_vol, especially when using the -n option.
475 -D volume_set
478 This option removes the overflow volume currently associated with
480 the specified volume_set. If the overflow volume is currently in
481 use by the volume_set, this operation fails with an "Overflow vol‐
482 ume still in use" error message. To resolve this situation, perform
483 one of the operations described below on the volume_set. These
484 operations momentarily clear out all overflow writes that are asso‐
485 ciated with this volume set.
486 abort(-a)
488 Abort copy operation.
490 disable(-d)
493 Dissolve the volume set.
495 update(-u)
498 Update the volume set.
500 -L
504 This option lists all overflow volumes which are associated with
506 one or more volume sets.
507 -Q overflow_vol
510 This option displays the current status of the overflow_vol.
512 -E volume_set
515 Export the independent shadow volume of the Point-in-Time Copy vol‐
517 ume set specified by volume_set. The shadow volume is to be made
518 available to another host for read/write access, by means of an
519 enabling technology, such as multi-ported devices. This other host
520 is responsible for maintaining a bitmap of differences that is used
521 to merge with locally recorded differences to the master when the
522 shadow volume is rejoined to its master volume. While a shadow vol‐
523 ume is exported it must not be subject to an update or copy opera‐
524 tion. Perform an iiadm -w volume_set command prior to invoking an
525 export command.
526 -I volume_set bitmap_vol
529 Import the independent shadow volume of the Point-in-Time Copy vol‐
531 ume set specified by volume_set. The shadow volume must have been
532 previously exported from a host by means of an enabling technology,
533 such as multi-ported devices. The import operation causes this host
534 to start maintaining a bitmap of differences as the volume is modi‐
535 fied. The bitmap_vol should not be the same as that used when the
536 shadow volume was originally formed into a shadow group.
537 After the exported/imported independent shadow volume is no longer
539 needed by the other node, you must enter a disable command so that
540 the bitmap_vol and its associated shadow_vol are consistent, prior
541 to performing a join operation. For example,
542 # iiadm -d volume_set
544 -J volume_set bitmap_vol
549 Join the volume_set, using the bitmap_vol, with the master volume
551 set of the Point-in-Time Copy volume set. The bitmap volume sup‐
552 plied is read and merged with the original volume to reconstruct
553 the original volume set consisting of the master, shadow, and bit‐
554 map volumes. The bitmap_vol to be merged is the one obtained on the
555 node that had imported the independent shadow volume. There must be
556 no write activity to the shadow volume on the importing machine
557 from the time the bitmap is copied over until the shadow is once
558 again imported.
559 -g group_name -m volume_set [volume_set2 ...]
562 Add one or more existing Point-in-Time Copy volume_set(s) into a
564 user specified group_name. This association of one or more Point-
565 in-Time Copy volume sets in a group allows the list of iiadm
566 options shown below to be performed on all volume sets within the
567 group_name as a whole.
568 Only the commands COPY (-c) and UPDATE (-u) are performed atomi‐
570 cally across all Point-in-Time Copy sets within the group. All
571 other grouped, iiadm commands are performed sequentially on each
572 member of the group.
573 The syntax of an iiadm group command is as follows:
575 iiadm -g group_name [options]
577 The options are as follows:
580 -a
582 Abort copy operation on all sets within group_name.
584 -A
587 Attach overflow_vol to all sets within group_name.
589 -c {s | m}
592 Copy shadow/master for all sets within group_name.
594 -D
597 Detach overflow_vol from all sets within group_name.
599 -d
602 Disable all sets within group_name.
604 -E
607 Export all volume sets within group_name.
609 -i
612 Status of all volume sets within group_name.
614 -l
617 List all volume sets within group_name.
619 -L
622 List all groups.
624 -n
627 Do not ask if an update of the master volume is what the user
629 really intended.
630 -P
633 Set parameters on all volume sets within group_name.
635 -R
638 Reset all volume sets within group_name.
640 -u {s | m}
643 Update shadow/master for all sets within group_name.
645 -w
648 Wait for all volume sets within group_name.
650 -g -" " -m volume_set [volume_set2 ...]
654 Remove one or more existing Point-in-Time Copy volume_set(s) from
656 their currently associated group_name. By default, or until moved
657 into a user specified group_name, all Point-in-Time Copy vol‐
658 ume_set(s) are in the blank (" ") group. This association allows
659 all the previously documented iiadm group commands to be performed
660 against the blank (" ") iiadm group_name.
661 -C cluster_tag
664 This Point-in-Time Copy option is a modifier that limits configura‐
666 tion operations to only those volumes belonging to a Sun Cluster
667 Resource Group, or Disk Group.
668 In a Sun Cluster where the volume manager is Sun Cluster-aware,
670 iiadm automatically obtains the correct Disk Group information,
671 therefore this option is typically not required unless the volumes
672 are part of an encompassing Resource Group.
673 In a Sun Cluster where the volumes are accessible on the local node
675 only, the special cluster_tag of local is used to indicate volumes
676 that are not part of a Sun Cluster Resource Group or Disk Group.
677 If "-L" is given as a the cluster_tag argument, then iiadm lists
679 all cluster tags associated with Point-in-Time Copy.
680 This option is invalid when used on a Solaris system on which the
682 Sun Cluster package has not been installed or configured.
683 -h
686 Prints the iiadm usage summary.
688 -v
691 Display the current version of the Point-in-Time Copy software com‐
693 ponents.
694 Contact Sun Enterprise Services for assistance in using the remaining
698 commands in this section.
699 -P delay unit volume_set
701 Alter the Point-in-Time Copy volume set tuning parameters for the
703 specified volume_set to delay ticks, every unit I/O's. Delay ranges
704 from 2 to 10000 inclusive; unit ranges from 100 to 60000 inclusive.
705 -R volume
708 After a volume has failed, Point-in-Time Copy places it offline.
710 After replacing the volume, place it back online using this option.
711 Associated dependent volumes in the Point-in-Time Copy volume set
712 are also placed online. After the volume is placed online, this
713 command also starts any necessary point-in-time volume updates.
714
717 0 Command completed successfully.
718 >0 An error occurred.
721
724 See attributes(5) for descriptions of the following attributes:
725 ┌─────────────────────────────┬─────────────────────────────┐
730 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
731 ├─────────────────────────────┼─────────────────────────────┤
732 │Availability │SUNWiir, SUNWiiu │
733 ├─────────────────────────────┼─────────────────────────────┤
734 │Interface Stability │Evolving │
735 └─────────────────────────────┴─────────────────────────────┘
736
738 dscfg(1M), svadm(1M), ds.log(4), rdc.cf(4), attributes(5), ii(7D),
739 sv(7D)
740SunOS 5.11 2 Oct 2007 iiadm(1M)