Auto Configuration Analysis forHP XP Storage

HP XP

You’ve surely invested a great deal of time and money in your HP StorageWorks XP storage and carefully designed and implemented redundancy, availability and data protection. But what guarantees that your storage service will always deliver the required level of availability and efficiency that you expect?

It is difficult to maintain a configuration that is always aligned with vendor best-practices, and even harder to ensure that changes in other IT layers are well aligned with your HP XP storage array configuration. Unfortunately, even a minor gap between storage, compute and networking can put an entire business application at risk.

HP XP Configuration Analysis

A well-designed foundation is where it all starts or ends as the slightest misconfiguration can affect hundreds of servers and cause service or data loss issues. AvailabilityGuard automatically detects HP XP storage arrays and their configuration, including:

  • Model
  • Physical disks, LUs and LDEVs, S-VOL, P-VOL, WWN and more.
  • Array port mapping, storage pools, RAID level, etc.
  • Replication and Point in Time copies (dependencies, state, etc.)

The above information is correlated to other configuration data obtained by scanning servers, databases, virtualization, and more. This includes:

  • Host configuration, HBA configuration, LVM and filesystem configuration, and more
  • IO multipath tools – Hitachi Dynamic Link Manager (HDLM), HP Secure Path, HP MPIO XP DSM, Native MPIO, Veritas DMP and many other
  • HORCM configuration, copy group settings, consistency group (CTG)
  • Database configuration

HP XP Configuration Vulnerabilities

AvailabilityGuard performs HP XP risk analysis and checks for configuration issues or best-practice violations. Here are a few examples:

  • Detect data access risks (e.g., dead paths, sub-optimal multi-pathing policies, potential tampering, …)
  • Cluster data access risks (e.g., standby does not see all shared disks, has reduced bandwidth, etc.)
  • Detect storage alignment issues (e.g., database files, VMware VMFS, etc.)
  • Storage mapping
    • Devices to shared cluster (visibility, # of paths, state, locking, etc.)
    • Replicas to DR hosts
    • Detect SAN security breaches (e.g., Cluster LU visible by non-cluster member)
  • Hosts directly accessing storage managed by HP XP

HP XP Replication Considerations

AvailabilityGuard provides deep analysis of replication and mirroring, include Continuous Access, Business Copy and Snapshots. A few key checks are listed below – see more info on appropriate solution pages.

  • Detect partial replication (Continuous Access, Business Copy, Snapshots, etc.)
  • Detect potentially inconsistent replication / snapshots
  • Detect RPO and retention violations
  • Incorrect alignment to replicated storage (e.g., database data and log on same volume)
  • Detect redundant / old replicas