You need to share details of Pool size and Volume size where video recordings gets stored . Also share size details of volume which is presented in VMware where video recordings gets stored.
You have shared only volume allocation details but we need to understand provisioned size both at MSA and VMware as well.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
*************************************************************************
I work for HPE
Hi,
Could you launch an SSH session to controller management IP and execute the below commands and share the output?
show pools
show volumes
show volumes details
Please share the name of the Pool and volume as well.
While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
It looks like your Pool B is working as main storage for your Video recording. Your Pool B total capacity 28.7 TB and you have created 28.7TB volume as well. You have created thin volume at MSA end and out of 28.7TB, approx 28.3TB got used.
Now question is what type of volume you have created at the VMware end. It looks like you have created Thick provision volume (A Lazy Zeroed disk or Eager Zeroed disk). This is the reason most of the thin provisioned space of volume in MSA already got allocated. Do you think you have stored 26TB of video in this volume in real ?
Your Volume size shows 28.7TB as provisioned size in MSA and at the VMware side you should see same size only but you are seeing 26.14TB. If size different then your unit base may not be same. Operating systems usually show volume size in base 2. Disk drives usually show size in base 10. So change the base at MSA end and then compare size again.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
*************************************************************************
I work for HPE
I can see that even if video files getting deleted and new videos getting recreated in same space of VMFS but some block still getting consumed at MSA which should be really concern for you.
I am not sure which version of VMware you are dealing with but it seems auto space reclaim feature or auto unmap feature is enabled. Interesting thing to notice here at MSA end 4-MB pages gets reclaimed so you need to check what is the VMFS block size set. If it's set as 1-MB then auto reclaim will not work. You can check the VMware link to get more details,
You can manually try space reclaim or initiate space reclaim at VMFS level after video files gets deleted at VMFS level and check if that helps you. Please consult with your VMware admin before you try this as this may create performance issue.
Coming to MSA end, you check "show disk-group-statistics" outout and look for columns "Pages Deallocated per Min" and "Pages Reclaimed". This will give you idea that space getting reclaimed back at MSA end.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
*************************************************************************
I work for HPE
Hi,
28.7TB volume has been created from MSA storage and presented to host server.
While creating a data store you have the option to either use entire MSA volume capacity or any size lesser than MSA volume size.
I believe that entire MSA volume size would have been used to create data store in your configuration.
28.7 TB converts to 26.1 TiB
MSA by default represents size in TB and operating system in TiB.
You would need to monitor the free space of the command show pools.
Current status is 370.5 GB free space in Pool B.
You need to ensure that free space does not fall under 200GB.
As this is a thin provisioned Pool if any data is deleted from OS end the free space does not reflect in MSA immediately.
Space reclamation needs to happen in the backend for the actual free space to show up on MSA and this takes time.
Leaving just about 370 GB space and continuing daily back-ups might lead to Pool high threshold of 99.25% exceeding.
Exceeding Pool high threshold results in controller cache moving to write through mode and degraded performance.
I would suggest adding a new disk group to Pool B by adding drives to avoid the risk of Pool getting full/exceeding high threshold.
While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company