Udayan,
>> Have installed AVS-i386-20070202 and were going through the
>> released pdf notes on
>> the availability suite ref: http://www.sun.com/hwdocs and have reached
>> Initial
>> Configuration Procedures but now are unable to use bitmap volumes as given
>> in your notes
>> i.e.-
>> To obtain the size of a Point-in-Time Copy bitmap, use this command:
>> dsbitmap -p data-volume [bitmap-volume]
>>
>> we don’t know the data-volume and bitmap volume in our system and
>> want the
>> procedure to create and use data and bitmap volumes.
The "data-volume", is the source volume of the Point-in-time copy.
The "bitmap-volume" is an optional argument to the dsbitmap utility, and can be
ignored.
Therefore if your "data-volume" is dev/rdsk/c4t3d7s0, this is the typical
output from dsbitmap:
# dsbitmap -p /dev/rdsk/c4t3d7s0
Point in Time bitmap sizing
Data volume (/dev/rdsk/c4t3d7s0) size: 285196221 blocks
Required bitmap volume size:
Independent shadow: 2222 blocks
Full size dependent shadow: 2222 blocks
Compact dependent shadow: 37518 blocks
What this output means, is that if your Point-in-time copy data-volume is
285196221 blocks, and you want either an independent or (full size) dependent
shadow, you will need to provision two volumes:
1) A volume 2222 blocks in size needs to be provisioned for the bitmap volume,
for example /dev/rdsk/c4t3d6s1
2). A volume 285196221 blocks in size needs to be provisioned for the shadow
volume, for example /dev/rdsk/c4t3d6s0
Now the independent (or dependent) shadow set can be enabled:
iiadm -e ind /dev/rdsk/c4t3d7s0 /dev/rdsk/c4t3d6s0 /dev/rdsk/c4t3d6s
If you wanted a compact dependent shadow volume, at step 1 above, you would
have had to providion a 37518 block volume, then
iiadm -e dep /dev/rdsk/c4t3d7s0 /dev/rdsk/c4t3d6s0 /dev/rdsk/c4t3d6s
Of course this is an example, and the master, shadow and bitmap volumes could
be any Solaris block device, on any storage.
Any help would be great
Tia,
Udayan
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Jim Dunham
Solaris, Storage Software Group
Sun Microsystems, Inc.
1617 Southwood Drive
Nashua, NH 03063
Email: [EMAIL PROTECTED]
http://blogs.sun.com/avs
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
