Container Guidelines - HP 418800-B21 - StorageWorks Modular Smart Array 70 Storage Enclosure User Manual

Hp storageworks replication solutions manager 4.0.1 user guide (t3680-96308, june 2008)
Hide thumbs Also See for 418800-B21 - StorageWorks Modular Smart Array 70 Storage Enclosure:
Table of Contents

Advertisement

Cannot store data
Implementation of container features is controller software dependent. See
controller software features - local
Containers for preallocated replication
Preallocated replication refers to a snapclone or snapshot that is created by copying data from a source
virtual disk to a container and immediately converting the container into a virtual disk. Compared to
standard snapclones and snapshots, the preallocated methods are faster. In cases where host I/O must
be suspended, the improved speed of preallocated replication reduces the time that a host application is
suspended.
Container planning
A container must be the same size as the virtual disk that you want to copy. For example, if you have
virtual disks of 10, 20, and 30 GB to copy, you should create containers of 10, 20, and 30 GB. A
container of 25 GB would not be usable with any of those disks.
When used for mirrorclones and preallocated snapclones, the container may be in a different disk group
than the source virtual disk. When used for preallocated snapshots, the container must be in the same
disk group as the source virtual disk.
Conversion of virtual disks to containers
A snapclone virtual disk can be converted to a container. This is useful when you repeatedly
create a snapclone of the same virtual disk. For example, when making daily backups
of a virtual disk. See the following job commands: ConvertStorageVolumeIntoContainer,
ConvertStorageVolumesIntoContainers,
ConvertStorageVolumesIntoContainersUsingRepository.
The following virtual disks cannot be converted into containers:
Virtual disks that are presented to hosts
Snapshots

Container guidelines

The following guidelines apply to containers:
The array must have a local replication license.
When used for mirrorclones and preallocated snapclones, the container may be in a different
disk group than the source virtual disk. When used for preallocated snapshots, the container must
be in the same disk group as the source virtual disk.
A container must be the same size as the source of the preallocated snapclone or snapshot.
The redundancy (Vraid) level of the container determines the Vraid level of a preallocated
snapclone. See
For a preallocated snapshot, the redundancy (Vraid) level of the container must be the same or
lower than the source. If the source has other snapshots, the Vraid level of the container must
be the same as the other snapshots.
Containers cannot be presented to hosts.
A snapclone virtual disk can be converted to a container. See
the following job commands: ConvertStorageVolumeIntoContainer,
ConvertStorageVolumesIntoContainers,
and ConvertStorageVolumesIntoContainersUsingRepository.
Virtual disks cannot be converted to containers if the disk is:
A snapshot
Presented to a host
replication.
ConvertStorageVolumesInManagedSetIntoContainers
redundancy level
(Vraid).
ConvertStorageVolumesInManagedSetIntoContainers
HP StorageWorks Replication Solutions Manager 4.0.1
and
431

Advertisement

Table of Contents
loading

Table of Contents