Many thanks to Nimble Support on this ..
I’m trying to run compression stats for Veeam on Nimble Volumes. Using iSCSI UNMAP between each test to clean up – but the reported GUI Used Space goes up. Trying to verify the best ‘Veeam compression’ option, to support my presentation which I am doing, on behalf of Nimble at VeeamOn 2014.
I am following these guides:-
I’m running ESXi 5.5 – and looked for on-line for CLI commands, but could only find a PowerCLI snap in on Nimble Connect but it wont install https://connect.nimblestorage.com/thread/1277 (This is a separate issue)
Ultimately I want to recommend an optimum compression setting, then maybe use this script to standardise the jobs.
Another thing I notice, is that after every iSCSI UNMAP command, the Snapshot Space increases – BUT I don’t have Snapshots enabled on this volume?
The volume I am monitoring is called: Zen-vPower and I am using this command, .. to clear out any unused blocks – in order to compare each Backup phase
esxcli storage vmfs unmap --volume-label=Zen-vPower
The answer is to use..
vol --info <volume_name>
This would give you the following information:
Volume usage (MB):
Volume space saved (MB):
Snapshot usage (MB):
Snapshot space reduction:
Snapshot space saved (MB):
Are you seeing the snapshot usage dwindle down for the volume eventually, after running unmap? It looks like the reclaimed space is being marked as “snapshot usage” temporarily.
Then, as garbage collection runs, and the space is recovered, you should see the snapshot usage decrease gradually.
Very interesting guys, thanks for the feedback