Viewing The Event Log; Removing The Event Log; Stopped Logical Disks And Missing Physical Disks; Preserved Data - HP 3PAR StoreServ 7200 2-node Administrator's Manual

Viewing the Event Log

To view the events log, issue the showeventlog command.
The eventlog display can be refined to include only events occurring before or after a specified
time, within a specified time period, or that match a specified pattern. For complete information
on the events log display options, see the HP 3PAR Command Line Interface Reference.

Removing the Event Log

To remove all event logs with severity Debug from the system, issue the removeeventlog
command.
The removeeventlog command removes all event logs with severity Debug from the system.

Stopped Logical Disks and Missing Physical Disks

If physical disks in the system are unavailable when the system is powered on, the physical disk
is in the Missing state. The system manager will not immediately start LDs that have chunklets on
these missing disks. The result is some LDs remain in the Stopped state. Use the showpd and
showld commands to display the state of physical and LDs.
If the LD is data-complete, but a few of the physical disks are missing, the LDs will be automatically
started after waiting five minutes. If more than four physical disks are missing, the LDs will not be
started automatically. You can start a data-complete LD using the InForm OS CLI startld command,
and the system manager will begin reconstructing the missing mirrored data. The system
automatically relocates the chunklets from the missing physical disks to free space or spare space.
For a complete list of options available for the showpd and showld commands, see the HP 3PAR
Command Line Interface Reference and the HP 3PAR CLI Help.

Preserved Data

When the system is holding data in cache but is not able to write that data to the destination disk
for any reason, it saves the data to the preserved data LD. This LD is automatically created at the
time that the storage system is installed and initially configured.
The data written to the preserved data LDs is typically created due to a temporary loss of availability
of disks, a situation that usually corrects itself once the disks become available again. When the
destination LDs become available again, the system automatically plays back the preserved data
by writing it from the preserved data LDs to the destination LDs.
If you notice that the preserved data LD has data saved for a long time, use the showpd command
to see which physical disks are in an unavailable state. If any disks are in an unavailable state, it
is necessary to take corrective action in order to make those disks available again. If data is
persistently saved to the preserved data LD, contact your local service provider for technical support
and services.
120 Managing Events and Alerts