I85PREP
⌘ K
HPE ATP Storage Solutions study materials
HPE ATP Storage Solutions study resources

HPE ATP Storage Solutions: Solution Integration and Customer Scenarios

HPE ATP Storage Solutions · Work through your exam, one topic at a time.

All guide sections

Solution Integration and Customer Scenarios

Domain 7: Solution Integration and Customer Scenarios

This domain tests whether you can integrate HPE storage into a customer’s real environment-virtualization, databases, SAP HANA, VDI, containers, backup, DR, cloud, and migration-and defend the choice against cost, risk, and operational constraints.

Integration patterns

  • VMware: VMFS or NFS datastores, VAAI support, vCenter plug-ins, SRM, Peer Persistence, and correct PSP/ALUA settings. Validate the array OS and ESXi version in the support matrix.
  • Microsoft: Hyper-V with SMB3 or block, CSV, MPIO, and SQL Server IO patterns. Separate logs and data where latency matters.
  • SAP HANA: use only certified HPE configurations for the specific model and OS version; confirm scale-up or scale-out, capacity, and tail requirements in the certification data.
  • Containers: use the supported CSI driver, storage classes, and persistent volume reclaim policies; test node failure and volume attach/detach.
  • Backup: integrate Veeam, Commvault, NetBackup, or HPE RMC with StoreOnce Catalyst and snapshots; verify catalog and restore, not just backup success.

Migration and cutover

Peer Motion supports array-to-array migration within supported families; Remote Copy supports replication-based migration; host-based migration remains valid for small scopes. Plan discovery, dependency mapping, replication seeding, cutover window, rollback, and application validation.

Customer scenario design

Ask about RPO/RTO, growth, compliance, existing skills, budget/opex preference, and current vendors. Match the tier to the SLA: Alletra 9000 for 100% guarantee and Peer Persistence; Alletra 6000/5000 for midrange; MSA for entry; StoreOnce for backup; GreenLake for consumption. Over-speccing is as wrong as under-speccing.

Worked example

A retailer has 200 VMs across three sites, VMware and Veeam, needs 15-minute RPO and 4-hour RTO, and has a tight budget. Alletra 6000 at the primary site with asynchronous replication to a secondary array meets the 15-minute RPO; a documented runbook and tested restore meet the 4-hour RTO; StoreOnce provides the Veeam backup target. Alletra 9000 with Peer Persistence would exceed the requirement and budget unless the SLA explicitly demands transparent failover and the 100% guarantee.

Traps that cost marks

  • Over-speccing or under-speccing without tying the choice to an SLA.
  • Assuming Peer Persistence is available on every Alletra model.
  • Ignoring backup software integration and restore testing.
  • Quoting SAP HANA without checking certification.
  • Planning migration without rollback or application validation.