Reliant Technology - Top 5 VNX5300 Admin Mistakes

Welcome to part 4 of our 5 part series about the WORST things you can do with a VNX5300 storage system. If you missed the first 3 parts of this series read up here (Part 1, Part 2, Part 3).

These VNX5300 mistakes come from one of Reliant’s EMC engineering experts. We want to make sure that you understand why these mistakes may occur and how you can best avoid them. So, what is another one of the biggest mistakes our EMC VNX engineering expert thinks you can make on a VNX5300?

VNX5300 Mistake #4:

Provisioning LUNs without understanding the required workload.
 

Don’t be an I/O hog

For a quick refresher on LUNs and how they affect your storage pools with a VNX5300, check out part 3 of this series. Now, if you’re all caught up, you can take note of our fourth biggest mistake on a VNX5300 - provision your LUNs with a full understanding of your performance workload.

So, let’s say that you’re storing some photographs, documents, and other files on a VNX5300. That is relatively low latency and not very I/O intensive - so it shouldn’t really cause an issue with bringing down performance of the storage array. You have a full understanding of the provisioned LUNs workload and don’t really have to worry about a performance issue at that point.

Now, let’s say that your organization is implementing a new application that - although it will be awesome - will be really I/O intensive. You’ll want to discuss those performance requirements a bit more to truly understand what will be happening before just provisioning a LUN for that application within a group with other LUNs. If your application has high utilization and is I/O intensive, it has the potential to affect the performance of everyone else. You just really need to have a good contextual understanding of the other LUNs within that group to know whether or not an I/O intensive app should be within the same group as other I/O intensive and high utilization LUNs.

How much juice is in the pool?

Where you can run into problems with provisioning LUNs without understanding the workload on your EMC VNX5300 is when things get applied without understanding what it’s going to do. However, the reality is that, a lot of times, you don’t really know for sure - especially in managed services. So, you can have Company A, Company B, and Company C all within the same storage pool on your VNX5300. You don’t have as much visibility into what these companies are doing until you get a call saying that they’re having performance issues. Then you can look into the backend of the system, find their data set and look at it in relation to the other data sets within the system. So, you may have one group that sucks up all the “juice” in the pool without fully knowing what they’re running.

So, what can you do?

The reality is that you may not be able to understand the workload in all circumstances. However, when you know better… you do better. So, ask more questions to try and understand, as best as you can, the type of workload for each LUN so you can make sure to put LUNs in groups in a way where they’ll “place nice” and not bring the other LUNs to a lower performance level.

Now you know… so what are the other mistakes you can make with a VNX5300?

So, we’ve journied through 4 of the 5 biggest mistakes you can make on an EMC VNX5300 storage array - according to one of Reliant’s EMC VNX storage engineering experts. If you want to know the last mistake (and let me tell you, it’s a BIG mistake), then you’ll have to come back later to find out. So, dont’ miss out! Get the latest updates from Reliant Technology on all things storage through our Twitter and LinkedIn or check out other posts in our blog.

Want to know more?

Reliant Technology provides 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!