Forum Widgets
Recent Discussions
Is the concept of "refreshing" volume groups possible
Is the concept of "refreshing" volume groups possible on an existing copy of a volume group? Let me rephrase. Say I setup a volume group (VG) of 24 volumes (PRD01) that are for a production database. I want to snapshot that group of 24 volumes and create a copy of it to repurpose as a prod support DB copy (COPY01) and another copy to mount on another server to get backed up (COPY02). When its time to backup the server again can I refresh the data of PRD01 group to COPY02?
Why 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 and 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.
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.