VERITAS Storage Foundation 4.1 Intelligent Storage Provisioning Administrator's Guide

Segregating Database Components
190 VERITAS Storage Foundation ISP Administrator’s Guide
Note You do not need to run the vxsnap prepare command. Volumes created in a clone
pool are automatically allocated a data change object (DCO).
3. Using the newly created volumes, take full-sized instant snapshots of the corresponding five
volumes in the data pool:
# vxsnap -g hrdg make src=vol1/snap=snapvol1/sync=yes \
src=vol2/snap=snapvol2/sync=yes \
src=vol3/snap=snapvol3/sync=yes \
src=vol4/snap=snapvol4/sync=yes \
src=vol5/snap=snapvol5/sync=yes
4. After synchronization of the data in the snapshot volumes is complete, split off a new disk
group, snapdg, from the hrdg disk group:
# vxdg split hrdg snapdg snappool1
The snapdg disk group contains the snapshot volumes from the snappool1 clone pool.
5. Deport the newly created disk group, snapdg:
# vxdg deport snapdg
This disk group can now be imported on a different host.
Segregating Database Components
To achieve best performance, it is usual to place the components of a database, such as the redo log,
table spaces and indexes, on different disks. Using ISP, this can be accomplished by using the
Annotation Service feature, which allows you to define new characteristics and then assign these to
your disks.
Note The Annotation Service is accessed by selecting a disk in the VERITAS Enterprise
Administrator, and then selecting Actions > Annotate Disks. This feature is not available
from the command line.
The Annotation Service can be used in conjunction with volume rules to reserve disks for particular
volumes. By tagging disks with a suitable attribute name and value such as reserved_for and
redo_log, you can use a confineto rule to ensure that the volume for a redo log is only
allocated space from those disks:
confineto "reserved_for"="redo_log"
Conversely when creating volumes that are not to be used for the redo logs, you can specify an
exclude rule:
exclude "reserved_for"="redo_log"