HPE7-J02 practice question 8 of 10

While attempting to increase an upstream volume size for an Alletra 6000 Peer Persistence setup from local web management, you are facing an error that prevents you from completing the task. Which action is required to complete the task successfully?

Full set: 50 questions
Answer options
A: Remove the upstream volume, volume collection before increasing the upstream volume.
B: Remove the downstream volume, volume collection before increasing the upstream volume.
C: Use the Data Services Cloud Console to grow the upstream volume. Correct answer
D: Increase the size of the volume in VMware HPE Storage plugin.
Correct Answer:
C. Use the Data Services Cloud Console to grow the upstream volume.
Explanation

HPE Alletra 6000 arrays are designed to be managed through the HPE Data Services Cloud Console (DSCC). Operations involving features that span multiple arrays, such as Peer Persistence, require centralized orchestration to ensure consistency. When attempting to increase the size of a replicated (upstream) volume, the change must be coordinated and applied to both the primary and secondary (downstream) systems simultaneously. The local web management interface of a single array lacks this cross-site orchestration capability, resulting in an error. The DSCC is the correct management plane to perform this task, as it orchestrates the volume growth across the entire Peer Persistence configuration seamlessly.

Why Incorrect

A. Removing the upstream volume is a destructive action that would cause data loss and is never a standard procedure for increasing volume size.
B. Removing the downstream volume would break the replication and high-availability configuration, which is a disruptive workaround, not the correct procedure.
D. The VMware HPE Storage plugin is an integration tool for vSphere administrators to manage datastores, not the primary interface for modifying core storage replication configurations.

References

1. HPE GreenLake for Block Storage built on HPE Alletra Storage MP Best Practices Guide, (a50006443enw, March 2023), Page 31, Section: "Volume sets and volumes".

The document states: "All provisioning and data protection operations are performed from the Data Services Cloud Console. You cannot perform these operations from the service console of the array." This principle applies to the Alletra 6000 series, confirming that management tasks like modifying volumes are performed via DSCC.

2. HPE Data Services Cloud Console User Guide, (Published on HPE Support Center), Section: "Storage > Block Storage > Volumes".

This guide details the procedures for managing volumes on cloud-connected arrays like the Alletra 6000. The "Edit Volume" functionality within the DSCC UI is the documented method for modifying volume properties, including size, for all volumes, including those under replication policies.

3. HPE Peer Persistence Software Technical White Paper, (4AA4-2809ENW, April 2020), Page 10, Section: "Management".

While this paper focuses on the underlying technology also used in 3PAR/Primera, it establishes the principle of centralized management for Peer Persistence to maintain a consistent state across sites. For the Alletra platform, the DSCC serves as this required centralized management entity.

Scroll to Top