Forum Widgets
Recent Discussions
Announcing the General Availability of Purity//FA 6.7.5 LLR
We are happy to announce the general availability of 6.7.5, the sixth release in the 6.7 Long-Life Release (LLR) line! This release line is based on the feature set introduced in 6.6, providing long-term consistency in capabilities, user experience, and interoperability, with the latest fixes and security updates. When the 6.7 LLR line demonstrates sufficient accumulated runtime data to be recommended for critical customer workloads, it will be declared Enterprise Ready (ER). Until then, Purity//FA 6.5 is the latest ER-designated LLR line. For more detailed information about bug fixes and security updates included in each release, see the release notes. UPGRADE RECOMMENDATIONS AND EOL SCHEDULE We recommend customers with compatible hardware who are looking for the latest feature set offered for long-term maintenance upgrade to this long-life release. When possible, customers should make use of Self-Service Upgrades (SSU) to ease the process of planning and executing non-disruptive Purity upgrades for their fleet. The 6.7 LLR line is planned for development through October 2027. HARDWARE SUPPORT This release is supported on the following FlashArray Platforms: Cloud Block Store for Azure and AWS, FA//X (R2, R3, R4), FA//C, FA//XL, and FA//E. Note, DFS software version 2.2.4 is recommended with this release. LINKS AND REFERENCES Purity//FA 6.7 Release Notes Purity//FA 6.6/6.7 Feature Content Self-Service Upgrades Purity//FA Release and End-of-Life Schedule FlashArray Hardware and End-of-Support DirectFlash Shelf Software Compatibility Matrix FlashArray Capacity and Feature Limits FlashArray Feature Interoperability MatrixWhy You Should Make Adopting Current Long-Life Releases a Habit
Hey everyone — At Pure Storage, we see many customers who still think about storage upgrades like old-school firmware: “set it and forget it” until it’s forced to change. But FlashArray isn’t firmware — it’s modern, continually improved, and designed for an agile, secure, predictable data platform. That means it’s time to make adopting recent Long-Life Releases (LLRs) a regular habit — not just something you reluctantly do, "when you have to". LLRs should be your standard practice: ✅ Fresh Features, Mature Code Each LLR is built on code that’s been running in production for at least 8 months before it branches. That means you get the innovations from recent Feature Releases — tested, stabilized, and production-proven. You avoid missing out on valuable improvements while still benefiting from enterprise-grade predictability. ✅ Consistent Security and Compliance Aging too far behind, even on an LLR, can expose you to security vulnerabilities and unsupported configurations. By habitually adopting recent LLRs, you ensure you’re in the supported window for critical patches and compliance audits — avoiding fire drills later. ✅ Reduce Technical Debt Getting stuck on very old LLRs can build up technical debt. Skipping multiple versions makes your next upgrade harder, riskier, and more time-consuming. Keeping up with recent LLRs means smoother transitions, less operational friction, and easier adoption of the next improvements. ✅ Keep Innovation Flowing The idea that an LLR is “old code” is a myth. Recent LLRs contain carefully chosen, well-hardened feature improvements. If you wait too long, you lock yourself out of meaningful performance, efficiency, and capability gains that your peers are already using. ✅ Break the Firmware Mentality FlashArray is software-driven, and has a rapid but reliable development model. Treating it like outdated firmware, and you miss the true value. The LLR program is designed precisely to let you safely adopt modern features and maintain enterprise-grade stability — and maintain a predictable cadence. Bottom line? Adopting recent Long-Life Releases, habitually, is the best way to get modern features, maintain security, reduce upgrade risk, and keep your environment aligned with Pure’s best practices. You deserve innovation and peace of mind — don’t settle for less by sticking with outdated code. If you want help reviewing which LLR is right for you, or understanding the timelines, just reach out — we’re here to help you stay current, secure, and ahead of the game.Announcing the General Availability of Purity//FA 6.5.11 LLR
We are happy to announce the general availability of 6.5.11, the twelfth release in the 6.5 Long-Life Release (LLR) line! This release line is based on the feature set introduced in 6.4, providing long-term consistency in capabilities, user experience, and interoperability, with the latest fixes and security updates. This 6.5 LLR line has demonstrated sufficient accumulated runtime data to be recommended for critical customer workloads and has been declared Enterprise Ready (ER) effective with the 6.5.3 release. For more detailed information about bug fixes and security updates included in each release, see the release notes. UPGRADE RECOMMENDATIONS AND EOL SCHEDULE We recommend customers already running 6.5 who are looking for the latest fixes and updates to upgrade to this long-life release. When possible, customers should make use of Self-Service Upgrades (SSU) to ease the process of planning and executing non-disruptive Purity upgrades for their fleet. The 6.5 LLR line is planned for development through September 2026. HARDWARE SUPPORT This release is supported on the following FlashArray Platforms: FA//M (R2), FA//X, FA//C, and FA//XL. Note, DFS software version 2.2.3 is recommended with this release. ACKNOWLEDGEMENTS We would like to thank everyone within the engineering, support, technical program management, product management, product marketing, finance and technical product specialist teams who contributed to this release. LINKS AND REFERENCES Purity//FA 6.5 Release Notes Self-Service Upgrades Purity//FA Release and End-of-Life Schedule FlashArray Hardware and End-of-Support DirectFlash Shelf Software Compatibility Matrix FlashArray Capacity and Feature LimitsAnnouncing the General Availability of Purity//FA 6.7.4 LLR
We are happy to announce the general availability of 6.7.4, the fifth release in the 6.7 Long-Life Release (LLR) line! This release line is based on the feature set introduced in 6.6, providing long-term consistency in capabilities, user experience, and interoperability, with the latest fixes and security updates. When the 6.7 LLR line demonstrates sufficient accumulated runtime data to be recommended for critical customer workloads, it will be declared Enterprise Ready (ER). Until then, Purity//FA 6.5 is the latest ER-designated LLR line. For more detailed information about bug fixes and security updates included in each release, see the release notes. UPGRADE RECOMMENDATIONS AND EOL SCHEDULE We recommend customers with compatible hardware who are looking for the latest feature set offered for long-term maintenance upgrade to this long-life release. When possible, customers should make use of Self-Service Upgrades (SSU) to ease the process of planning and executing non-disruptive Purity upgrades for their fleet. The 6.7 LLR line is planned for development through October 2027. HARDWARE SUPPORT This release is supported on the following FlashArray Platforms: Cloud Block Store for Azure and AWS, FA//X (R2, R3, R4), FA//C, FA//XL, and FA//E. Note, DFS software version 2.2.3 is recommended with this release. ACKNOWLEDGEMENTS We would like to thank everyone within the engineering, support, technical program management, product management, product marketing, finance and technical product specialist teams who contributed to this release. LINKS AND REFERENCES Purity//FA 6.7 Release Notes Purity//FA 6.6/6.7 Feature Content Self-Service Upgrades Purity//FA Release and End-of-Life Schedule FlashArray Hardware and End-of-Support DirectFlash Shelf Software Compatibility Matrix FlashArray Capacity and Feature Limits FlashArray Feature Interoperability Matrix
Snapshots and growth
I have a question about snapshot growth and retention. Last week we had 14 days worth of snapshots and due to some storage growth, we changed this to 7 days worth of snapshots. Before the change was made snapshots were taking up about 21 TB of space, after the change that number is around 10 TB. This reduction of space was more than expected. We expected around a 5 TB reduction. We just added up days 8-14 to get the 5 number. The other 6 TB reduction came from the most recent snapshot which at the time was 11 TB in size and now its down to around 5 TB in size. Does anybody know why the most current snapshot also had a large reduction after making this change? We are trying to figure out future growth including snapshot growth.
Having issues with Long HBA rescan times
Having issues with Long HBA rescan times. Any point in the right direction is appreciated. We already have a high priority ticket in but this coummunity has been helpful more than once! Vsphere 7.0.3.00600, Cisco UCS, Cisco MDS 9132 switches, Pure X90R3 Arrays.
Community Resources
Account Info & Registration
Check out these articles for user account and registration information.
Using the Community
A place to learn how to find your way around the community.