HPE StoreOnce

Application Version and Upgrade Details

Introduction

HPE StoreOnce is a backup and data deduplication solution offered by Hewlett Packard Enterprise (HPE). It is designed to address the challenges of data protection, backup, and recovery in modern IT environments. StoreOnce leverages advanced deduplication technology to optimize storage efficiency and reduce the storage footprint of backup data.

key aspects and features of HPE StoreOnce:

• Deduplication Technology: HPE StoreOnce employs deduplication at the source and target to eliminate redundant data, resulting in significant reductions in storage requirements. This helps optimize backup storage and network bandwidth.
• Efficient Data Movement: StoreOnce enables efficient data movement across the network, allowing organizations to perform backups and recovery operations without consuming excessive bandwidth.
• Scalability: HPE StoreOnce solutions are designed to scale horizontally, accommodating the growing data protection needs of businesses. This scalability is essential for environments with expanding data volumes.
• Integration with Backup Software: HPE StoreOnce is designed to work seamlessly with various backup software solutions, providing flexibility for organizations using different backup and recovery tools.
• Cloud Integration: Some StoreOnce models offer integration with cloud storage, allowing organizations to extend their backup and recovery capabilities to the cloud. This can be beneficial for long-term retention, disaster recovery, and hybrid cloud strategies.
• Advanced Recovery Features: StoreOnce provides features for rapid and granular recovery, enabling organizations to quickly restore data and applications in the event of data loss or system failures.
• Security and Compliance: HPE StoreOnce includes features to enhance data security and meet compliance requirements. This includes encryption capabilities to protect sensitive data during transmission and storage.
• Centralized Management: StoreOnce solutions often come with centralized management interfaces that allow administrators to monitor, configure, and manage backup and deduplication operations from a single console.
• Appliance and Software Options: HPE offers StoreOnce as both physical appliances and as software that can be deployed on existing hardware. This provides flexibility for organizations with different infrastructure requirements.

HPE StoreOnce is positioned as part of HPE’s broader portfolio of data storage and management solutions. It aims to provide reliable and efficient data protection capabilities for enterprises of varying sizes, offering a balance between performance, scalability, and cost-effectiveness in backup and recovery operations.

Key Use cases

Discovery Use cases

• It discovers the HPE StoreOnce components.
• Publishes relationships between resources to have a topological view and ease of maintenance.

Monitoring Use cases

• Provides metrics related to status, utilization on different resources.
• Concern alerts will be generated for each metric to notify the administrator regarding the issue with the resource.

Prerequisites

• Classic gateway version should be 14.0.0 and above.
• Nextgen gateway version should be 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.

Hierarchy of HPE StoreOnce Resource

-HPE StoreOnce System
        -HPE StoreOnce System Cpu
        -HPE StoreOnce System iLOModule
        -HPE StoreOnce System Fan
        -HPE StoreOnce System HBA
        -HPE StoreOnce System Memory DIMM
        -HPE StoreOnce System PowerSupply
        -HPE StoreOnce System Temperature Sensor
        -HPE StoreOnce System Storage Cluster
              -HPE StoreOnce System Storage Controller
              -HPE StoreOnce System Pool
                      -HPE StoreOnce System Volume
                              -HPE StoreOnce System FileSystem
              -HPE StoreOnce System Drive Enclosure
                      -HPE StoreOnce System Drive
        -HPE StoreOnce Storage Cluster
              -HPE StoreOnce Storage Controller
              -HPE StoreOnce Storage Temperature Sensor
              -HPE StoreOnce Storage Pool
                      -HPE StoreOnce Storage Volume
              -HPE StoreOnce Storage Drive Enclosure
                      -HPE StoreOnce Storage IOModule
                              -HPE StoreOnce Storage Management Processor
                      -HPE StoreOnce Storage PowerSupply
                      -HPE StoreOnce Storage Fan
                      -HPE StoreOnce Storage Drive

Supported Metrics

Default Monitoring Configurations

HPE StoreOnce has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. Users can customize these default monitoring configurations as per their business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends doing this activity before installing the app to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of HPE StoreOnce. You can find those Device Management Policies at Setup > Resources > Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: hpe-storeonce HPE StoreOnce System - 1 (i.e, appName = hpe-storeonce, nativeType = HPE StoreOnce System, version = 1)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of iLO Redfish. You can find those templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: hpe-storeonce HPE StoreOnce System Template - 1 (i.e, appName = hpe-storeonce, nativeType = HPE StoreOnce System, version = 1)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find those monitors at Setup > Monitoring > Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: hpe-storeonce HPE StoreOnce System Monitor hpe-storeonce HPE StoreOnce System 1(i.e, monitorKey = HPE StoreOnce System, appName = hpe-storeonce, nativeType = HPE StoreOnce System, version = 1)

