BREAKING NEWS: Park Place Technologies Acquires Reliant Technology Learn More

3 minute readThe Worst Things You Can Do With a VNX5300: Part 3

Welcome to part 3 of our series about the WORST things you can do with a VNX5300 storage system. If you missed parts 1 & 2, then read up!

These top admin mistakes for the VNX5300 storage system come from one of Reliant’s EMC VNX engineering experts, and we want to ensure that you can understand why these mistakes may occur and how to avoid them. So, what is another thing our engineering expert thinks is one of the biggest mistakes you can make with a VNX5300?

VNX5300 Mistake #3:

Creating extremely large LUNs without taking a recovery method into account.

What is a LUN?

A LUN, or logical unit number, is essentially an identifier for storage devices. LUNs convert physical disk space into logical storage space so a host server’s Operating System (OS) can access and use that storage. The size of a LUN is determined by the size of the storage pool or RAID group to which a LUN is “bound.” Traditional RAID groups had certain limitations such as the amount of drives that can be in the RAID group as well as IO performance limitations. Storage pools, unlike RAID groups, are not bound by the same limitations. So, when using storage pools instead of RAID groups, the size of the LUN can get significantly larger to accommodate larger types of data.

Don’t forget the recovery method!

One of the things that is important to keep in mind while creating these larger LUNs is the recovery method you will need for those LUNs. Make sure that you have the ability to restore that data – should something go wrong. Under RAID group configuration, you may be dealing with 500GB LUNs, while storage pools may increase the size of your LUNs to something like 9TB. The restoration time for those LUNs will vary greatly – especially depending on your recovery method. So, you have to make sure that you do not forget your data path, restoration, or tape speed (should you be backing up to tape instead of disk).

What’s the big takeaway?

So, what should you take away from this big VNX5300 mistake? Don’t forget to keep your recovery method in mind when you’re creating large LUNs for your storage system. You can easily get carried away and overlook recovery method details – which can definitely put you into a difficult situation in the future if you’re not careful.

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

Now you know three of the big mistakes you can make with an EMC VNX5300 storage system according to one of Reliant’s EMC storage engineering experts. Want to know the last 2 VNX5300 mistakes? You’ll have to check back later to find out!

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!

Subscribe to our newsletter for blog, End-of-Life (EOL/EOSL) dates, and data center news and information.

Reid Smith-Vaniz

by Reid Smith-Vaniz

Reid is the founder and CEO of Reliant Technology and for 14 years has pursued his mission to remove the pain associated with maintaining IT infrastructure. Reid writes on common challenges related to maintaining, servicing, tracking, budgeting, and upgrading technology.

Reliant Technology Cares

Reliant Technology Cares

When you have Reliant Technology support your data center, you help us support SERV International and provide thousands of meals for starving children.

About Reliant Technology

As Data Center and storage experts, Reliant Technology is available to provide consultations and solutions to your server backup needs. Our experienced engineers and IT specialists are ready to help you determine the best option for your Data Center. If you have a topic you would like to see discussed, or if you would like to submit an article for possible publication, please, get in touch with us.