About the Overview page

To ensure the continuous availability of the HCP repository:

•A strict majority of the HCP storage nodes must be running and healthy. For example, a six-node system requires at least four running nodes.

If this condition is not true, namespaces cannot accept write requests, including requests to store new data or change object metadata.

•At any given time, the unused HCP storage space must be sufficient to allow the creation of new objects and to ensure proper behavior in the event that a node fails.

The top section of the Overview page serves as an early warning system for violations of these requirements. It also reports system configuration issues and provides other system status information, such as notification that the system is rebalancing metadata. When the system is functioning normally, this section indicates that no problems exist.

The information in this section is represented by icons that are associated with text. These are called alerts. To see the text that accompanies an alert icon, hover over the icon. The text appears below the icon.

This section contains three categories of alerts:

•Hardware Status — Alerts in this category identify nodes that are reporting problems relating to drives, network interface cards (NICs), HCP S Series Node tiering, and other internal components.

For more information about the types of problems reported, see Hardware status.

•System Status — Alerts in this category report on storage usage and indicate systemwide conditions such as a high rate of page swapping.

Note: When the amount of primary storage that’s used reaches 90 percent of primary storage capacity, HCP will not store any new objects or any new or replacement custom metadata or ACLs. HCP will, however, continue to allow changes to system metadata. In a SAIN system with primary spindown storage, the 90 percent capacity limit applies to primary running storage usage only.

Tip: If the amount of primary storage that’s used is approaching 75 percent of primary storage capacity, consider adding more storage capacity to HCP. By adding capacity before the 75 percent threshold is reached, you can prevent interruptions in namespace availability due to insufficient space. In a SAIN system with primary spindown storage, this tip applies to primary running storage usage only.

•Object Integrity — Alerts in this category report on the state of object data and metadata. They also identify situations in which the protection or Content Verification service is fixing errors or has found errors it cannot fix.

The background color in an alert icon indicates the status of the relevant component:

•A green background indicates that the component is within normal operating parameters.

•An orange background indicates that the component is disabled or needs attention in some way. The text that accompanies icons with an orange background appears automatically below the icon area. This text may contain links to Console pages that you can use to view more information about the problem and, in some cases, change one or more specific configuration settings in order to resolve the problem. For example, the text may contain a network name that’s a link to the page on which you can view and change the IP configuration settings for that network.

•A red background indicates that the component is malfunctioning. The text that accompanies icons with a red background appears automatically below the icon area. This text may contain links to more information about the problem and, in some cases, change one or more specific configuration settings in order to resolve the problem. For example, the text may contain a node number that’s a link to more detailed information about a problem with the hardware on that node.

For more information about the alerts that can appear on the Overview page, see Overview page alerts.

Note:  If the entire HCP system is read-only due to metadata unavailability, a message about the situation appears at the top of every System Management Console page. While the system is read-only, configuration changes and changes to namespace content are not allowed. Additionally, in this situation, statistics that describe repository content may be inaccurate. If the message says that the system has limited functionality and the situation persists, contact your HCP support center for help.

The Services section on the Overview page displays the status of each HCP service except Shredding, Migration, Fast Object Recovery, Replication, and Replication Verification. The information in this section is rolled up from all the HCP storage nodes. For example, if the Content Verification service is running on at least one storage node, the status of the service is running, regardless of whether it’s running on any other nodes.

For each service, the Services section shows:

•Service — The name of the service.

•Status — The current status of the service. Possible values are:

oRunning — The service is currently running.

oCompleted — The service stopped running because it completed all of its work before the end of its scheduled run time period.

oStopped — The service stopped running at the end of its scheduled run time period.

oStopping — The service is in the process of transitioning from Running to Completed or Stopped.

oWaiting — The service has never run.

oFixing — The service is fixing violations that it has detected.

oIrreparable — The service failed to fix violations. This is a severe condition and should be evaluated immediately.

oDisabled — The service cannot run because it has been manually disabled (for example, during problem resolution) or because another service that has precedence is currently running.

If unforeseen or user-initiated events violate a service setting at the object, node, or system level, the status of the service changes as HCP detects the violation and attempts to correct it.

•Time — The time of the most recent change to the service status, shown for the time zone that’s used for the HCP system time. The service was enforced until the specified time. For example, if the Protection service finishes at 10:00 PM on March 9, 2011 and the status of the service is Completed, the Time column displays:

10:00 PM 03/09/2011

The only exception to this is while a service is waiting for its first run. During this time, the Time column shows the current time.

For more information about services, see HCP services.

The Major Events section on the Overview page lists log messages, reasons for the message, and suggested actions about major events that have occurred since the HCP system was installed (for example, the addition or failure of a node). The list of messages in this section is a subset of the messages in the HCP system log. You can view all the messages in the system log in the All Events panel on the System Events page. For more information about this panel, see Viewing the complete event log.

By default, the messages in the Major Events section are listed ten at a time in reverse chronological order. For information about managing the message display, see Managing the message list.

For a description of the information provided by each log message, see Understanding the HCP system log. For information about the messages that can appear in the system log and how to respond to them, see HCP system log messages.

The System section on the Overview page contains two graphs: Objects and Ingested Volume.

Objects graph

The Objects graph shows the total number of objects that were stored in the repository during the past 30 days (or since HCP was installed if that was less than 30 days ago). This is the total number of objects stored in all namespaces.

Each version of an object counts as a separate object. However, the object count does not include object versions that are delete markers.

