CA SRM collects information about the following virtual storage environment objects:
Objects representing the applications of your storage virtualization. For example, SMI-S provider of your storage virtualization server.
Objects representing the clusters of your storage virtualization. The nodes are clustered together for single point of control for administrator. A cluster can have one to four node pairs in it. Each pair of nodes is known as an input/output (I/O) group. Each node must be in only one I/O group.
Objects representing the ports of your storage environment. Fibre-channel ports are identified by their physical port number and by a worldwide port name (WWPN).
Objects representing the nodes of a cluster of your storage virtualization. A node is a single processing unit within a VSS cluster. Each pair of nodes is known as an input/output (I/O) group. Each node must be in only one I/O group.
Objects representing the managed disks of your storage virtualization. A managed disk (MDisk) is a logical disk (typically a RAID or partition) that a storage subsystem exports to the SAN fabric to which the nodes in the cluster are attached.
An MDisk consist of multiple physical disks that are presented as a single logical disk to the SAN. An MDisk always provides usable blocks of physical storage to the cluster even if it does not have a one-to-one correspondence with a physical disk.
Objects representing group of the managed disks of your storage virturalization. An MDisk Group is a collection of MDisks that jointly contain all the data for a specified set of virtual disks (VDisks). All MDisks in a group are split into extents of the same size.
You can add MDisks to an MDisk group at any time either to increase the number of extents that are available for new VDisks or to expand existing VDisks.
Objects representing virtual disk of your storage environment. A virtual disk (VDisk) is a logical disk that the cluster presents to the SAN.
Application servers on the SAN access VDisks. VDisks are created from a set of extents in an MDisk group. There are three types of VDisks:
Objects representing copies of your VDisks in your storage virtualization. Flash Copies allows you to make an instant, point-in-time copy from a source VDisk to a target VDisk.
Objects representing the mirror of your VDisks in your storage virtualization. The Metro Mirrors and Global Mirror Copy Services represents the relationship between two volumes, so that updates that are made by an application to one volume are mirrored on the other volume. The volumes can be in the same system or on two different systems.
Metro Mirrors provides a consistent copy of a source VDisk on a target VDisk. Data is written to the target VDisk synchronously after it is written to the source VDisk, so the copy is continuously updated.
With Global Mirror copying, a consistent copy of a source volume on a target volume. Data is written to the target volume asynchronously, so that the copy is continuously updated, but the copy might not contain the last few updates in the event that a disaster recovery operation is performed.
Objects representing all the internal storage disks of your storage virtualization. These drives are used to create a Redundant Array of Independent Disks (RAID), which are presented as managed disks (MDisks) in the system. You can open the Internal Disks detail form by clicking the Display Detailed Line button on the toolbar of this table. The form displays information about the selected internal disks.
Objects representing performance. CA SRM reports detailed information about performance attributes of storage objects and the data collection.
Objects representing a single VDisk copy. Each VDisk must have at least one copy and can have a maximum of two copies after it is mirrored.
Host mapping is the process of controlling which hosts have access to specific volumes within the system. Each host mapping associates a volume with a host object and provides a way for all WWPNs and iSCSI names in the host object to access the volume. You can map a volume to multiple host objects. Objects representing the volume name, host name, LUN number, and protocol (iSCSI or FC).
|
Copyright © 2016 CA Technologies.
All rights reserved.
|
|