- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: MSA 2050 storage question/issue
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 05:24 AM
тАО11-27-2018 05:24 AM
Hi,
Just got the responsibility for our MSA 2050 san.
I have some questions about the storrage.
B pool is right now "overcommited", it did have some TB free last day.
in Vcenter, i can see there should be about 6 TB
if i tjek the Volumes, attached to Pool B, i see there shoudl be 2.6 TB free (Size minus allocated)
how come i do get these 3 diffrent result? do i miss something?
/Anders
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 05:35 AM
тАО11-27-2018 05:35 AM
Re: MSA 2050 storage question/issue
>From the MSA "free space" standpoint, this means how much actual space you have left in the pool. This is what you really want to be concerned about. When this number reaches zero then the array will not except any more writes and you'll be in a world of hurt.
>From a VMWare perspective, it has no idea what you are doing on the back end. Because of the ability to "over commit" you could have provisioned a 16TB datastore with only 5TB of actual space in the SAN. So, if I've used 4TB of that then VMWare will tell you that you have 12TB left and the MSA will say you only have 1TB. The MSA value is what we are more concerned about.
So, add up all your volume sizes from Pool B and see how this differs from the space actually present in the pool. You really don't want to be wildly over committed/provisioned unless you're doing it with a specific purpose in mind and you are going to stay on top of the storage running out on the MSA and purchase additional storage before you actually run out. I prefer to turn over commitment off on the Pools as a safety mechanism but there are some valid reasons for it.
Finally, if you've recently deleted a bunch of stuff from a datastore, VMWare will show that free and the storage might not. This is because a zero reclaim has not occurred. Zero reclaim is handled differently in different versions of VMWare so best to search the VMWare KB's for guidance on your setup (or call VMWare support).
I work for HPE. The comments in this post are my own and do not represent an official reply from the company. No warranty or guarantees of any kind are expressed in my reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 05:44 AM
тАО11-27-2018 05:44 AM
Re: MSA 2050 storage question/issue
Hi, Thanks for your answer.
with the MSA standpoint, you mean the volumes?
i recently tried to migrate a our exchange server from one datastore to another datastore, in the same Pool. and id did fail. how can i see if it use double space? is it possible to "browse" the datastores?
/Anders
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 05:54 AM
тАО11-27-2018 05:54 AM
Re: MSA 2050 storage question/issue
Perhaps others, monitoring the thread, might have other suggestions but that's what I'd try.
I work for HPE. The comments in this post are my own and do not represent an official reply from the company. No warranty or guarantees of any kind are expressed in my reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 07:36 AM
тАО11-27-2018 07:36 AM
Re: MSA 2050 storage question/issue
Acording to this, i really dont have much space.
Im trying to see what really takes the space. but i cant find a soulution on that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 07:36 AM
тАО11-27-2018 07:36 AM
Re: MSA 2050 storage question/issue
Hello,
My understanding for VMotion of VMs is you must also be aware of the datastores the VMs are on and where you are attempting to migrate to. For example if you are moving the VM from datastore1 you need to move to another datastore that is accessable in VCenter. As a best practice you should also not span datastores for a VM.
As mentioned, be sure you have enough space to do the copy. It does require enough space to copy and then create a new VM.
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.
I work for HPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 07:58 AM
тАО11-27-2018 07:58 AM
SolutionYou have three different virtual disk groups in your Pool B "standard" tier that are different set sizes and, based on description may be different disk types and capacities. With this setup you will likely experience some performance issues. Ideally, all disks in a tier (standard, performance, archive) should all be the same speed and capacity and they should be added to the pool in set sizes that are consistent.
Also, according to your screen shot, you show 685MB free in your Pool B which is dangerously low if you are overcommitting. If you add up all of the volumes, you have provisioned from the MSA Pool B, are they more than the 10.6TB total size of the pool?
This is going to take some effort on your part. The question is are you just plain using more capacity than you have? If so, order some more disks. Or is the issue that you have deleted stuff that hasn't been zero reclaimed yet? Create a spreadsheet of all your data stores, what volumes those datastores use on the MSA, which pool those volumes are in, and columns for free and used space of the datastore as reported by VMWare.
We can try to help you make sense of that spreadsheet if needed but I think you'll start to get some answers by just going through the exercise yourself.
Best of luck
I work for HPE. The comments in this post are my own and do not represent an official reply from the company. No warranty or guarantees of any kind are expressed in my reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 08:21 AM - edited тАО11-27-2018 08:22 AM
тАО11-27-2018 08:21 AM - edited тАО11-27-2018 08:22 AM
Re: MSA 2050 storage question/issue
Hi, yes i see now the voloumegroups are bigger than the physical disk... VG on Pool B is 13,3 TB total. wich is over 2,7 TB over the physical disk.... on Pool B
ill try to make a spreadsheet, but im still sure the exchange is using double space as the migration failed last night, and the Pool B space was fine yesterday. And i cant fint a method to see that..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 08:28 AM
тАО11-27-2018 08:28 AM
Re: MSA 2050 storage question/issue
You can also take a look at this article and see if you can get some help with zero reclaim
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-B40D1420-26FD-4318-8A72-FA29C9A395C2.html
I work for HPE. The comments in this post are my own and do not represent an official reply from the company. No warranty or guarantees of any kind are expressed in my reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2018 09:32 AM
тАО11-27-2018 09:32 AM
Re: MSA 2050 storage question/issue
Deleted some VM's for about 200 gb. nothing happen on the pool thoug.. have set reclaimnation to high on datastores on Pool B. still reclaiming very slow. (100 mb every 10-15 minutes?)
Thanks for the tip anyway. im continue my journey :)
/Anders