ViPR SRM 3.6.4 — Manage Object Storage using ViPR SRM

Table of Contents

Object storage reporting features

Learn how to view object storage capacity, object counts, and object usage trends using feautres introduced in ViPR SRM 3.6.4, or in ViPR SRM 3.6.3 Patch 1. Use ViPR SRM to monitor the health and performance of object arrays.

ViPR SRM supports the following reporting features for object storage:

Back to Top

Research available object storage capacity

ViPR SRM can help you make decisions about allocating object storage.

Assume that you are a system administrator with a request for 15TB of object storage from a new customer. You believe that your current collection of arrays on various devices is adequate. To provide solid confirmation, you use ViPR SRM to analyze object storage availability in your environment and research usage trends on existing object arrays.

Procedure

  1. Log in to the Console and navigate to Dashboards > Storage > Object Capacity Dashboard > Configured Usable Capacity.
    In the summary capacity report, you see at a glance that your environment contains more than 750,000GB of configured and available object storage.

  2. To determine the arrays that contain the free object storage, navigate to Explore > More Reports > Object Capacity.


    In this report, the Array Type column shows that your enterprise has object arrays defined on Centera and Atmos devices, in addition to a software-defined array managed by ECS. Looking in the Free column, you see that all but the first array could satisfy your requirement for 15TB (approximately 15,000GB).

  3. To analyze and compare usage trends on the arrays, navigate to Planning > Forecast Capacity Problems > Array Utilization.


    This report includes a column for Utilization Percentage and another column that projects when the array will be 90% full based on current usage. You want to choose an array that has a favorable, long term projection.

    The report shows that most arrays do not yet have configured pools and are not actively used.

Results

Using ViPR SRM, you confirmed that your current environment can handle the new request for 15TB of object storage. You identified several arrays to recommend, but know that the quickest approach would be the ECS array because the others do not yet have pools configured on them.

Back to Top

Monitor object counts and object usage

In ViPR SRM, you can track total object counts per object array. Additionally, object chargeback reports show object counts and object network access counts for ECS-managed namespaces and buckets.

Assume that you are administering an object storage program that charges some customers based on object counts and others by object usage. You want to use reports in ViPR SRM to track these numbers.

Procedure

  1. Log in to the Console.
  2. To view the number of objects stored across the enterprise, by object array, navigate to Explore > Storage > More Reports > Object Capacity.
    This report lists enterprise-wide object storage by array. The array types that you might see in this report include:
    • object arrays defined in Centera clusters
    • object arrays defined in Atmos clouds
    • (in ViPR SRM 3.6.4 and later) object arrays on commodity hardware managed by ECS
      Note Image
      In ViPR SRM 3.6.3 Patch 1, you can see object count information for ECS object arrays on the Report Library > Operations > Chargeback by Namespace report.

Back to Top

Monitor object storage health

ViPR SRM presents consolidated performance and alert reports for all devices, in addition to the report sets included in each SolutionPack.

Assume that you are a System Administrator with operational responsibility for several important object storage customers. It is important for you to recognize and address potential performance backlogs before they present as real problems to your customers.

Procedure

  1. Log in to the Console.
  2. Navigate to Operations > Situations to Watch and explore the performance reports for devices that might be experiencing problems.
    All device types are captured in these reports.
  3. To view alerts for all storage devices, enterprise-wide, go to Operations > Alerts.
    The Top Devices with Critical Alerts and High Impact Alerts reports are important to monitor.
  4. Perform a search to drill into more detail about a specific device listed on these reports:
    1. Copy a string, such as a device or array name, and paste it into the search box at the top of the page.
    2. Press Return.
      A results page contains links to all reports that contain the searched string.
    3. Click a link to go to the listed report.
  5. To monitor the health of EMC ECS 2.0 systems:
    1. Navigate to Report Library > EMC ECS > Operations > Health Dashboard > Virtual Data Centers.
      This report shows the health of a virtual data center from two perspectives:
      • The ECS system nodes, and,
      • The storage disks




    2. Click a row in the report to research specific problems. In this case, click the first row.


      The report shows which node in the ECS system is involved in the health problem. In this case, the fourth node has two bad disks attached.

    3. To discover which disks are bad, click the node row.
      The resulting page displays a set of reports for the node, showing resource usage, a list of services running on the node, various bandwidth trending graphs, and a list of disks attached to the node with status and health columns.

    4. Navigate to Report Library > EMC ECS > Operations > Situations to Watch, and use the following reports to monitor quotas and disks:


  6. To monitor Centera health:
    1. Navigate to Report Library > EMC Centera > Centera Summary.
    2. Notice the Offline column. You can drill into an offline cluster (array), if any, for more information.
    3. Navigate to an individual cluster name and then click Performance to display performance statistics.
    4. Click Max Lookup Time, and review the trends.
      For example, a consistent downward trend might need investigating.
    5. Navigate to Node Summary > Node Capacity Summary, and review the Free and Faulted capacity columns.
  7. To monitor Atmos health:
    1. Navigate to Report Library and click EMC Atmos.
    2. Review the System Overview report, which shows defined cloud instances and their availability and disk usage percentages.


    3. Check disk health using the Top-N Reports.
      Here is the Atmos report tree.

    4. Click Trending and Forecasting Analysis and evaluate displayed values for metrics such as CPU utilization, memory, and total disk space.
      Here is an example Memory Utilization report showing one node with high memory usage.

