ViPR SRM 3.6 – 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 in ViPR SRM. 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

ViPR storage terminology

ViPR software-defined storage and ViPR virtual data center storage are different concepts.

What's included in ViPR software-defined storage?

In the ViPR SRM enterprise-wide reports, the array type "Software-defined" refers to arrays that are defined using ViPR and consist of the following storage assets:

How is commodity storage represented?

Commodity storage connected to ViPR nodes and managed by ViPR software is represented as virtual pools. Using the ViPR user interface, an administrator assigns the virtual pool space into data stores. Data stores can be assigned to virtual arrays. Commodity storage connected to ECS also uses the data store concept.

What's included in a ViPR virtual data center?

A ViPR virtual data center can incorporate arrays from many sources in addition to the ViPR software-defined storage arrays. For example, a virtual data center might include a combination of file, block, and object arrays defined on devices such as Isilon, VNX, and Centera, as well as ViPR software-defined arrays backed by commodity hardware.

For details about ViPR virtual data centers and the arrays, pools, and storage systems that comprise a virtual data center, use the reports under Report Library > EMC ViPR > Virtual Data Centers > <virtual_data_center_name> > Inventory.

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.


  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 ViPR. 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.


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 tenants and projects that were defined in ViPR.

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.


  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
    • object arrays in ViPR software-defined storage using commodity hardware
    • object arrays managed on ECS

    The last column in this report shows Used Object Count for each object array.

  3. To view object counts and object access numbers for tenants and projects defined in ViPR, navigate to Dashboards > Storage > Object Chargeback.

    Note Image
    This set of chargeback reports shows usage for objects on ViPR-managed commodity storage and on ECS-managed storage.

  4. Open one of the Capacity reports to see numbers of objects used by tenant or project.

  5. Open one of the Network Usage reports to see the number of times objects are accessed, by tenants and projects.


You learned how to track object counts by array, enterprise-wide. You also learned how easy object usage chargeback reporting is for tenants and projects defined in ViPR virtual data centers.

Back to Top

Monitor object storage health

ViPR SRM presents performance information for all arrays, including object arrays, on the same set of reports.

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.


  1. Log in to the Console and navigate to Operations > Situations to Watch .
  2. Explore the reports under Situations to Watch and Alerts for devices and components that might be experiencing problems. All device and array types are captured in these reports.
  3. 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.
  4. 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.

  5. To check the health of ViPR virtual data centers that might include software-defined object arrays:
    1. Navigate to Report Library > EMC ViPR > Operations > Health Dashboard.
      Two reports on that page distinguish between the ViPR cluster health and the supporting ViPR hosts:
      • The Virtual Data Centers report shows the health of the ViPR cluster that represents the virtual data center.
      • The ViPR Nodes report shows health for the ViPR servers.
    2. Navigate to Report Library > EMC ViPR > Operations > Situations to Watch and explore the reports under that node.
      Here is the ViPR report tree.

    3. To view alerts for all storage devices managed by ViPR, navigate to the global alerts area: All > Operations > Alerts.


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

Back to Top

View and change object service level criteria

ViPR SRM supports service levels for managing object storage. You can change the out of the box criteria for an object service level.

The out of the box object service level names are the same as those used for LUN service level groups, but the criteria rules for the two sets of service levels are not related or connected.

The initial object service levels are based upon the following:

The object service level reporting is by tenant and project.

The following scenario shows how to view object service level criteria and also how to customize the criteria. Assume that you are a system administrator tasked with enforcing service level agreements for object storage. You need to:
  • Review the grading criteria for the out of the box object service levels and customize the rules if needed.
  • For accounting and chargeback purposes, ensure that one of your object storage customers (the SRM Texas project) is consistently assigned to the Platinum service level.


  1. Log in to the Console, and click Administration in the banner.
  2. In the Administration navigation tree, click Centralized Management > Groups Management.
  3. In the Group Name list, click Object Service Levels.
    The Service Level definition page opens, showing the current members of the Platinum group.

  4. To view the service level criteria, click View All Service Level Rules.
    The initial criteria are similar to the following image.

    In the rules statements:

    virtual pool name (vspname)
    Impacts the service level if it contains the service level name. For example, if the bucket was provisioned out of a virtual pool with the name SRM Texas Platinum Object vPool, the Platinum service level is assigned to that space.
    Is essentially the number of virtual data centers that are linked together for object replication. A value of 1 represents an isolated virtual data center with only local object protection. A value of 2 represents two virtual data centers that replicate objects across the two sites. A value of 3 means three sites, and so on.
    The higher the numsites value, the better the protection. Therefore, the better service levels have higher numsites values.
  5. To add a rule that assigns the SRM Texas project to the Platinum service level regardless of number of sites:
    1. Close the Service Level Rules page by clicking OK in the lower right corner of the page.
    2. On the main page, click Platinum, and then click Edit.
    3. On the Edit Service Level page, click Add new rules set.

    4. Scroll to the bottom of the page to see the wizard that can help you create the new rule.
    5. In Select a type, choose Advanced.
    6. Move the cursor to the next field, and type the database field name (or a partial value) that you want to use in the rule. In this case, type pr (for project name).
      The wizard lists valid field names that begin with pr.
    7. Scan the resulting list, and select prjname.
    8. Select an operator. In this case, select Is for exact equal.
    9. Type the value that you want the rule to match. In this case, type SRM Texas.

  6. Click Save.
    The main page redisplays showing the current members of the Platinum group.

  7. Compare the current Platinum members to the original Platinum members in Step 3.


You have changed the criteria for the Platinum object service level to capture all SRM Texas project access.

Back to Top