• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry
BrianS

What size should The System/Data Drive really be

15 posts in this topic

Hi

Up until now I thought that I had the WHS installation strategy clear in my mind but I am not so sure now after reading through many of the threads on this forum, I thought that the system/data drive should be the largest drive in the pool for the following reasons.

The data drive is the really only temporary storage or as many people are describing it now a "landing zone" only for your files, eventually the data will migrate across the other dives in the pool and the only thing left on the data drive are tombstones (pointers to the data)

If one of the drives in the pool throws it hand in and you have to remove it for any reason the data on the drive to be removed is migrated back to the data drive for redistrubution across the pool when it feels like it.

The system/data drive should be the fastest or at least not the slowest drive in the pool because it hold the OS and has the most work to do

I am not concerned at the moment because I only use one drive the other four are not in the pool but are shared as network drives these are used to back up my data (data is backed up at least twice)

There must be an optimum drive size for the system/data drive because If I have a 750 gig drive (my largest) as the main dive and all it does is hold tombstones that's a waste of drive space.

So, I have a 500Gb SataII drive (currently my main drive) but it could equally well be much smaller or larger, a 750 Gb ide 2x320 Gb IDE a 400Gb IDE and a 200 Gb ide, When PP1 is released and I have confidence in the system what is the optimal setup for a WHS

Thanks in advance to anyone who knows the answer or at least has a better understanding than me.

Brian

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

It's a difficult question to answer, unfortunately. There is no single right answer.

Complications

