FlashArray: Purity 5.3 is out! What's new?

[ NOTE: machine translation with the help of DeepL translator without additional proofreading and spell checking ]


In the course of the continuous development and introduction of new features of the Pure Storage systems, the new software version 5.3.0 was made available for the FlashArray operating system "Purity" last Friday, August 20th.


I would like to keep this blog short and sweet, but as long as necessary to cover the essential new features. More information can be found in the Pure Storage "Purity//FA 5.3.x Release Notes" in the documentation (www.support.purestorage.com).


Purity 5.3 is not in any beta phase, but is fully GA and fully supported for production systems! Compatible here are all FA//X, FA//M and FA-4xx systems.


New features


new Purity "Maximums"/Limits for M70R2, X70R1/R2 and X90R2 *


  • maximum number of volumes p. array: 10 000

  • maximum number of NVMeOF volumes p. array: 500

  • maximum connected volumes p. host: 2 000

  • maximum number of volume snapshots p. array: 50 000

  • maximum vVol volumes p. array: 5 000

  • maximum number of (unstretched) pods p. array: 20

  • maximum number of stretched pods (ActiveCluster) p. Array: 12


* deviations of the values in ActiveCluster operation are possible.


new Purity "Maximums"/Limits for FA420/FA450, M20R2/X20R1/R2, M50R2/X50R1/R2


  • maximum number of volumes p. array: 5 000

  • maximum number of NVMeOF volumes p. array: 500

  • maximum number of volume snapshots p. array: 50 000

  • maximum vVol volumes p. array: 5 000

  • maximum number of stretched/unstretched pods (ActiveCluster) p. Array: 6


* deviations of the values in ActiveCluster operation are possible.


The maximum volume size remained unchanged at 4 PB for all FA systems.


In addition, the REST API was extended with new commands and released in version 2.0.


Microsoft Azure Blob as offload target


My last blog was about snapshot offload to NFS. With Purity 5.3, Pure Storage now makes Azure Blob accessible as a target storage in addition to NFS and S3 with their integration.


QoS - Quality of Service


Before Purity 5.3, it was only possible to set QoS limits on the respective bandwidth of a volume or volume groups. This was very difficult to implement for enterprises/service providers with guaranteed IOPS values and internal clearinghouses when set up with bandwidth limits. With Purity 5.3, QoS limits can now be defined on IOPS thresholds in addition to bandwidth.

The defined QoS values are now also exportable with the volume report (csv) and can be processed accordingly.


Of course, as usual with every software update, system bugs have been fixed and further software optimizations have been made to continuously improve Purity.


More info - Links


All officially published setting options in the GUI but also CLI can be read via the "on-board" user guides of the Pure Storage systems.


Click on "Help" in the Purity main menu.


The User Guide is structured like the main menu and can be opened downwards. A search function is also integrated - within here you can also search for keywords.

WEB: Pure Storage (Pure1) support portal - Ticket system and support *(requires registered FlashSystems)

PHONE: Pure Storage phone support: GER - (+49) (0)800 7239467; INTERNATIONAL - (+1) 650 7294088

WEB: Pure Storage community

WEB: Pure Storage OFFICIAL blog

The blog lives from your questions, wishes and suggestions...every comment is welcome. I am very grateful for feedback.

322 views0 comments