Building a Nas Server.
Building a Nas Server.
Hello, I've chosen to set up a NAS server to store all my school/work documents. I'm planning to use Windows Server 2012 and need advice on the best case for my PC. Any recommendations? Should I opt for a regular motherboard or a dedicated server board? My reason for running Windows Server 2012 is its user-friendly sharing features, which aligns with my preference for Windows.
I think your school and work storage units use minimal space unless you’re a CAD designer, photographer, or video producer; even then, an 8-bay unit offers ample room. I’d suggest purchasing a ready-made option instead. You can choose from one bay up to eight, and most models accept various hard drives. Here are some options:
- http://www.amazon.com/QNAP-TS-453-Profes...s=qnap+nas
- http://www.amazon.com/QNAP-TS-431-Person...s=qnap+nas
- http://www.amazon.com/QNAP-Personal-2-41...s=qnap+nas
These units are generally straightforward to install and tailor to your requirements. Saving money is possible by opting for a pre-built model rather than building one yourself—it’s also simpler overall.
You’re interested in setting up your own server for learning and future IT work. I can guide you through the process of building a Windows Server and exploring server management. Let me know if you need tips on hardware, installation steps, or best practices!
I understand now, constructing it helps clarify things. I'll wait for someone with server experience to arrive and explain the approach, then I'll review their recommendations.
I operate a home server running 2K12, several FreeNAS units, and a test machine with Win Server 2016 TP3. Initially, I didn’t notice significant gains from upgrading to server-grade parts unless you prioritize the core components. My setup includes a Xeon X5660*2 server; outside of one specific use case, it performs similarly to my micro-test server and the NAS running an H81 board with 8GB RAM and a dual-core Haswell Pentium processor. You’ll likely trade off ECC memory for consumer models, but with solid backup plans you should be fine. For storage, choose cases with ample space for drives and other needs—my Xeon serves as a transcoding box for streaming video from FreeNAS. Unless you have a substantial budget, avoid bulky rackmount solutions; they’re costly for the value provided. Even my dual-core unit handled 1080P transcoding via Plex smoothly, though it struggled with large file batches to mobile devices. The main drawback was occasional delays when transcoding quickly from afar on a slow connection. The only advice is to invest in a reliable raid controller card.
As mentioned before, unless you require the main count, the additional options (IPMI), or you're overly cautious (that's me), you don't need premium motherboards. I use Windows Server 2012 R2 on my NAS, powered by a Xeon E5-2695V3 (a bit too much for a NAS) with ECC memory. Honestly, I might have preferred a Haswell i3 with ECC RAM, but I changed my mind to make the NAS also serve as a part-time rendering server. Windows Server is quite similar to regular Windows, though it demands more configuration. You’re responsible for setting everything up yourself—many settings need activation, like internet access (turned on only after enabling the adapter) or audio (usually unnecessary for servers). Be sure to choose a GUI version when you install; there’s also a free one available.
For a case, I managed to find a used Super Micro 24 bay chassis for $199 on eBay near my location, but avoid rackmount solutions unless you really need many drives. I’d select a suitable case based on your drive requirements (possibly larger for future upgrades). Your choice of case is personal, so it’s important to know the number of drives and components beforehand.
Regarding RAID cards, don’t go cheap—look for a quality unit with a battery backup (around $600–800). Avoid low-cost options regardless of brand. I’d suggest the LSI 9360-8i, making sure to get the battery backup included. Running a RAID without a backup is risky if power fails, especially in Write Back mode where data stays in RAM until written.
It’s not as straightforward to set up a RAID card without a backup, particularly if you’re using Write Back. I recommend learning about Windows Server first or reading a guide. It’s not as simple as consumer versions, but it’s solid (unlike the default bloat in Windows 10).
You’ll need to turn on features you require—remote access, audio (not essential for servers), and antivirus protection. For antivirus, opt for enterprise solutions like Symantec Endpoint Protection instead of consumer products like Norton.
When choosing drives, consider RAID models such as WD Red, Red Pro, or enterprise-grade options if you can afford it. HGST NAS drives are also a good choice. A battery backup (UPS) is advisable for the server, though not mandatory.
If you want remote access via Windows Connexor and use Microsoft’s free remotewebaccess domain (yourname.remotewebaccess.com), keep in mind that the DNS server consumes significant RAM—about 1.3GB on my NAS. That’s a lot of memory usage on a 32GB system when idle.
Avoid using connector tools at all. HGST drives, WD Red/Pro and WD Black seem reliable. Enterprise-grade hard drives aren't necessary—they're not budget-friendly. Skip Seagate models and WD Greens; opt for any NAS drive with a 3-year warranty or more. I frequently use consumer SSDs and SSDs in production servers since they offer better value. I prefer running a RAID 60 with consumer drives instead of enterprise RAID 6, especially at similar costs. I keep enterprise SSDs for devices far from the main site (harder to replace/repair). My home NAS/server setup uses consumer SSD boot drives, plus some premium drives, and only my main PC runs pro-grade storage. Windows Server 2016 TP2 felt more challenging to set up than Server 2K12—especially for beginners. If you're a sysadmin, install Active Directory and Windows domain features, but avoid dynamic DNS unless necessary. You might need Intel NICs (10GbE or 1Gbit*4) plus bonding. Personally, I use two 10GbE bonded cards for the main server, a failover link with 4x 1Gbit, and an onboard NIC for management. Each NAS connects via four 1Gbit NICs, while my PC uses a dual 10GbE plus onboard card. I know this is excessive, but I managed to get many network cards cheaply. Watch out for 10GbE over copper—better use 10Gb Ethernet instead.