- You need a minimum of 80 GB (WHS won't install on anything less), and WHS will create a 20 GB partition for the operating system.

- Vista checks the size of the volume that a share resides on. If you have a 60 GB D:\ partition ("landing zone") and you try to copy a 61 GB file, Vista will error and tell you that there's not enough free space (even if you have 10 TB of other disks in the storage pool)

- PP1 is a lot less aggressive about moving files off the landing zone. We used to be able to count on DE moving files as soon as they stopped copying (and sometimes before, hence the data corruption bug), but I'm not sure we can anymore.

So, the real question is how much data will you be copying at one time?

Personally, I'd go with the fastest disk you have available as the system disk, within reason. The system disk, the disk controller, and the CPU (in that order in my opinion) are the bottlenecks when it comes to WHS storage transfer speed.

I'm using a 120 GB IDE disk as my system disk. That's backed by 2x 250 GB SATA and 2x 500 GB SATA disks in the storage pool, and a single 250 GB IDE disk that's out of the pool (used for Virtual Server images).

Share this post


Link to post
Share on other sites

I'd recomment a system drive of 200 to 500GB. It really depents on what you do with it.

Mine is 500GB, but I used to have a 250GB drive for a very long time and I never had problems with that except for copying very much files to the WHS. I used Total Commander for moving files from my main system to my WHS and when the error occured I simply waited an hour or so (to let drive extender do it's thing) to continue.

Share this post


Link to post
Share on other sites
I'd recomment a system drive of 200 to 500GB. It really depents on what you do with it.

Mine is 500GB, but I used to have a 250GB drive for a very long time and I never had problems with that except for copying very much files to the WHS. I used Total Commander for moving files from my main system to my WHS and when the error occured I simply waited an hour or so (to let drive extender do it's thing) to continue.

I think I might reserve judgement until I see what is happening what happens with PP1. The migrator semes to be a lot slower, needing more space on the landing zone to handle transfers.

Share this post


Link to post
Share on other sites

I personally recommend 500GB. It is fairly large, but not excessively so. It has plenty of room to grow, but again, isn't excessive. However if you are going to lots of storage space, all 1TB drives isn't a horrible idea.

Share this post


Link to post
Share on other sites

OK Thanks chaps

Better understanding now, basically big enough to migrate whatever data you have transferred over the period of time it takes to move the data to the other drives in the pool.

One last question though to put this one to bed "How much data does it migrate in 24 hours (specifically PP1) to the drives in the pool.

Thanks again

Brian

Share this post


Link to post
Share on other sites
One last question though to put this one to bed "How much data does it migrate in 24 hours (specifically PP1) to the drives in the pool.

Well, that's just the thing, we really can't tell. My box for example, one day on of the drives is instantly filled up, the other day I don't see much movement. But then again, I don't migrate much data on my box anymore. It's all on there allready.

So maybe you could tell us how that's working out :)

Share this post


Link to post
Share on other sites
- Vista checks the size of the volume that a share resides on. If you have a 60 GB D:\ partition ("landing zone") and you try to copy a 61 GB file, Vista will error and tell you that there's not enough free space (even if you have 10 TB of other disks in the storage pool)

Ahhhh........

I was experiencing this and wondered if it was due to something like this.

Ive got around this by migrating my files to my WHS in batches of 70Gb or so.

Share this post


Link to post
Share on other sites

i dont think any of this is really about drive size its more a case of the size of your daily backups. tbh the system is very flawed and not really the best method of backing up valuable data.

Share this post


Link to post
Share on other sites
tbh the system is very flawed and not really the best method of backing up valuable data.

You are welcome to your opinion but can you give more background to how you come to this conclusion. The backup functionality of WHS is one of the key features. What is the flaw that you see. Microsoft have made recomendations on making the "system" disk as large as possible (although conventional wisdom suggests 500gb is ample) - so constraining the system by using a small system disk is going to introduce issues.

Share this post


Link to post
Share on other sites
You are welcome to your opinion but can you give more background to how you come to this conclusion. The backup functionality of WHS is one of the key features. What is the flaw that you see. Microsoft have made recomendations on making the "system" disk as large as possible (although conventional wisdom suggests 500gb is ample) - so constraining the system by using a small system disk is going to introduce issues.

I am still working out the PP1 implications, but it is not indicative of how it will end up. My data drive with PP1 is filling up and won't seem to off-load to the other drives till it is nearly full. Hence it doesn't deem to matter what size it is, it will keep filling till about 10Gb free. You then have to hope it can off-load to the other drives quicker than you can carry on filling it (which it should as network should be slower than disk-disk transfers). I am hoping they make the Drive Extender a bit more aggressive than I have on my PP1 before final release.

Share this post


Link to post
Share on other sites
I am hoping they make the Drive Extender a bit more aggressive than I have on my PP1 before final release.

Ouchh....thats not good - have you reported it on Connect?

Are others experiencing that issue?

I'm going to post a link to your comments over in the PP1 discussion thread as this looks an interesting PP1 "feature" if others are also experiencing it

Share this post


Link to post
Share on other sites
Ouchh....thats not good - have you reported it on Connect?

Are others experiencing that issue?

I'm going to post a link to your comments over in the PP1 discussion thread as this looks an interesting PP1 "feature" if others are also experiencing it

I have seen others report it. I am doing some more tests at the moment and compiling a series of results.

Share this post


Link to post
Share on other sites

Well, unless you copy very large files, 80 GB should be enough. In that case, it has a 60 GB 'landing zone' and distributes from there. You'll be wanting a bigger drive when you, for example, do the .torrent thing on the server. Some (all?) .torrent clients allocate the space first and then keep filling up the empty file with actual data. Meaning, you'll have those huge files in the landing zone all the time until they are finished. Same would probably go for video files you start to work with immediately after copying it over too.

In short I'd recommend to get a large system drive. First, you'll be safe for the future without having to worry about space. Secondly, the prices for storage are down right now so a few € or $ more will buy you a lot more space. And using some old drive isn't recommended anyway as it'll probably run 24/7.

Share this post


Link to post
Share on other sites
Well, unless you copy very large files, 80 GB should be enough. In that case, it has a 60 GB 'landing zone' and distributes from there. You'll be wanting a bigger drive when you, for example, do the .torrent thing on the server. Some (all?) .torrent clients allocate the space first and then keep filling up the empty file with actual data. Meaning, you'll have those huge files in the landing zone all the time until they are finished. Same would probably go for video files you start to work with immediately after copying it over too.

In short I'd recommend to get a large system drive. First, you'll be safe for the future without having to worry about space. Secondly, the prices for storage are down right now so a few € or $ more will buy you a lot more space. And using some old drive isn't recommended anyway as it'll probably run 24/7.

Torrent allocation depends on your client. Not to mention, I use the D:\ drive for a bunch of stuff, like WSUS, MySQL, utorrent and a few other things. Not to mention, it is the landing zone....

I personally recommend 200GB-500GB for the system drive. And getting an enterprise class drive may be a good idea.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • I am running WSE2012 R2 and I only ever see red, yellow or green. I have never seen blue even when backing up. I can't explain what could be happening here, but maybe some feedback from other users may help us pin it down. What OS are your client PC's? Mine are all Win 10. Not sure if that may have a bearing.   
    • I made the leap from WHSv1 to WSE2012R2.  I like the new system but one thing seems to be missing.  In WHS v1, the tray icon would change colors to indicate various things blue - backing up now green - everything is healthy yellow - warnings detected (e.g. haven't backed up in a while) red - critical issues (e.g. recent backup failed) In WSE 2012 R2, however, I only get the blue and green indicators, even when there are critical errors on my home network.  For example, a server hard drive had failed for several weeks, but the connector icon in my system tray remained green.  I only discovered the issue when I happened to login to the dashboard for something else. Does anyone know if this feature has been removed in the latest WSE versions?  Or have I just mis-configured something?
    • I am building a new home server: I really want to use StableBit DrivePool and Scanner - am used to them and like the relative ease of use. Hardware = PC running Windows 7 Pro has SSD for OS and 5 additional 2TB HDDs + SansDigital Towerraid (model TR5M6G) connected by eSATA controller (pCie) with 5 2TB HDDs of varying age (2 brand new WD Red and the remaining 3 a combo of Hiatachi and Seagate of varying age - all test out fine for now). Towerraid is currently configured as JBOD, so I can't really see individual drives, and neither does StableBit drive pool - so I get a pool consisting 5 1.82 TB drives (the ones on the PC) and 1 giant 9.1TB drive. I have about 10 TB of data ready to go into this new build.  Will be adding more over time.  Not sure when but certain I'll have HDDs go bad on me, of course. My question(s): 1)  Is there a RAID configuration that will let StableBit do its thing watching individual drives and letting me identify sick drives that need to be removed/replaced?                           2)  If I decide to give up the RAID and just let DrivePool handle duplication, how do I configure the SansDig?                           3)  Am I just getting it all wrong from the get-go? Would appreciate any advice - thanks   
    • I have almost 10 TB in the storage pool so I was not surprised when my first server backup took a very long time (22 hrs.).  Lately the incremental server backups have been fast (15 - 18 min.)  Two days ago the server apparently initiated a full backup that failed twice but completed successfully this morning after about 23 hours.  An hour later the regular daily backup is back to a normal incremental backup times (18 min.) So why did the previous backup take so long, as long as a full backup would take? Does the server occasionally make a fresh start with a full backup to reduce the time a full incremental recovery takes?  (fewer increments, less processing time) I don't see a setting in the server backup options for specifying a number of increments between full backups, for example.    
    • I just posted a similar question elsewhere.  By Shadow Copies are you referring to the Windows 10 File History backups that periodically use shadow copy to backup open files? I too discovered that a huge amount of backup space was consumed by File History backups, no doubt because I was moving some large Blu-Ray files around.  That I fixed by moving the temporary and final file folders to the server, where they are backed up as part of the daily server backup.  That too, of course, uses Shadow Copies but that is another story. Has anyone done the math?  What is the equivalence .. or lack thereof ... between the traditional WS2012r2 (WHS v1 et al.) daily incremental backup :: and a Win7 System Image backup + File History backups? Restore time comparison? Which do you feel is best?
  • Popular Contributors