HPE Peer Persistence for the Alletra 6000 (and Nimble) provides synchronous replication and automatic transparent failover (ATF) using the Automatic Switchover (ASO) feature. This process is governed by a Quorum Witness that monitors the health of both arrays in a group. A fundamental design principle of HPE high-availability storage is to prevent "flapping"--a condition where a workload repeatedly bounces between two sites due to an unstable connection.
Consequently, the ASO process is designed to be unidirectional and sticky. When a primary site failure occurs and the Quorum Witness authorizes an automatic switchover, the secondary array becomes the "Upstream" (active) array and begins serving I/O. Once the original primary site is restored and the replication link is re-established, the arrays will automatically begin a resynchronization to ensure data consistency. However, even after the data is fully synced, the system will not automatically move the workload back to the original array. The administrator must perform a manual handover to return the volume collection to its preferred primary site.

A foundational principle of the HPE CloudPhysics partner program is transparency and collaboration. When an HPE Partner invites a customer to run a CloudPhysics assessment (using the "Invite Customer" workflow in the Partner Portal), it establishes a shared view of the customer's data center environment.
According to the HPE CloudPhysics Partner and Customer User Guides, both the partner and the customer have access to the same set of analytics "cards" within the platform. This shared visibility is intentional; it allows the partner to act as a "trusted advisor" by walking the customer through the same data visualizations and insights that the partner is using to build their proposal.
Whether looking at the "Storage Inventory," "VM Rightsizing," or "Global Health Check" cards, both parties see the same data points, ensuring there is no "black box" logic in the assessment process. While partners have additional administrative tools in their specific Partner Portal (like the ability to manage multiple customer invitations or use the Card Builder for advanced custom queries), the actual environment assessment and the standard reports are based on the core cards available to both accounts.

Alletra Storage MP X10000 is designed for scale-out file and object workloads, supporting massive namespace growth and billions of files. StoreOnce handles backups, MSA targets midrange block storage, and tape is archival only.

When sizing a migration from a highly efficient array like the HPE Alletra 9000 (or Primera) to the next-generation HPE Alletra MP B10000, storage architects must account for the difference between the "Written Capacity" (what the host thinks it has stored) and the "Consumed Capacity" (the physical space used after data reduction).
The standard best practice for an HPE Master ASE when performing these migrations is to Size to consumption multiplied by 1.25. This "1.25 factor" (representing a 25% overhead) is the recommended safety margin used in sizing tools like HPE NinjaStars and the HPE Cloud Physics assessment reports. This 25% buffer is designed to cover several critical architectural requirements:
System Metadata and Overhead: Both the Alletra 9000 and Alletra MP require physical capacity to store internal metadata, map tables, and the structures required for their respective data reduction engines. Snapshot Reserve: While snapshots are thin and pointer-based, they still consume physical space as data changes over time. The 1.25 multiplier ensures there is enough
"headroom" for typical snapshot retention policies.
Data Reduction Parity: Data reduction ratios (deduplication and compression) can fluctuate based on the specific workload. Sizing exactly to current consumption without a buffer risks an out-of- space condition if the new array's reduction engine handles a specific block pattern slightly differently during the initial ingest.
Operational Performance: SSD-based arrays perform best when they are not "packed" to 100% capacity, as the garbage collection and wear-leveling processes require free blocks to operate efficiently.