Geeks, I am a newbie, trying to build a server for my skillset development.
I know .net development and wish to learn cloud-based technologies.
I am planning to set up a lab having around 10-20 virtual machines (SQL Server, Oracle, Workstation, build server, test server, LB etc...) using Hyper-V.
I have chosen a used Dell PowerEdge 1U R620 from eBay around $300. Configuration listed below.
Processor: 2 x Xeon E5-2670
RAM: 128 GB
HDD: None
No RAID cards & No power cables
The whole purpose of the server is ONLY for learning and 0% professional.
Geeks, please answer my questions.
1: Is this choice correct?
2: Can I add desktop HDD (5400 / 7200 rpm) to the server which is available on eBay for few bucks? Share, if there are any other cheap options.
3: Is it necessary to have a RAID card for up and running the server?
4: I am planning to have this server in my living room. Will it generate a lot of noise? (Work hours: ~4 hours of a day).
5: Is there any other important components I am missing?
6: What are all the key points I need to remember before starting the build? Let me know from your experience.
Thanks
a) That's, what, a 12th Gen? Yeah, that's a Sandy/Ivy-EP based machine. Decent, but recall the first rule of IT is the rule of diminishing returns on spending. $350 for a server like that is great. If you need to blow more than 30% on it to get a slight performance boost? Not worth it.
b) Depends on the chassis. Some chassis are SATA, some are SAS, and whether you can slot regular 3.5" HDDs depend on which chassis you got. I totally agree with the others here - HDDs are to be avoided unless it's only for long term archival storage - for regular I/O lifting, just get SSDs. They are much better IOPs wise and a bit less on the power consumption.
c) That'll depend on whether the machine comes with embedded PERC (PowerEdge Enterprise RAID Controller) or not, and whether you plan to attach more disks to the backplane. You might need an HBA (host bus adapter). Of course, whether you need to run RAID on it is another matter altogether, and resides upon whether you consider the contents ultimately disposable or not.
d) It'll sound like LaGuardia Airport for the first 4 minutes (between power-up to OS boot), but once the OS boots the 6 shrouded chassis fans should quiet down quickly (just keep the chsssis cover closed, okay?). That being said, even if it doesn't generate a lot of noise, it's still going to be chomping down on electricity - especially if both PSUs are drawing down on power. The 1U footprint might also make it immediately ridiculous in a typical living room.
e) Did you figure out what the networking options might be? On the R620s there is a mezzanine card between the PSUs and the IPMI port. Base models can have a dual or quadport Broadcom Gigabit Ethernet NICs, while more expensive models can have 10GbE or Infiniband adapters there. There is a PCIe x16 slot which some might use with a GPU, or add extra 10/40GbE NICs in. Then there is the question of where you want to situate the boot media. At my workplace the R620s are fitted with dual SD card slots in the back mezzanine that is used to house (typically) the VMWare ESXi boot volume. Depending on whether you plan to run ESXi, you might choose to do the same or not. Also, depending on whether you are planning out a homelab or not, you might want a set of Dell ReadyRails to go with a server rack.
Oh yeah, and finally - OS/software stack licensing. If you have an MSDN subscription and don't mind seeing the "unregistered software" watermark in the VMs that you log into, that's fine...just don't start begging strangers or trawling warez sites looking for software to run. If you are an IT guy or dev at a Microsoft shop chances are you'll have easy access to software in question. Just don't get too crazy with those privileges. I did have to put the kaboosh to a former dev of ours who used up half the MSDN entitlements for the company doing labs for stuff that he doesn't really use. Don't be that guy.
f) Permission from the missus/significant other or room-mates. If you are in a relationship, make sure they are okay with you running this beast, and there is an explicit understanding regarding who shall be paying for its upkeep. AFAIK no one only turn a server on and then power it off after about 2 hours. That's a 24/7/365 presence in your house, and all you'll do is to feed it more VMs, more tech and make it even more permanent (attache SAN/NAS to it, add VPN connectivity so you can reach it from outside the house, etc). Think of it more like a kilowatt chomping tamagotchi.