Each multipart object counts as a single object. Objects that are in the process of being created by multipart uploads are not included in the object count.

While either of the two search facilities is selected for use with the Search Console, the Objects graph also shows the total number of indexed objects in the repository during the past 30 days. For any point in time for which the indexed object count is shown, the count reflects the index maintained by the search facility that was selected for the Search Console at that time.

Note:  While the HDDS search facility is selected for use with the Search Console: •The Objects graph shows the number of indexed objects only if that facility is configured to show statistics. •For any period during which HCP cannot retrieve statistics from the HDDS server (for example, because the network connection is broken), the Objects graph shows the number of indexed objects as zero.

The x-axis in the Objects graph marks the passage of time. The y-axis measures the number of objects. As the number of objects increases, the intervals on the y-axis get larger. The graph heading indicates the current measurement unit (for example, thousands or millions).

To see the number of objects in the repository at a given point in time, hover over the top edge of the colored portion of the graph at the time you want.

Ingested Volume graph

The Ingested Volume graph shows the total size of the ingested data and custom metadata during the past 30 days (or since HCP was installed if that was less than 30 days ago). This value is the total size of the data and custom metadata before they were added to the repository. The value tells you how much data and custom metadata has been stored, not the amount of storage used.

Ingested volume includes the parts of in-progress multipart uploads that have already been written to the repository. Ingested volume does not include replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads. For information about multipart uploads, see Working with multipart uploads.

The x-axis in the Ingested Volume graph marks the passage of time. The y-axis measures the ingested volume in gigabytes, terabytes, or petabytes, depending on the system capacity. As the ingested volume increases, the intervals on the y-axis get larger. The graph heading indicates the current measurement unit (gigabytes (GB), terabytes (TB), or petabytes (PB)).

To see the ingested volume in the repository at a given point in time, hover over the top edge of the colored portion of the graph at the time you want.

Note: Due to compression and duplicate elimination, the ingested volume can be greater than the used storage capacity. For information about used storage capacity, see Storage graphs.

Updating the information

Below the System section option, the Overview page shows the most recent values for the number of objects stored (Ingested objects), the number of indexed objects, if applicable (Indexed objects), and the ingested volume (Ingested volume). The bottom left corner of the Overview page shows the date and time these values and the Objects and Ingested Volume graphs were last updated. To update these values and the graphs to show the most current information, click Refresh Now in the bottom right corner of the Overview page.

The Primary Storage section on the Overview page contains a graph showing the amount of used primary storage (both running and spindown) during the past 30 days (or since HCP was installed if that was less than 30 days ago). The used storage value is the total amount of storage occupied by object data, system and custom metadata, the metadata query engine index, and any redundant data required to satisfy data protection level and metadata protection level settings in service plans.

If the HCP system has S Series storage available to it, the Overview page also has an S Series Storage section that contains a graph showing the amount of used S Series storage during the past 30 days (or since HCP was installed if that was less than 30 days ago). The used storage value is the total amount of storage occupied by object data, system metadata, and any redundant data required to satisfy data protection level settings in service plans.

Used storage includes storage occupied by the parts of in-progress multipart uploads that have already been written to the repository. Used storage does not include replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads. For information about multipart uploads, see Working with multipart uploads.

The x-axes in the Primary Storage and S Series Storage graphs mark the passage of time. The y-axes measure the used storage in megabytes, gigabytes, terabytes, or petabytes, depending on the amount of used storage. As the amount of used storage increases, the intervals on the y-axis get larger. The graph heading indicates the current measurement unit (megabytes (MB), gigabytes (GB), terabytes (TB), or petabytes (PB)).

To see the amount of used storage at a given point in time, hover over the top edge of the colored portion of the graph at the time you want.

Above the Primary Storage graph heading, the Overview page shows the total amount of primary storage in the HCP system, excluding the space required for system overhead and the operating system. Above the S Series Storage graph heading, the Overview page shows the total amount of S Series storage available to the HCP system.

Below the Primary Storage section option, the Overview page shows the most recent value for the amount of used primary storage. Below the S Series Storage section option, the Overview page shows the most recent value for the amount of used S Series storage. The bottom left corner of the Overview page shows the date and time these values and the Primary Storage and S Series Storage graphs were last updated. To update these values and the graphs to show the most current information, click Refresh Now in the bottom right corner of the Overview page.

Note:  When merging data from identical objects, the Duplicate Elimination service flags the redundant data for deletion. Similarly, when compressing an object, the Compression/Encryption service flags the uncompressed version for deletion. The Primary Storage and S Series Storage graphs do not reflect space reclaimed by either service until the flagged data is actually deleted. For more information about the Duplicate Elimination service, see Duplicate Elimination service. For more information about the Compression/Encryption service, see Compression/Encryption service.

You need to keep these considerations in mind when monitoring your HCP system Overview page:

•When an HCP system begins to approach its total storage capacity, you need to add nodes, hard drives, or arrays depending on the type of system you have. For more information about the different types of available storage upgrades, contact your HCP sales representative. There are two ways to determine when it is time to add storage:

oA "Storage usage is percent-used" warning appears on the Overview page when the system has used 75 to 90 percent of its primary storage capacity. The warning becomes an alert when the system is over 90 percent of its total storage capacity. For more information about the storage usage alert and warning, see Overview page alerts.

oYou can also monitor your HCP system by checking the object count on the Overview page. The page contains a graph that shows the total number of objects that were stored in the repository during the past 30 days out of a maximum storage capacity. For more information about the Overview page graphs, see Storage graphs.