1ii(7D)                              Devices                             ii(7D)
2
3
4

NAME

6       ii - Instant Image control device
7

DESCRIPTION

9       The ii device is a control interface for Instant Image devices and con‐
10       trols the Instant Image module through the ioctl(2) interface.
11
12
13       Instant Image is a point-in-time volume copy facility for  the  Solaris
14       operating  environment  that is administered through the iiadm(1M) com‐
15       mand. With Instant Image, you can create an  independent  point-in-time
16       copy  of a volume or a master volume-dependent point-in-time view.  You
17       can also independently access the master and shadow volume for read and
18       write  operations. Instant Image also lets you update the shadow volume
19       from the master volume or restore the master volume  from  the  shadow.
20       (Restore  operations  to  volumes  can be full or incremental). Instant
21       Image supports fast volume re-synchronization, letting you create a new
22       point-in-time  volume  copy  by updating the specified volume with only
23       changed data.
24
25
26       To create a shadow volume you need a:
27
28           1.     Master volume to be shadowed.
29
30           2.     Shadow volume where the copy will reside. This  volume  must
31                  be equal to or larger than the master volume.
32
33           3.     Administrative  bitmap  volume  or file for tracking differ‐
34                  ences between the shadow and master volumes. The administra‐
35                  tive bitmap volume or file must be at least 24Kbytes in size
36                  and requires 8KBytes for each GByte  (or  part  thereof)  of
37                  master volume size, plus an additional 8KBytes overhead. For
38                  example, to shadow a 3GByte master volume,  the  administra‐
39                  tion  volume  must  be  8KBytes + (3 * 8KBytes) =32KBytes in
40                  size.
41
42
43       The Instant Image module uses services provided by the SDBC and  SD_GEN
44       modules.  The  SV  module  is  required to present a conventional block
45       device interface to the storage product interface of the Instant Image,
46       SDBC and SD_GEN modules.
47
48
49       When  a  shadow  operation  is suspended or resumed, the administration
50       volumes may be stored in permanent SDBC storage or loaded and saved  to
51       and   from   kernel   memory.  The  ii_bitmap  variable  in  the  /ker‐
52       nel/drv/ii.conf configuration file determines the administration volume
53       storage  type. A value of 0 indicates kernel memory, while a value of 1
54       indicates permanent SDBC storage.  If the system is part of  a  storage
55       products  cluster,  use  the 1 value (permanent storage), otherwise use
56       kernel memory (0 value).
57

FILES

59       kernel/drv/ii          32- bit ELF kernel module (x86).
60
61
62       /kernel/drv/ii.conf    Configuration file.
63
64

ATTRIBUTES

66       See attributes(5) for a description of the following attributes:
67
68
69
70
71       ┌─────────────────────────────┬─────────────────────────────┐
72       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
73       ├─────────────────────────────┼─────────────────────────────┤
74       │Architecture                 │x86                          │
75       ├─────────────────────────────┼─────────────────────────────┤
76       │Availability                 │SUNWiu                       │
77       ├─────────────────────────────┼─────────────────────────────┤
78       │Interface Stability          │Committed                    │
79       └─────────────────────────────┴─────────────────────────────┘
80

SEE ALSO

82       iiadm(1M), ioctl(2), attributes(5), sv(7D)
83
84
85
86SunOS 5.11                        8 Jun 2007                            ii(7D)
Impressum