What’s the worst thing you can do with a VNX5300? The honest truth is probably to spend too much money on the system, then proceed to never use it, but instead drop it off the side of a skyscraper, run it over with a bulldozer, blow it up with dynamite, set fire to the tiny remaining pieces, and give it a proper burial by sprinkling the ashes across the ocean. That’s probably the absolute worst thing you could do with a VNX5300. However, we certainly hope you wouldn’t do that – even though we’re pretty sure it would be amazing to watch.
We asked one of our engineering experts at Reliant what he thinks are the top 5 biggest mistakes you can make with a VNX5300. He gave us a list of mistakes that include technical mistakes, all the way to mismanagement of the system itself.
Since each of these VNX5300 mistakes can seriously affect your system performance and company’s bottom line, we want to take the time to explain each one thoroughly – and how best to avoid them in the first place. We’re creating this series about the 5 worst things you can do with a VNX5300 – so you’ll have to check our Storage Blog to find out each of the 5 mistakes.
But, we don’t want to create a blog post without telling you at least one of the mistakes. What’s one of the top 5 mistakes you can make with a VNX5300 according to one of Reliant’s EMC VNX engineering experts?
VNX5300 Mistake #1:
Using thin provisioning when thick provisioning would have been a better solution.
First, what exactly is thin provisioning?
Thin provisioning is essentially allocating storage on an as needed basis – based on the minimum required space for any single user at any given time. So, for simplicity’s sake in this example – say you have 3 team members of your company – and you tell each one of those team members that they have 1TB of space available on your VNX5300 system based on previous usage data. However, you may not actually have that 1TB per user that you promised allocated on your VNX5300 system at the time you tell your users about their “allotted space.” Instead, you may start out much smaller, with 350GB per user in actuality.
If those individual team members stay under the “actual” amount that you have allotted for them at any given time, then running out of space is a non-issue. What can cause an issue is if a user starts using a lot more space at a rapid rate for which you are unprepared. That can put you in quite a pinch on short notice. So, thin provisioning could mean additional administrative tasks onto your storage administrators essentially.
So, why does our engineer recommend thick provisioning?
Thick provisioning means that the capacity on a disk is pre-allocated when the disk is created. This would mean that 200GB virtual disk consumes exactly that much on a physical disk That means that the disk is unavailable for anything else – even if no data has actually been written to that disk. So, while thin provisioning can avoid wasting capacity on space that doesn’t end up being used and save on capacity costs, thick provisioning can help by offering less latency since all the storage space has been allocated at one time.
Now you know… so what are the other mistakes you can make with a VNX5300?
Now you know one of the biggest mistakes you can make on a VNX5300 according to one of our EMC Storage Engineering Experts at Reliant. Want to know the other 4 worst things you can do with a VNX5300? Check back later to find out!
Want to know more?
Reliant Technology provides the in-depth product knowledge and expertise around all things storage. If you are looking to upgrade your existing systems, want support for your storage, server, or networking hardware, or want to learn more – reach out to one of our storage specialists or call 1.877.227.0828. We’re here to help!