An ActiveCluster (AC) FlashArray pair lost connectivity with each other over the replication network. When the pod failover occurred, a single volume in the stretched pod lost connectivity to its host while other volumes in the stretched pod remained available to the host.
What is the most likely cause of the loss of stretched volume connectivity from the host?
ActiveCluster Connectivity Models: In an ActiveCluster environment, hosts can connect to the arrays using either a Uniform or Non-Uniform access model. In a Uniform model, the host has active paths to both FlashArrays in the cluster.
The Failover Scenario: When the replication network between the two arrays fails (a 'split-brain' scenario), the Mediator decides which array keeps the pod online (the winner) and which array takes it offline (the loser) to ensure data consistency.
Analyzing the Symptoms:
The pod failed over, meaning one array is now the exclusive servicer for that pod.
Most volumes in that pod stayed online for the host. This proves that the host is correctly registered in Purity (ruling out Option C) and that the general ActiveCluster/Pod logic is functioning.
Only one specific volume lost connectivity.
The Root Cause (Zoning/Access): If a single volume loses connectivity while others do not, it indicates a pathing issue specific to that volume's visibility. In an ActiveCluster failover, if the 'winning' array does not have a physical path to the host for that specific volume (due to missing FC Zoning or Ethernet VLAN tagging on the switches), the host will lose access once the 'losing' array drops its paths.
Why Option A is unlikely: If 'Uniform access' (the ability to see both arrays) was the issue, it would typically affect all volumes in the pod equally during a failover, not just a single outlier. The fact that the rest of the volumes remained available suggests the host is configured for uniform access, but the specific network plumbing (zoning) for that one volume's path to the surviving array is missing.
!
How is SAN Time measured?
Understanding Total Latency: In a FlashArray environment, total latency as seen by the host application is the sum of several components. Pure Storage breaks this down into Array Time and SAN Time to help administrators pinpoint where performance bottlenecks exist.
SAN Time Definition: SAN Time represents the latency introduced by the network infrastructure between the host (initiator) and the FlashArray (target). This includes the time spent traveling across Fibre Channel or Ethernet switches, cables, and host bus adapters (HBAs). It is calculated by taking the total round-trip time measured by the host and subtracting the time the FlashArray spent processing the I/O.
Metric Breakdown: * Array Time: The time the FlashArray takes to process the I/O once it hits the front-end ports (Option C describes internal array time).
SAN Time: The transit time for the request to reach the array and the response to return to the host (Option A).
Wait Time: In ActiveCluster environments, there is also 'Mirror Latency,' which is the time spent synchronizing data to a peer array (Option B).
Troubleshooting Value: If a user reports high latency but the FlashArray GUI shows very low Array Time, the administrator can look at the SAN Time metric. A high SAN Time indicates an issue with the fabric, such as a failing SFP, a congested switch port, or oversubscribed ISLs (Inter-Switch Links).
Which FA File Directory Services statement is correct?
Interface Separation: Pure Storage FlashArrays distinguish between Management traffic (used for the GUI, CLI, and Pure1 connectivity) and Data traffic (used for host connectivity). Within the data path, File Service Interfaces are the logical interfaces assigned to handle NFS and SMB traffic.
Directory Service Communication: For FA File to function, it must communicate with external identity providers (like Microsoft Active Directory or OpenLDAP) to authenticate users and resolve permissions.
The Default Path: By design, Purity prioritizes the File Service Interfaces for these lookups. This is because the directory servers (Domain Controllers) are typically located on the same production/data network as the clients accessing the files. Using the File Service Interface ensures that authentication traffic follows the same network path and security rules as the data traffic itself.
Why Option B is incorrect: While the array management plane can use the management interfaces for its own administrative LDAP/SAML logins, the File Services component defaults to the data-path (File) interfaces to avoid 'crossing the streams' between management and production data networks.
Why Option C is incorrect: Purity is very specific about its routing tables. It does not blindly use 'all' interfaces for DNS/Directory services. If a File Service interface is configured and active, it becomes the primary egress point for file-related metadata and authentication requests.
A FlashArray administrator has created a 1PB volume and wants to resize it to 1TB, but accidentally sets the new size to 1GB.
How can the administrator recover the potentially truncated data?
Purity Safety Mechanism: In Pure Storage Purity, volume resizing---specifically downsizing---is a destructive operation because it can lead to data truncation. To protect against human error (like the one described in the scenario), Purity automatically creates a 'pre-resize' snapshot of the volume before the change is committed.
The 'Destroyed' Snapshot: When a volume is shrunk, Purity generates a snapshot of the volume in its state immediately before the shrink operation. This snapshot is placed in the Destroyed (or 'Pending Eradication') bucket.
Recovery Process: To recover the data, the administrator does not simply 'resize back up' (Option C), as the data beyond the 1GB mark may have already been unmapped or treated as truncated by the host file system. Instead, the administrator should locate the auto-generated snapshot in the Destroyed volumes/snapshots section, 'recover' it to make it active again, and then either copy that snapshot to a new volume or overwrite the truncated volume from that snapshot.
SafeMode Integration: If SafeMode is enabled, these auto-generated snapshots are even more secure, as they cannot be manually eradicated before the timer expires, ensuring a guaranteed recovery point for accidental shrinks.
Why Option C is incorrect: Increasing the size of a volume back to 1TB (or 1PB) does not automatically restore the data that was logically removed or truncated when the volume was set to 1GB; the host file system would still see the data as corrupted or missing.
An administrator needs to enable Remote Assist (RA) on Purity version 6.8.4 to facilitate remote troubleshooting. Due to security restrictions, only certain commands can be executed on the array.
What type of access should the administrator grant when enabling RA?
Remote Assist (RA) Overview: Remote Assist is a secure, customer-initiated tunnel that allows Pure Storage Technical Support Engineers (TSEs) to log into a FlashArray to perform diagnostics and maintenance. It is disabled by default and must be explicitly opened by the customer.
Access Modes in Purity: In modern Purity versions (like 6.8.4), Pure Storage has introduced granular access controls for these support sessions to satisfy enterprise security and compliance requirements (such as SOC2 or HIPAA).
Restricted Access: This mode is specifically designed for high-security environments. When RA is enabled with the Restricted flag, the Support Engineer is limited to a pre-defined subset of non-destructive, read-only, or diagnostic commands. They cannot perform major configuration changes, delete data, or access sensitive metadata without further authorization.
Elevated vs. Secured: * Elevated access (often used during emergency recovery) provides the TSE with broader permissions, including the ability to run system-level scripts and configuration commands that go beyond standard diagnostics.
Secured is often a baseline state but does not imply the specific command-level filtering that 'Restricted' does.
Security Best Practice: If a security team mandates that 'only certain commands can be executed,' Restricted is the correct administrative choice. This ensures that the principle of least privilege is applied even to the vendor's support staff.
Dorothy Davis
2 months agoHarold Morgan
2 months agoEric Flores
3 months agoLaura Mitchell
3 months agoAmy Roberts
4 months agoLinda Scott
4 months agoRonald Reed
5 months agoAnthony Adams
6 months agoRichard Clark
6 months agoGary Jones
6 months agoSarah Moore
7 months agoMark Nguyen
7 months agoKevin King
6 months agoAdam Thomas
7 months agoMargaret Lee
7 months agoEmily Hill
7 months ago