@Tim_G said in Deployment Scenarios for the Dell PowerEdge VRTX:

I'd certainly love one of these for a home lab. That's for sure!

I can see the whole ROBO deployment scenario. Even in single/several use situations, like you mentioned... such as for specific critical high-performing services that won't outgrow it. Anywhere else, I'd feel stuck with it... what happens if you start to outgrow the resources? How scalable is it? That's what would determine it's worth for usage in place of regular 2u deployment servers.

Maybe I'm just not a blade type person.

It's really meant for contained scenarios where you know how big you will grow. For a normal SMB, the issue is growing into it, rather than outgrowing it.

@JaredBusch said in Scott Alan Miller: Storage 101:

@scottalanmiller said in Scott Alan Miller: Storage 101:

@s.hackleman said in Scott Alan Miller: Storage 101:

I didn't get to make it up, but I have been watching the sessions and burning up my data plan. Thanks for posting these. I also wanted to take a minute to call out the guy sitting front and center to just surf the internet the entire time SAM is talking.

I didn't even notice that, I'm going to look for it now.

In the red? That is @DustinB3403

Ha no it is not!

@Shuey said in Invalid Drive Movement from HP SmartArray P411 RAID Controller with StorageWorks MSA60:

Thanks again to everyone who replied and gave feedback on this. It's great to know that there's a solid community of knowledgeable people who are willing to share their expertise - I really appreciate it!!

Sadly we didn't find your solution. But happily you found it on your own!

I think describing the heads as moving in and out is more appropriate since they're mounted on an armature, like a record player, and not forward or backward. I often use record players as a description for clients when they ask how drives work.

In my writing, I try to avoid use 'but' and things like it (however, etc.). Replace the word 'but' with 'and' as an exercise to see how it changes your readers' perception.

You've got a couple sentences that are like Yoda. Eg, by doing this, and it's unnecessary.

Similary, the logical volume... You missed a comma. The same occurs in drive impressions, the stack.

A good article, and a great way to open discussion on SANs and how volumes, drives and RAID presentations can be partitioned or utilized efficiently.

@StuartJordan said in Backup File Server to DAS:

Wow what a thread, took me a while to read through it :)

We don't fool around around here!

Overview

Storage Spaces Direct seamlessly integrates with the features you know today that make up the Windows Server software defined storage stack, including Scale-Out File Server, Clustered Shared Volume File System (CSVFS), Storage Spaces and Failover Clustering. Figure 4 below illustrates the “Storage Spaces Direct” stack:

What's amazing is how many people read my posts and then are like "oh wow, I had no idea you thought that" when I do these things :)

On HyperV, the use of SMB3 is pretty nascent and very vendors provide a good platform for it. So there tends to be a trend to remain with iSCSI for HyperV because of this. Not because SMB3 isn't the better option at a protocol level but because it is so new it remains mostly impractical.

@alexntg said:

it would be a "dream job" for a storage-inclined IT professional.

@ScottLongHDS Welcome!