Configure and Install the HPE StoreOnce Integration

1. From All Clients, select a client.
2. Go to Setup > Account.
3. Select the Integrations and Apps tab.
4. The Installed Integrations page, where all the installed applications are displayed.
   Note: If there are no installed applications, it will navigate to the ADD APP page.
5. Click + ADD on the Installed Integrations page. The Available Integrations and Apps page displays all the available applications along with the newly created application with the version.
   Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.

6. Click ADD in the HPE StoreOnce application.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. Enter the below mentioned BASIC INFORMATION:

Notes:

• By default the Is Secure checkbox is selected.
• Ip Address/Host Name and Port should be accessible from Gateway.
• Select the following:
  • App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.
  • Alert Configuration: enables integrating third party alerts into OpsRamp using further configurations.
    • Below are the default values set for:
      • Alert Severity: Provides alerts severity and gets integrated out of all possible alerts.
        • Default Values: Critical, Disabled, OK, Unknown, Warning.
        • Possible Values: Critical, Disabled, OK, Unknown, Warning.
  • Alert On Root Resource: Checking this will generate event polling alerts on root resource.
    • Below are the default values set for:
      • Alert Severity Filters: Possible values of Alert Severity filter configuration property are [“Active”,“Cleared”,“Locked”,“None”]
      • Alert Severity Map: Provides alert severity map configuration. Default values for Alert Severity Mapping configuration are {“Active”:{“Critical”: “Critical”,“Disabled”: “Critical”,“OK”: “Ok”,“Unknown”: “Warning”,“Warning”: “Warning”},“Cleared”: {“Critical”: “Ok”,“Disabled”: “Ok”,“OK”: “Ok”,“Unknown”: “Ok”,“Warning”: “Ok”},“Locked”: {“Critical”: “Critical”,“Disabled”: “Critical”,“OK”: “Ok”,“Unknown”: “Warning”,“Warning”: “Warning”},“None”: {“Critical”: “Critical”,“Disabled”: “Critical”,“OK”: “Ok”,“Unknown”: “Warning”,“Warning”: “Warning”}}.

9. Select the below mentioned Custom Attribute:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

10. In the RESOURCE TYPE section, select:

    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.

11. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:

    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly

12. Click ADD.

Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.

13. Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

    Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

14. Click NEXT.

15. (Optional) Click +ADD to create a new collector by providing a name or use the pre-populated name.

16. Select an existing registered profile.

17. Click FINISH.

The application is installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed integration.

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select the HPE StoreOnce application.

View the HPE StoreOnce Details

To discover resources for HPE StoreOnce:

1. Navigate to Infrastructure > Search > SERVERS AND VMS > HPE StoreOnce.
2. The HPE StoreOnce page is displayed, select the application name.
3. The RESOURCE DETAILS page appears from the right.
4. Click the ellipsis (…) on the top right and select View details.

5. Navigate to the Attributes tab to view the discovery details.

6. Click the Metrics 2.0 tab to view the metric details for HPE StoreOnce.

View resource metrics

To confirm HPE StoreOnce monitoring, review the following:

• Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
• Alerts: Alerts are generated for metrics that are configured as defined for integration.

Resource Filter Input keys

HPE StoreOnce application Resources are filtered and discovered based on below keys:

Note: You filter the resources with the discoverable keys only.

Supported Alert Custom Macros

Customize the alert subject and description with below macros will generate alerts based on customisation.
Supported macros keys:

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure notifications for below two cases when user enables “App Failure Notifications” in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application will send any duplicate/repeat failure alert notification for every 6 hours.
• Latest snapshot metric is available from Gateway version 14.0.0.
• Using metrics for monitoring the resources and generating alerts when the threshold values are breached.
• Application cannot control monitoring pause/resume actions based on above alerts
• Component level thresholds can be configured on each resource level.
• No support of showing activity log and applied time.
• hpe-storeonce Event/Alert polling will be started only if the user enables Event/Alert Polling in configuration.
  Note: Here Event/Alert polling support is given for hpe-storeonce Alerts only.
• When a status value which presents in the Event/Alert Cleared Status field occurs, OpsRamp will create an Ok alert accordingly. Otherwise, OpsRamp will create an alert based on Event/Alert Severity Filter & Event/Alert Severity Mappings of Event/Alert Polling configurations.
• Possible hpe-storeonce Alert Severity Filter configuration are Active,Cleared,Locked,None.
• OpsRamp has given default mappings to map hpe-storeonce Severity with OpsRamp Severities as part of Alert Severity Mapping configuration.
• Users can modify them as per their use-case at any point of time from the application configuration page. Possible OpsRamp Severities are Critical, Warning, Ok, Info.