The customer currently has a FlashArray//X with 40 TB of available block storage and needs to add 10 TB of file workloads while minimizing infrastructure costs. Let's analyze the options:
Analysis of Options:
A). Run both workloads on the current FlashArray:
Pure Storage FlashArray supports both block and file workloads using the Purity File Services feature, which allows customers to run file workloads directly on their FlashArray.
Since the FlashArray already has 40 TB of available storage, adding 10 TB of file workloads is feasible without requiring additional hardware. This is the most cost-effective solution.
B). Add another disk pool for file storage to their current FlashArray:
Adding a separate disk pool for file storage is unnecessary because Purity File Services can handle both block and file workloads on the same array.
C). Purchase an entry-level FlashBlade for the file workload:
While FlashBlade is designed for file and object workloads, purchasing a new FlashBlade would be significantly more expensive than leveraging the existing FlashArray. This option does not align with the customer's goal of minimizing costs.
D). NDU the FlashArray //X to a //XL and run both workloads there:
Upgrading the FlashArray//X to a FlashArray//XL via a Non-Disruptive Upgrade (NDU) is unnecessary for this use case. The current FlashArray//X has sufficient capacity to handle both workloads, and upgrading to a higher-tier array would increase costs unnecessarily.
Recommendation:
The most cost-effective solution is
A). Run both workloads on the current FlashArray, leveraging Purity File Services to support the file workload.
Reference: Purity File Services Documentation:
Purity File Services
Explains how to configure and use file services on FlashArray.
FlashArray Use Cases:
FlashArray Use Cases
Highlights the versatility of FlashArray for both block and file workloads.