Monitoring HPE StoreOnce Backup 4.x

eG Enterprise offers an exclusive HPE StoreOnce Backup 4.x monitoring model (see ), which keeps tabs on the backup and restore operations performed by the appliance, and reports deviations much before they impact the performance of the server as a whole, or the dependent service.

Figure 1 : Layer model of HPE StoreOnce Backup 4.x

The metrics reported by the tests associated with the above layers will accurately answer the following queries:

  • Is the appliance, data service, license, or hardware status critical?

  • Are the available local disk and cloud capacity of the appliance too low?

  • Are there too many job sessions running on the appliance?

  • Is the memory and disk utilization percentage of the appliance too high?

  • Are the health and current status of StoreOnce Catalyst satisfactory? If not, then what is the current status?

  • What are the network and logical throughput of inbound and outbound jobs on each catalyst store?

  • Is the amount of data stored in the catalyst stores too high? If so, then how much?

  • Is the CPU utilization by the target appliance too high? If so, then which process is consuming more CPU?

  • Is the disk usage by the target appliance too high?

  • What is the level of IO activity on OS and data disks?

  • How well do the Ethernet and FC ports transmit and receive data?

  • Is there any abnormal memory usage by the target appliance?

  • What is the status, health, and replication status of the NAS services?

  • Is the health and replication status of each NAS share satisfactory?

  • Were encryption, deduplication, encryption, and size on disk quota enabled on the NAS shares?

  • How good is the IO processing ability of NAS shares?

  • Are there too many source and target replication jobs on the NAS shares?

  • What is the status and health of the replication service?

  • Are there too many source and target jobs running on the replication services?

  • Are there too many stores, shares, or libraries in a critical or warning state?

  • What is the status, health, and replication status of the VTL services?

  • How many remaining drives and libraries are there on the VTL service?