Pure Storage Purity Version 6.7.4 issues with Veeam

[ndaviscmm]

We have both HPE Nimble and Pure Storage arrays. We are utilizing storage snapshots for our less critical workloads. It had been working fine for both platforms for several years.

Recently, we upgraded our Pure Storage arrays to Purity version 6.7.4. That is when we began having issues.

The first issue was that anytime a recovery ran such as a SureBackup job, we would be alerted by the Pure array: Multipath configuration for one or more hosts appears to be incorrect. This may impact high availability.
Pure had us a do a workaround for this issue. Essentially, mounting an empty volume from the array to the vproxy to ensure redundant paths are available at all times. Not the best solution, but it stopped the alerts.

The second issue which we have not resolved is that our storage snapshots are not following our retention settings. The source or primary array retains the desired number of restore points. But the secondary target, which is another Pure array, does not. The issue being that we end retaining endless amounts of snapshots on that secondary target.

No errors are present. We can see in the logs that Veeam is sending the api call to delete the snapshots. Veeam then removes them from the database orphaning the snapshots.

I have an open case with Veeam that has been escalated. I also have a case with Pure, but I want to see if anyone else is seeing issues. I know not everyone uses Storage Snapshots or replicates them to a secondary target so my issue may not be common.

Does anyone else have Pure storage running 6.7.X and is using storage snapshots? Do you see issues as well? Are there any other issues with 6.7.X that you have seen?

Support has been tremendous trying to resolve the issue and I do not expect to find an answer here, I'm just hoping to find other datapoints.

Thank you!

[david.domask]

Hi ndaviscmm,

Thanks for the detailed explanation and sorry to hear about the difficulties.

For the SureBackup issue, I've heard of this challenge and it makes sense given how SureBackup works, and the workaround is suitable.

I'm not aware of any issues specifically as you're describing regarding the retention issues; can you please share your Veeam Support case number so we can review? Glad to hear Support is working hard on the issue for you, but as noted not aware of any such issue at first blush.

[ndaviscmm]

Our Veeam support case is 07779727!