Get Started Here
Solution Forums
Connect with peers on today's solutions.
Product Forums
Learn and collaborate about the Everpure Platform.
Node Navigation
Featured Content
Start Here
Recent Discussions
First Preset and Counting
A bit routine, but this preset creates a volume to be used as a VMware datastore with a set regular size of 16GB. It also ensures "VMware Datastore" is in the volume name to quickly ascertain what the volume's use case is. Lastly, snapshots are taken every 6 hours and retained for 5-days. Create Regular Size 16GB Volume for a VMware Datastore w/6h5d SnapshotsCybersecurity Challenge: Your Mission - Analyze, Report & Defend! 🫡
October is Cybersecurity Awareness Month and as professionals we know that recognizing a threat is only the first step - knowing how to triage, investigate and mitigate it is what builds true cyber resilience. To kick off this special month, we’re challenging our community to put their incident response instincts to the test! 🔍 The Challenge: Threat Analysis & Response Take a look at the attached simulated phishing email. It’s loaded with initial indicators of compromise and social engineering tactics. Your Mission: Identify at least 5 distinct red flags hiding in this email. Go Beyond Awareness: Pick at least one red flag and explain how you or your organization would: Investigate: What logs, headers, or telemetry would you pull to verify the threat scope? Respond & Defend: What immediate remediation or control updates (e.g., mail gateway rules, SIEM detections, endpoint controls) would you implement to prevent impact? ✏️ How to Participate Examine the email screenshot above. Reply in the comments with your 5 identified red flags + your investigation/defense strategy. Check back on October 23rd when we share the answers! 🎁 Prizes & Bonus Entries 🎟️ Every detailed submission enters you into a raffle for a prize! 🚀 Want an extra entry? Share your response or this challenge on LinkedIn, tag/link back to the Community and paste the link in your comment reply! 🛡️ Why "Beyond Awareness" Matters Threat actors constantly adapt their tactics, techniques and procedures. Moving beyond passive identification into active triage and defensive engineering ensures that every member of our community acts as a sensor and defender. Drop your submission in the comments below! 👇
ActiveCluster for File Veeam Backup
Hello everyone :-) we recently got a Flasharray with the new "ActiveCluster for File" feature, which is pretty nice. We are trying to switch to Veeam. We are using VMware. I therfore created a Linux based Veeam Backup & Replication Server as well as linux based proxies in our vCenter. Backing up VMs via the hot-add transport mode works without any issues. The issue that we are facing is, how do we backup the NFS shares created from the "ActiveCluster for File"? Because Veeam sees the VMDKs from the VMs in the vCenter but doesen't see the NFS mounts from Everpure in the guest OS of the VM. My questions and thoughts are: Is it possible to create an physical Linux based on Veeam proxy and connected it to the Everpure FlashArray? According to this link, Everpure doesn't support the storage snapshot Integration feature https://helpcenter.veeam.com/docs/vbr/userguide/storage_system_requirements.html?ver=13 This is the Plugin I wanted to use with the physical proxy which is connected to the FlashArray https://www.veeam.com/kb4129 I can add the NFS Share into Veeam and create backjobs but how does it technically work? It uses the VBR Server as an proxy.. But is that the right way? How can I create Veeam backup jobs for NFS mounts (which are mounted on VMs in the vCenter, which Veeam doesn't see) provided by ActiveCluster for File ? How does a Veeam file share backup work technically and how should the recommended backup design be in this scenario? Thank you!‘Tis the Season: Share Your Spookiest "Data Horror Stories"! 👻
We kicked this month off with some Cybersecurity Awareness month fun, now let’s shift gears towards something a little more spooky to celebrate the Halloween season. As Data enthusiasts and professionals, we all have our dreaded Data Horror Story that sticks in the back of our minds. Will you have the scariest tale? 🕸️ We want to hear YOUR spooky stories! What is the most horrifying, hair-raising or downright just plain funny data mishap you’ve ever experienced? How did you escape that nightmare (or fix the query)? Whether it was a mysterious dashboard metric that unexpectedly plummeted to zero at 4:59 PM on a Friday or entering a server room that just gave you the chills - drop your best Data Horror Story in the comments below!ActiveCluster for File Veeam Backup
Hello everyone :-) we recently got a Flasharray with the new "ActiveCluster for File" feature, which is pretty nice. We are trying to switch to Veeam. We are using VMware. I therfore created a Linux based Veeam Backup & Replication Server as well as linux based proxies in our vCenter. Backing up VMs via the hot-add transport mode works without any issues. The issue that we are facing is, how do we backup the NFS shares created from the "ActiveCluster for File"? Because Veeam sees the VMDKs from the VMs in the vCenter but doesen't see the NFS mounts from Everpure in the guest OS of the VM. My questions and thoughts are: Is it possible to create an physical Linux based on Veeam proxy and connected it to the Everpure FlashArray? According to this link, Everpure doesn't support the storage snapshot Integration feature https://helpcenter.veeam.com/docs/vbr/userguide/storage_system_requirements.html?ver=13 This is the Plugin I wanted to use with the physical proxy which is connected to the FlashArray https://www.veeam.com/kb4129 I can add the NFS Share into Veeam and create backjobs but how does it technically work? It uses the VBR Server as an proxy.. But is that the right way? How can I create Veeam backup jobs for NFS mounts (which are mounted on VMs in the vCenter, which Veeam doesn't see) provided by ActiveCluster for File ? How does a Veeam file share backup work technically and how should the recommended backup design be in this scenario? Thank you!Azure Red Hat OpenShift with Everpure Cloud
Azure Red Hat OpenShift (ARO) can use Everpure Cloud for persistent block storage, for VMs and containers. Both Everpure Cloud options - Everpure Cloud Azure Native and Everpure Cloud Dedicated are certified with ARO, and the cluster-side setup is nearly identical for both. This post covers the architecture, configuration sequence, and the checks that catch most problems early. Two storage options, one ARO procedure Everpure Cloud Dedicated is an array you deploy into your Azure subscription. Everpure Cloud Azure Native is delivered through the Azure portal, where you deploy a Storage Pool into a delegated subnet in your own Azure Virtual Network. With Azure Native you manage the array through the Platform Console, which gives you the Purity GUI, REST API, and CLI. It's disabled by default and you enable it per Storage Pool. With Dedicated you use the Purity interface directly. Architecture ARO provides the compute platform for VMs and containers. The Storage Pool (or Dedicated array) provides persistent block storage, and PX-CSI connects the ARO worker nodes to it to provision and manage volumes. The solution uses two paths. Management path. PX-CSI talks to the Purity management endpoint to create and manage volumes. With Azure Native, the Platform Console is how you get that endpoint. Data path. iSCSI traffic flows between the ARO worker nodes and the storage over the Azure virtual network. Deploy the ARO cluster and the storage in the same Azure region and virtual network. Put ARO in its dedicated subnets and the Azure Native Storage Pool in a separate subnet delegated to the Everpure Cloud service. A jump host VM is optional, and it's handy for reaching both the cluster and the Platform Console. For the data path, keep it short and boring. Everpure's field guidance is no virtual network peering and no user-defined routes or virtual appliances between the workers and the storage. Walkthrough Enable the Platform Console (Azure Native only) In the Azure portal, open the Storage Pool, go to Settings, then Platform console, and set it to Enabled. Pick the access methods you need (GUI and REST API, and optionally SSH) and select Configure. Copy the management IP address and the cloudadmin user name from Connection details, then generate a one-time password. It's shown once, so copy it before you close the dialog. Browse to https://<management-IP-address>, sign in as cloudadmin, and create a local administrator account right away. cloudadmin is only for first access. Make sure your Network Security Group allows TCP 80 and 443 for the GUI and REST API, and TCP 22 if you enabled SSH, and limit those rules to your management addresses. Prepare the OpenShift cluster Log in to the cluster from your Azure VM, create the Portworx namespace, and turn on user workload monitoring so OpenShift can scrape Portworx metrics. RESOURCE_GROUP="<ARO cluster resource group name>" CLUSTER_NAME="<ARO cluster name>" ADMIN_PW=$(az aro list-credentials --name $CLUSTER_NAME \ --resource-group $RESOURCE_GROUP --query "kubeadminPassword" -o tsv) API_URL=$(az aro show --name $CLUSTER_NAME \ --resource-group $RESOURCE_GROUP --query "apiserverProfile.url" -o tsv) oc login $API_URL -u kubeadmin -p $ADMIN_PW oc create namespace portworx apiVersion: v1 kind: ConfigMap metadata: name: cluster-monitoring-config namespace: openshift-monitoring data: config.yaml: | enableUserWorkload: true Apply that with oc apply -f. Then, in the ARO web console, go to Ecosystem -> Software Catalog, search for Portworx Enterprise, and install it into the portworx namespace. Don't create a StorageCluster yet. It comes after the worker nodes and the credentials are ready. Configure worker nodes PX-CSI attaches volumes over iSCSI, so the workers need multipath and udev settings that match Everpure's Linux recommendations. Create a multipath.conf with "user_friendly_names no" and "find_multipaths no" (each controller has a single path), and a udev.rules file with the recommended queue depth and tuning. The same two files go on every worker. Base64-encode both with base64 -w0, and wrap them in a MachineConfig. apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfig metadata: name: 98-worker-pure-multipath labels: machineconfiguration.openshift.io/role: worker spec: config: ignition: version: 3.2.0 storage: files: - path: /etc/multipath.conf mode: 0644 contents: source: data:text/plain;charset=utf-8;base64,<base64-multipath-conf> - path: /etc/udev/rules.d/99-pure-storage.rules mode: 0644 contents: source: data:text/plain;charset=utf-8;base64,<base64-udev-rules> systemd: units: - name: iscsid.service enabled: true - name: multipathd.service enabled: true oc apply -f 98-worker-pure-multipath.yaml oc get mcp worker -w The Machine Config Operator merges this into the worker pool and rolls it out one node at a time, cordoning, draining, applying, and rebooting each. Wait until the worker pool shows Updated as True. Give PX-CSI access to the array Create a user with the Storage Admin role (or an equivalent tenant-scoped role if you use secure multi-tenancy) and generate an API token for it. On Dedicated, that looks like this: pureadmin create --access-policy storage_admin px-pure-user ssh px-pure-user@<array-management-IP> pureadmin create --api-token On Azure Native, do the same from the Platform Console. Next, describe the array in a pure.json file and load it into a secret in the portworx namespace. { "FlashArrays": [ { "MgmtEndPoint": "<management-endpoint-IP>", "APIToken": "<api-token>" } ] } oc create secret generic px-pure-secret \ --namespace portworx \ --from-file=pure.json=/path/to/pure.json The secret name has to be px-pure-secret, because PX-CSI looks for that name by default. Generate and apply the PX-CSI StorageCluster Open Portworx Central, go to Spec List, Create New Spec, and choose PX-CSI. Pick a supported release (26.1.x in the documented setup), set the namespace to portworx, choose Azure Red Hat OpenShift (or generic OpenShift, since the YAML is valid for both), set the access type to Block Storage and the SAN type to iSCSI, and leave the rest at defaults. Download the manifest and apply it. oc project portworx oc apply -f px-csi-storagecluster.yaml Watch the StorageCluster in the console until it reads Running. During creation PX-CSI reads px-pure-secret, parses pure.json, and uses those endpoints and the token to manage volumes. Verify and use oc get pods -n portworx | grep -E 'px|pure-csi' oc get storagecluster -n portworx All PX-CSI pods should be Running and the StorageCluster should report Online or Running. oc get sc PX-CSI creates several default px-pure-csi-* StorageClasses, pick your PX-CSI StorageClass with backend: pure_block or create your own. Create a PVC or VM against the class, bind it to a pod, and you'll see the volume appear in the Platform Console or Purity UI. When something doesn't work Start at the bottom of the stack and work up. Connectivity. From a worker, run iscsiadm discovery against the array endpoint, and check that initiator names are unique. Node configuration. Confirm multipath.conf and the udev rules landed on every worker, and that iscsid and multipathd are running. PX-CSI. Check that the pods are Running, the StorageCluster is Online, and px-pure-secret exists in the same namespace as the operator. Connect to workers oc get nodes oc debug node/<worker> -T -- chroot /host Check services (ensure iscsid and multipathd services are enabled and running on workers) and check config files are updated. cat /etc/multipath.conf cat /etc/udev/rules.d/99-pure-storage.rules Resources Everpure Cloud Dedicated with Azure Red Hat OpenShift and PX-CSI Deployment GuideEverpure Cloud Azure Native: A closer look at the Platform Console
In this post, I thought to take a closer look at the Platform Console for Everpure Cloud Azure Native. It provides access to a Storage Pool through the familiar Purity GUI, REST API, and CLI, giving storage administrators an additional way to handle advanced configurations. The important distinction here is that the Platform Console complements the Azure-native experience. It does not replace it. Azure remains the primary interface for day-to-day management, while the Platform Console is intended for specific tasks that Azure does not expose. What does it add? Let's start with the practical use cases. Storage configuration outside Azure Resource Manager The Platform Console allows you to create and manage Purity resources such as standalone volumes, hosts, host groups, protection groups, and snapshot policies outside Azure Resource Manager (ARM). This gives administrators more flexibility when a supported storage workflow requires objects or settings that are not available through the Azure-native interface. For teams already familiar with Purity, it also means working with interfaces they already know. Snapshot management For resources managed through the Platform Console, you can create manual snapshots, configure snapshot schedules, and restore snapshots. The benefit here is control over when recovery points are created and how snapshot protection is configured for those resources. However, it is important to keep resource ownership clear when using both Azure and the Platform Console. More on that below. Automation and monitoring Supported storage workflows can be automated through the REST API, SDKs, or CLI. Local users can generate API tokens for REST access and upload SSH public keys for command-line access. Array metrics can also be collected through the OpenMetrics endpoint using a local-user API token. This provides a way to collect storage metrics for monitoring workflows, alongside the ability to script supported administrative tasks rather than perform each operation manually. Getting access One Platform Console is available per Storage Pool. It is disabled by default and must be explicitly enabled from Azure. In the Azure portal, open the Storage Pool and navigate to Settings → Platform console. Web console and REST API access are enabled together, while SSH can be enabled independently. Once the configuration is applied, the portal provides the management IP address and the pre-created cloudadmin user name. Initial access uses a one-time password generated from Azure. The cloudadmin account is temporary: it’s reserved for this first sign-in and removed when the password expires. Generating a new password recreates it. After signing in, create your own local users for ongoing administration. The management interfaces use the same delegated subnet as the storage data path. Because of that, use Network Security Groups to restrict management access to the administrative hosts that need it. Application VMs do not need Platform Console access to consume storage. Two interfaces, but not interchangeable resource management This is probably the most important operational consideration. Resources created through Azure are tracked in Azure. Resources created through the Platform Console exist on the array, but are not visible to the Azure-native interface. There is also no hard isolation between the two. Changing or deleting an Azure-created resource through the Platform Console can leave Azure with stale information, causing subsequent operations to fail or report an incorrect state. A practical rule is therefore: Manage the lifecycle of Azure-created volumes and volume groups through Azure. Use the Platform Console for resources created there, or for specifically documented advanced configuration. Keep a record of resources created outside Azure so they are not overlooked during decommissioning. The summary The Platform Console adds flexibility where the Azure-native interface does not expose a supported storage operation. Familiar Purity tools, snapshot management, automation, and access to array metrics give administrators more options for advanced workflows. The key is to use those options deliberately: keep routine management in Azure, limit console access to the people and systems that need it, and maintain clear ownership of resources across the two interfaces. For the supported workflows, access requirements, and configuration instructions, refer to the Platform Console for Everpure Cloud Azure Native KB.
Proxmox VE
Hi all Hope you're all having a great day. We have several customers going down the Proxmox VE road. One of my colleagues was put onto https://github.com/kolesa-team/pve-purestorage-plugin as a possible solution (as using Pure behind Proxmox (using the native Proxmox release) is not a particularly Pure-like experience. Could someone from Pure comment on the plugin's validity/supportability?
Featured Places
Introductions
Welcome! Please introduce yourself to the Pure Storage Community.Pure User Groups
Explore groups and meetups near you./CODE
The Everpure /Code community is where collaboration thrives and everyone, from beginners taking their first steps to experts honing their craft, comes together to learn, share, and grow. In this inclusive space, find support, inspiration, and opportunities to elevate your automation, scripting, and coding skills, no matter your starting point or career position. The goal is to break barriers, solve challenges, and most of all, learn from each other.Career Growth
A forum to discuss career growth and skill development for technology professionals.
Featured Content
You're invite you to our first virtual PUG, the Everpure User Group! It's built for anyone who has been weighing what's next for their virtualization platform. You'll join a small, off-the-record gro...
5 days ago
October is Cybersecurity Awareness Month and as professionals we know that recognizing a threat is only the first step - knowing how to triage, investigate and mitigate it is what builds true cyber r...
7 days ago Greetings, I am just starting my Pure1 Workflows journey, and wanted to know some "Recipe ideas" others would recommend for beginners in order to get the hang of how to create them before progressing...
19 days ago
Fleet Security Assessment
The Pure1 Fleet Security Assessment provides a fleet-wide view of the security posture of FlashArray and FlashBlade systems by correlating each asset's current software ve...
1 month ago
