Forum Widgets
Recent Discussions
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 LimitsLudes4 days agoCommunity Manager6Views0likes0CommentsAnnouncing 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 MatrixLudes18 days agoCommunity Manager19Views2likes0CommentsBackup and Restore FA Configuration
Hi All, Purestorage has how to save or backup and restore configuration when an issue occurs? For example, the software crashed and could not be used anymore. Once the problem was fixed, we restored the existing configuration file from backup.Solved137Views2likes6CommentsSnapshots 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.Candyman9992 months agoNovice III160Views0likes4CommentsActiveCluster Asynchronous
Hello Having question about ActiveCluster Asynchronous is it possible to configure between 2 existing clusters Poland to Germany . Idea is to have ability to perform DR tests in Datacenters located in different country The customer is currently running a configuration based on X20R2/R4. They have two systems in the Poland and two in the Germany. Local replication between arrays is configured using ActiveCluster Synchronous. ################## Reviewed documentation is ActiveCluster over Fibre Channel and ActiveDR or Async is supported on the same system starting with Purity 6.1.3+. ActiveDR must be configured with separate volumes (and pods) from ActiveCluster volumes. ActiveCluster asynchronous works in such way that that both arrays Metro Arrays replicate data to 3d array protection group snapshot only Leveraging asynchronous replication is easy to do, it's a simple matter of defining a Target array in a Protection Group after connecting the array. Once defined in a Protection Group, the Protection Group itself can be moved into an ActiveCluster (our synchronous replication, RPO0 replication service) Pod, where the Protection Group is owned by two arrays. The defined Target can replicate regularly scheduled snapshots to a third array. This Active-Active Asynchronous Replication is shared by the ActiveCluster arrays and in the event that either array is offline, the alternate array will assume ownership of continual snapshot replication to the third array. In summary, you can replicate snapshots as desired between any number of arrays to any other number of arrays, requiring a defined array connection and Protection Group Target. These Protection Groups can also be moved into a pod for sharing between ActiveCluster arrays for disaster recovery purposes as well. The sequence of steps for enabling asynchronous replication: Connect arrays so the source and target arrays are aware of each other Create a Protection Group with desired snapshot policies Add any array to replicate snapshots to the Target field If using in an ActiveCluster pair, move the Protection Group into the ActiveCluster podSolved125Views1like3CommentsHaving 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.172Views0likes9CommentsIs there a way, on the flasharray (either GUI or CLI) to check connections hitting a specific port on one of the controllers?
I've got a support case open on this as well, but it appears that we have no hosts hitting one particular port on our array despite all configs looking correctjhunter2 months agoNovice I164Views0likes10CommentsHello All, I am a Sr. Architect with the Pure Professional Services team
Hello All, I am a Sr. Architect with the Pure Professional Services team. In our PS Delivery team, we spend a large amount of my time automating against FlashArray for various tasks, such as database refreshes, automated volume provisioning, DR/BC, zero touch provisioning, etc Recently, we have had a thought that it would be mutually beneficial for us to share our successes with the customer base, as well as create an open forum for you all to share with each other where you have had success. I have made a slack channel topic-automation-user-group where you can join if interested. If we can spark enough interest, we will attempt to meet quarterly. We will have an agenda for demos, guest speakers (including from your peers), open Q&A etc.33Views6likes0CommentsLast week there was a big announcement around the FA
Last week there was a big announcement around the FA being truly unified now Could someone please elaborate on what that means from a technical standpoint? (ive been through all the marketing material) Are there some new features to FA file or another architecture? Or is it just that 6.3.10 is now ER and therefore FA file is available to all, if enabled via Pure support? (so its actually been around since April last year when 6.3.0 was released)Solvedah2 months agoNovice I43Views1like1CommentI miss release notes for the 6.5.6, 6.5.5 and 6.5.4
I miss release notes for the 6.5.6, 6.5.5 and 6.5.4 Version: https://support.purestorage.com/bundle/m_flasharray_release/page/production-branch/content/documents/Production/FlashArray/FlashArray_Release/01_Purity_FA_Release_Notes/topics/reference/r_release_timeline_02.html|https://support.purestorage.com/bundle/m_flasharray_release/page/production-branch/conte[…]Release_Notes/topics/reference/r_release_timeline_02.html Have these Versions been pulled?Solved70Views0likes3Comments