Recommended Posts

After having an issue with my RAID-5 array recently, that resulted in only 1 lost file, I decided it was time to finally upgrade. Going from 8x 2TB drives in RAID 5, I decided to move to a RAID 6 array, starting with 6x 3TB drives. The RAID 6 will allow me to have better resiliency if a drive dies, but I'm still planning on keeping not only a hot spare around, but a separate 3TB backup drive for critical files that will get backed up to nightly.

So my question is now, how best to partition my new server. I use it for the following:

1.) Hyper-V VM host (~300GB)

  • ?ADDC
  • Exchange 2010
  • Linux Anti spam/virus/phishing filter in front of exchange
  • Apache web server
  • subsonic media streamer
  • various other vms

2.) TV show / Movie repository for streaming to XBMC (~7TB)

3.) SVN Server for code/Electronic schematics/board files/gerbers (~80MB)

and a few other things. The RAID 6 array has a 64KB stripe size, and while it currently has 6x3TB drives, I bought a new case and 4 5-in-3 drive cages to allow me to increase it to 20 3TB (or 4TB in the future) drives.

Should I:

1.) Create one large array, then partition it into separate drives

2.) Create smaller RAID 6 arrays (or possibly RAID-1 arrays for critical stuff)

3.) Create multiple, different type arrays for each specific function above

My requirements would be that if necessary, I should be able to expand a volume if it needs more space (in windows drive manager), and that when space runs out, be able to easily add in and expand the array(s) with new drives. I am familiar with OCE, but im not sure if I can span different arrays on same drives (say a 4TB RAID 6 array, spanning 5x 3TB drives, plus a 4TB RAID-1 array on those same 5 drives). Ideally I'd prefer separate partitions/arrays, so that I can specify different block/strip sizes (SVN stuff is usually small, so say 32 or 64KB for that, whereas TV and movies are usually several gigabytes, so maybe a 512 or 1024KB strip for those).

Anyone have any recommendations?

so FWIW,I decided to do the following: I bought a SAS expander and several 5-in-3 cages, and will do the following config:

1.) 4x3TB in RAID-5 + 1 x 3TB Hotspare for movies and TV shows

2.) use 2 of my old 2TB drives to do a RAID-1 array for my SVN, photography, website, etc.

3.) grab 4x1TB, or possibly 4 of the 2TB drives I had and do a 0+1 for my Hyper-V VMs.

This way I can always plug in extra drives and either expand, migrate, etc, and I've got extra slots so I can put in other backups.

For the videos use refs or ntfs with 64k clusters

Yeah, originally i was trying to figure out how to best strip a single raid array for multiple uses, but I think it's better to do multiple arrays on the controller, then use something like:

512KB/1MB strip for the video content (64KB REFS)

32KB-64KB strip for SVN/photography(NTFS)

128-256KB strip for Hyper-V vms (64KB REFS system)

This topic is now closed to further replies.
  • Posts

    • Payday TWO!! Is 13 years old man I feel old - I remember trying it out and if I did not know I would say 5-6 years ago or something
    • Payday 2 engine upgrade adds 64-bit and DX11 support, drastically shrinks install size by Pulasthi Ariyasinghe Payday 2, the most popular entry in the heisting game franchise, is getting a surprising update after all these years. This is slated to be a complete engine upgrade that will enhance almost every aspect of the 13-year-old title, targeting performance, loading times, file size, rendering backend, and more. Developer Sidetrack Games is planning a beta to test out the new version ahead of the full public launch. The development team today revealed that the long-awaited upgrade to the 64-bit architecture is happening with this Diesel 3.0 engine update. By letting the game use more ram than 4GB, it is said to improve stability and compatibility on most hardware. It should also help modders in the long term with implementing larger changes too. "While many of the changes are made on the backend and not everything will be visible to you guys because it is a massive rewrite of the entire codebase, there will be a lot of things that you can look forward to," Sidetrack explained. Payday 2 will also hop over from DirectX 9 to 11. Instead of visual improvements, this is slated to reduce the amount of VRAM used by the title, letting more lower-end hardware access the title and run it better. Since these changes would require a complete redownload of the game anyway, Sidetrack says it has revamped "the game's packaging and bundling system." This should reduce the installation size from 86GB to 32GB. "So, now it's time to finally move the game to your SSDs," added the studio. The Payday 2 Diesel Engine 3.0 update is entering open beta on June 30 for Steam users. No console release plans were announced today. Sidetrack Games says it has been working on this complete rewrite of the codebase for the last nine months. While these changes should break most mods, the studio encouraged modders to use the beta period to repair their creations with support from the development team.
  • Recent Achievements

    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
    • First Post
      Kolakid60 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      440
    2. 2
      +Edouard
      194
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      68
  • Tell a friend

    Love Neowin? Tell a friend!