Dismiss
Innovation
A platform built for AI
Unified, automated, and ready to turn data into intelligence.
Dismiss
June 16-18, Las Vegas
Pure//Accelerate® 2026
Discover how to unlock the true value of your data.
Dismiss
NVIDIA GTC San Jose 2026
Experience the Everpure difference at GTC
March 16-19 | Booth #935
San Jose McEnery Convention Center
5:17 Video
Three SafeMode Enhancements for Ransomware Protection | Everpure
Get these capabilities when you upgrade your existing FlashArrays to Purity 6.4 or buy a new array running Purity 6.4: Per-object SafeMode; Default Protection SafeMode; Auto-On SafeMode; for New Arrays
Click to View Transcript
Hi, my name is Ben. I'm a technical marketing engineer at pure storage and we're going to go over some new ransomware protection capabilities you get when you upgrade your existing flash arrays to PRT 64 or if you buy new flash arrays already running purity 6.4. These are per object safe mode or per protection group. Safe mode, default protection safe mode and
auto on safe mode for new erase. So let's dive in per P group or per protection group safe mode allows us to focus in on only specific protection groups. This gives us greater granularity and control over what is going to consume space on our array and exactly what we want protected. This is how this works. You click on protection,
you click on protection groups, you can see right here. We have a column called retention lock. I have a list of protection groups. They're all unlocked. None of them are protected. That means I can click on this protection group, I can click on the snapshot schedule, I can lower it, I can go back, I can disable it, I can do whatever I
want with this. This is not what we want when we have a protection group locked. When we are taking snapshots of critically important volumes. We don't want that snapshot scheduled to be modified or downgraded in any way. So we'll back out to protection groups and I just happen to have a protection group here. That's pretty important and you can see I have
a snapshot schedule. I have volumes that are members of this protection group and if I want to modify the schedule, I can come in here and I can Change this to five and change this to weeks. So that way we dramatically lower how many snapshots we take and how long we keep them click safe. And you can see I was able to do that without a
problem. So I'm gonna back out once again show you that the protection lock is unlocked. We'll go back into this protection group, you might have already noticed this window labeled safe mode. It says retention lock is unlocked. We'll click this option here. We will not enable it. Now it is ratcheted and not click safe.
Now if I want to come in here and try to lower the retention policy, I can't do it. The only way forward to lower or degrade the retention settings for this snapshot schedule is through customer support of pure storage. So with the full protection, we're going to introduce a new term here called container. A container is a generic word. It's an interesting word because it's specific
and at the same time. But in this case a container refers to a pod or the array itself. Right? You can see on this array, the dash represents the array and then I have three different containers that represent different pods. Now, what the fault protection is or what it does is it provides a protection group.
That is the default protection group for that container. So any volumes that are created within that container, inherit the snapshot and retention policies defined in that protection group. So basically to uncomplicated this here, are your containers? Are they protected? No. Do we want them protected?
Yes. So let's look at our first pod workload, click on this menu item here. Available protection groups. There aren't any Why? Because we do not have any protection groups in that container. Click cancel, click back on the pot. Workload will create a new protection group, click create
and we'll back out to the default protection page, click the menu again. And look there's my production group. Now I can select it and set it now. However, I have that protection group configured every new volume in the first pod workload will inherit the retention policies from that protection group. So in the previous example,
let's say we want the protection group. We were working with a very important stuff to be the default protection group for the array container. Well click this again, important stuff is here. It had a very aggressive retention policy. That's great. We'll click set and now we have a default protection group for the array container. That's all there is to it.
This is all straightforward. It is all self service. You can lock down individual protection groups if you want and you can also create default protection groups that cover entire containers if you want. A couple of clicks. If you need to modify or change these features, you have to contact support purity 6.4. We have auto on safe mode.
This provides out of the box enabled ransomware protection for new arrays, a new array defined as an array without any volumes on it whatsoever. New volumes are then automatically assigned a default protection group. Okay, leveraging, default protection and then snapshots are automatic for all new volumes.
Get these capabilities when you upgrade your existing FlashArrays to Purity 6.4 or buy a new array running Purity 6.4: Per-object SafeMode; Default Protection SafeMode; Auto-On SafeMode; for New Arrays
We Also Recommend...
Personalize for Me