Storage Question
-
@BRRABill said:
@scottalanmiller said:
Depends on your specific needs. Generally no, but generally is 70% of the time, guesstimate. NTG went 100% colo about ten years ago, zero in house servers. Then went 100% cloud, nearly there now. So zero physical servers anywhere.Is it still an AD environment?
Yup, AD works great when not local.
-
@BRRABill said:
We do all sorts of file hosting. A lot of office files, but also all sorts of other business-related documents. Peachtree. Desktop DB files. Things like that. Is that what you meant?
Desktop DB files?
-
@BRRABill said:
BTW, specifically what 3rd party RAID card would you recommend going with?
Seems like even from this site people aren't keen on the H310.
I reached out to xByte and EDGE directly to inquire about their SSDs. But perhaps I should upgrade my PERC card regardless.
I guess whatever the model equivalent to the entry level H710 would be fine for me.
RAID cards are not something that you want to hear "entry level" associated with. I always want pretty high end RAID card. H710 with 1GB or 2GB cache and NVRAM would be good.
-
@BRRABill said:
Hmm, I left work, picked up kids from soccer, and came home. And this thread quieted. Let's keep it going!!
Most everyone had to go out and get dinner or whatever
-
@Dashrender said:
@scottalanmiller Do you join PC's to an Azure AD? Or does that concept kinda go away?
The old machines are on AD via Pertino. But that is going away as everything moves to Windows 10 and can connect directly to our AD that DirSyncs to Azure AD and Office 365.
-
@BRRABill said:
@Dashrender said:
@scottalanmiller Do you join PC's to an Azure AD? Or does that concept kinda go away?
That's what I want to know, too. Keep in mind we're using a 2003 Server from 2003. So all this stuff is new to me.
Time to consider dropping all servers completely!
How much total storage are you using today?
-
@Dashrender said:
@BRRABill said:
@Dashrender said:
@scottalanmiller Do you join PC's to an Azure AD? Or does that concept kinda go away?
That's what I want to know, too. Keep in mind we're using a 2003 Server from 2003. So all this stuff is new to me.
Looks like you can join a windows 10 PC to Azure. Not yet sure how Windows 7 and 8 play with it.
http://blogs.technet.com/b/ad/archive/2015/05/28/azure-ad-join-on-windows-10-devices.aspx
It's only Windows 10. You don't get that feature if you don't upgrade.
-
@scottalanmiller said:
@Dashrender said:
@BRRABill said:
@Dashrender said:
@scottalanmiller Do you join PC's to an Azure AD? Or does that concept kinda go away?
That's what I want to know, too. Keep in mind we're using a 2003 Server from 2003. So all this stuff is new to me.
Looks like you can join a windows 10 PC to Azure. Not yet sure how Windows 7 and 8 play with it.
http://blogs.technet.com/b/ad/archive/2015/05/28/azure-ad-join-on-windows-10-devices.aspx
It's only Windows 10. You don't get that feature if you don't upgrade.
LOL good thing I upgraded last night.
-
Time to get back to the core of this thread. Just waiting on @BRRABill to wake up
-
@scottalanmiller said:
Time to get back to the core of this thread. Just waiting on @BRRABill to wake up
Considering the new information - it really might be time to start a new thread.
-
I am up and ready now.
I already purchased the server, so I am going to keep it in-house for now.
My head is still spinning a little bit from yesterday.
I spoke to xByte. Their SSD drives do indeed work with the DELL servers. They have a yellow exclamation point in OMSA, but apparently the front panels works as expected, so that might be an option.
-
-
Haha!
So let's start working through this as a refresher.
Biggest thing from yesterday...
You still think it's a good risk not to have a second domain controller. I was able to stop the paperwork, so that will indeed save me $800 or so on a license and a few thousand on another server.
The only other thing I thought of was that if the server goes down, I lose my DC, and files serer, and mail server. But this new thing should be pretty darn reliable, so that's probably a good risk to take as well.
-
@BRRABill said:
You still think it's a good risk not to have a second domain controller. I was able to stop the paperwork, so that will indeed save me $800 or so on a license and a few thousand on another server.
In the light of day, it still seems like the right thing to do. That you can save the $800 makes it a pretty significant win.
-
if you split the load over two server, you're still loosing 50% of your stuff, and how usable is your business with one but not the other?
-
It was technically day yesterday when we decided.
Not just the $800 ... also the cost of another server.
-
@BRRABill said:
It was technically day yesterday when we decided.
Not just the $800 ... also the cost of another server.
And power, and cooling, and management.
-
@BRRABill said:
The only other thing I thought of was that if the server goes down, I lose my DC, and files serer, and mail server. But this new thing should be pretty darn reliable, so that's probably a good risk to take as well.
Yes, of course, but those things are tied together, right? So if one goes down the others may be useless or at least decline in value? Better to have fewer things to fail and fail all at once much of the time than more things to fail that likely fail at different times. Only have one thing to keep running, one thing to fix and everything is up or down.
-
@Dashrender said:
if you split the load over two server, you're still loosing 50% of your stuff, and how usable is your business with one but not the other?
Yeah I guess I was thinking it would be easier to spin in up off a backup, but it wouldn't be that much worse to do it twice. Plus I am considering outsourcing the e-mail in the near future anyway.
-
@BRRABill said:
@Dashrender said:
if you split the load over two server, you're still loosing 50% of your stuff, and how usable is your business with one but not the other?
Yeah I guess I was thinking it would be easier to spin in up off a backup, but it wouldn't be that much worse to do it twice. Plus I am considering outsourcing the e-mail in the near future anyway.
There shouldn't be a near future. NOW is when you should be doing it... You're already making a change. Change it all at once. One less move to do later.