Results

You have researched the health of your object storage devices by using the ViPR SRM Report Library and the global alerts reports.

Back to Top

View ECS 2.0 chargeback reports

A set of ECS chargeback reports shows object storage usage and calculated costs by service level by namespace and by bucket.

Note Image
Information about chargeback reports applies only when the SolutionPack for EMC ECS is licensed for Full ViPR SRM (VIPRSRM_ECS_TB license).

The ECS chargeback reports provide the information needed to reclaim costs of storage from the owners of ECS namespaces or buckets, and to analyze storage usage and trends. The reports show usage metrics by a variety of attributes, described below.

Procedure

  1. Log in to the Console and navigate to the Chargeback by Namespace report.
    ViPR SRM 3.6.3.1 Report Library > EMC ECS > Operations > Chargeback by Namespace
    ViPR SRM 3.6.4 All > Dashboards > Storage > Object Chargeback > Chargeback by Namespace.




    The Total Cost column at the far right uses the cost per GB value assigned to the service level in Administration > Centralized Management > Groups Management > Bucket Service Levels.

  2. Click a namespace name to explore it in more detail.
    A set of reports appears for the namespace.
  3. Scroll to find the Buckets report.




  4. Click a bucket name for even more analysis about the bucket.
    A set of reports show details about object, network, and quota usage and trends for the bucket. One report shows cost by service level.

Back to Top

Bucket service levels

The SolutionPack for EMC ECS uses bucket service levels to classify object storage in ECS namespaces. You can create custom bucket service levels and edit existing ones. You can edit the service level cost basis for chargeback computations.

Note Image
Information about bucket service levels applies only when the SolutionPack for EMC ECS is licensed for Full ViPR SRM (VIPRSRM_ECS_TB license).

The bucket service levels are based on replication policy. A bucket that has the characteristics defined by the rules in the service level definition is assigned to that service level.

There are two out-of-the-box service levels:

Back to Top

Edit bucket service level cost basis

Change the cost basis used for the ECS bucket chargeback computations.

Procedure

  1. Log into the Console and navigate to Administration > Centralized Management > Groups Management > Bucket Service Levels.
  2. In the list under All, click a service level to select it.
  3. Click Edit.
  4. To change the cost basis, in the Cost per GB field, type a new value, and then click Save.
Back to Top

Create custom bucket service level

Create additional bucket service levels with different or more specific criteria than the out-of-the-box levels.

Suppose you want to create a bucket service level for a locally protected specific namespace and chargeback a different rate for that namespace.

Procedure

  1. Log into the Console and navigate to Administration > Centralized Management > Groups Management > Bucket Service Levels.
  2. Click All to select it, and then click Create.
    By selecting All, the new service level will appear directly under All in the list.
  3. In Service Level, type a name for the new service level.
  4. In Cost per GB, type a decimal value, such as .02, to represent a monetary unit.
  5. For the first rule, in Select a Property, select Component type, and fill in the next two fields with Is Bucket.
  6. Click Add rule.
  7. Create a second rule to define the replication as locally protected.
    numsites Is 1
  8. Click Add rule.
  9. Create a third rule to define the namespace.
    1. In Select a Property, select Advanced.
    2. Fill in the next two fields with ns Is.
      Note Image
      The database property name for namespace is ns.

    3. In the third field, select or type the namespace value.
      For example, you might have a rule ns Is apzatcity.
    4. Click Save.
  10. If you are not sure of the database property name, try this method to research it:
    1. Find a report that contains a column for the property you want.
    2. Click EDIT MODE at the top of that report page.
    3. Click the Reports Detail:Table tab.
    4. Click the blue bar for the column name.
    5. In the Property field, you see the database property name used for that column. You can use that value in your rules.
  11. Navigate to the Chargeback by Namespace report.
  12. After sufficient time for new collections, the Other Service Levels column begins to show metrics for the new service level.
  13. To create a column specifically for the new service level, edit the report definition to add a new column.
    For steps, see Add columns to a table report on the ViPR SRM 3.6 Documentation Index.
Back to Top