I'm trying to figure out how much space this Pure repo is using after its reduction. Veeam and Pure are reporting different numbers and I don't know why.
Veeam says it's using 179.9 TB out of 200.
Pure says it's using 150.35 TB out of 200.
We have 200 TB provisioned for the repository, so it's either 75% or 90% usage which makes a significant difference when making a storage purchase request. I'm inclined to believe the Pure numbers but why would Veeam show something different? And what will happen if it reaches 100% in Veeam but there's still space on the Pure?
Based on what Veeam is showing, you are using Windows with the repository drive set up with ReFS. If so, Veeam does not report correctly within the console, which is a known issue. I would follow up with Support to be safe but think you can go by the Pure numbers.
Yes it's Windows 2019 and ReFS. So is the problem in Windows then? This is the Pure volume in Windows. It looks like that's where Veeam is getting its numbers.
So what happens when the Windows volume gets full when there's still space on the storage? I'm having trouble finding documentation on the ReFS issue so please share if you know where it's at.
So that matches Veeam and would be where it pulls the numbers from. It is just the USED column in Veeam does not report correctly when ReFS with Block Cloning is used. So might be best to open a support case just for clarity and more information.
Oh I see, I wasn't referring to the "Used Space" for this issue, just the numbers that are highlighted in the screens. Thank you, I'll open a case. I guess the question is why does Windows think the array is fuller than it is.
