Logical Volume Number of Copies | HP HA s Software guide

Monitoring Disk Resources

Disk Monitor Reference

Logical Volume Number of Copies

The logical volume number of copies is most useful to monitor in a mirrored disk conﬁguration. It tells you how many copies of the data are available.

MirrorDisk/UX supports up to 3-way mirroring, so there can be from 0 to 3 copies (see Table 2-5.) In a RAID conﬁguration that is not mirrored using LVM, the only possible number is 0 or 1; either the data is accessible or it isn’t.

Note that when you conﬁgure mirroring in LVM, it lists 0 mirrors to mean you have one copy of the data. Likewise, 2 mirrors mean you have 3 copies of the data (one original plus 2 mirrors). The disk monitor is monitoring all copies of data, and therefore counts the “original” as part of the total number of copies.

Table 2-5		Interpreting Logical Volume Copies

		Resource Name	vg/vgName/lv/copies/lvName

		Condition	Interpretation

		0	No copies, either physical parts of the disk array have problems,
			the lv is inactive, or a physical extent is stale or unavailable.

		1	One complete copy of data available; if the data is not mirrored,
			then all physical extents are ﬁne, if data is mirrored, all other
			copies have problems.

		2	Two complete copies of data are available; if the data is two-way
			mirrored, then all physical disks are up and data is available, if
			3-way mirrored, at least one logical extent has a missing or stale
			physical extent .

		3	All copies of a 3-way mirror are available.

When conﬁguring requests from the SAM interface, a wildcard (*) may be used in place of lvName to request status for all logical volumes in a volume group.

If you split off mirrors from your mirrored conﬁguration, you will see the number of copies reduced by 1 when the split mirror is created.

Chapter 2

39

Image 39

HP HA s Software manual Logical Volume Number of Copies, Interpreting Logical Volume Copies

Contents

B5735-90001 August Using EMS HA Monitors Legal Notices Contents Monitoring Network Interfaces Monitoring Cluster Resources Troubleshooting Monitoring System ResourcesGlossary Contents Printing History Printing Date Part Number EditionB5735-90001 Page Publications PrefacePage Installing and Using EMS What are EMS HA Monitors? Event Monitoring Services High Availability Monitors Chapter Role of EMS HA Monitors in a High Availability Environment Installing EMS HA Monitors Installing and Removing EMS HA Monitors Removing EMS HA Monitors Pvpvlink Using EMS HA MonitorsEvent Monitoring Service Resource Class Hierarchy Status AvailMB Event Monitoring Service Screen Screen Selecting a Resource to Monitor Using Wildcards Monitoring Request Parameters Creating a Monitoring Request How Do I Tell EMS When to Send Events? Which Protocols Can I Use to Send Events? What is a Polling Interval? What is a Notiﬁcation Comment? Copying Monitoring Requests Modifying Monitoring RequestsRemoving Monitoring Requests Service EMS Conﬁguring MC/ServiceGuard Package Dependencies Package Conﬁguration Screen Package Resource Dependencies Screen Resource Parameters Screen Using EMS HA Monitors Monitoring Disk Resources Monitoring Disk Resources Disk Monitor Resource Class Hierarchy Disk Monitor Reference Interpreting Physical Volume Summary Physical Volume Summary Disk Monitor Reference Interpreting Physical Volume and Physical Volume Link Status Physical Volume and Physical Volume Link Status Interpreting Logical Volume Summary Logical Volume Summary Logical volume is DOWN, a complete copy of the data is not Logical Volume StatusInterpreting Logical Volume Status Logical volume is inactive Interpreting Logical Volume Copies Logical Volume Number of Copies Rules for Using the EMS Disk Monitor with MC/ServiceGuard Rules for Using the EMS Disk Monitor with MC/ServiceGuard Pvsummary Calculations Case Conclusion State Rules for RAID Arrays Adding PVGs to Existing Volume Groups Creating Volume Groups on Disk Arrays Using PV Links # mkdir /dev/vgdatabase Creating Logical Volumes Rules for Mirrored Individual Disks Creating Disk Monitoring Requests Disk Monitoring Request Suggestions Parameters When Disks Fail RAID Array Example Resources to Monitor for RAID Arrays Pvgup Return Mirrored Disks Example Resources to Monitor for Mirrored Disks Monitoring Parameters Resource Notify Condition Option Resource Monitoring Parameters Notify Condition Option Resources to Monitor for Lock DisksExample for Interpreting the pvsummary for Mirrored Disks Number Pvsummary Valid Meaning Value Devices Resources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Monitor Reference Cluster Monitor Resource Class HierarchyCluster Interpreting Custer Status Cluster Status Interpreting Node Status Node Status Interpreting Package Status Package Status Creating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Reference Network Monitor Resource Class HierarchyInterpreting LAN Interface Status Chapter Hour Net/interfaces/lan/status/LANname When value isConﬁguring Network Monitoring Requests 30 sec Monitoring System Resources System Resource Monitor Class Hierarchy System Monitor Reference Number of Users Interpreting Number of UsersResource Name Value Range Interpretation Job Queues Interpreting Job QueuesResource Name Value Interpretation Range Filesystem Available Space Filesystem Available SpaceResource Name Creating System Resource Monitoring Requests 6Troubleshooting EMS Directories and Files Etc/opt/resmon/log EMS Logging Logging and tracing EMS Tracing System Performance Issues Network Performance IssuesPerformance Considerations Testing Network Monitor Requests Testing Monitor RequestsTesting Disk Monitor Requests Testing Cluster Monitor Requests Making Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index