In order to better support our growing community we've set up a new more powerful forum.
The new forum is at: http://community.covecube.com
The new forum is running IP.Board and will be our primary forum from now on.
This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.
Thank you,
When will it be safe to jump into the pool?
Tonight brand new HW will be assembled and WHS 2011 will be put on the new server. Having a WHS v1 with 5 TB data, the migration is going to take som time. Disk form the WHS v1 will have to be freed up and moved to the WHS v2 - one at the time.
In short WHS v1 will not be able to be a full backup for the WHS v2.
The migration is thus not going to start until DrivePool is reliable/stable. I guess that would be related to the designations RTM og RC?
Can you give an estimated date for the RC or RTM versions?
Am I to careful - is it safe to jump in now?
BR Steen
Comments
Yes he has. Personally i have been trying everything i can to break it on a test system since M2. I havent managed it yet.
And yes there are apparenttly a few bugs about but many of these seem to be related to having the full server backups in the pool. Personally thats something that i never intend to do.Unless i have missed something there is still the 2TB vhd limit in WHS 2011. Therefore i use a dedicated 2TB drive purely for server backup. Im struggling to see any advantage of having the full server backup in the pool.But as i said i may have missed something. I tend to agree with Snake. Its already as stable as in needs to be in that there is no way there is gonna be any data loss. I dont even have performance issues. The absolute slowest I/O speed i have had is about 35-40M/bps. That was writing files to the pool over the network.(so yes room for improvement but for me at least, non critical.) Reading from the pool and writing to a network device im getting 90-110 M/bps. This is no different to what i get going from a non-pooled drive to the network.
:-)
Only thing I have run into so far is "after-the-fact" balancing of the pool.. Not an issue, but after so many years on v1 and using DriveBalancer it is a little disheartening looking at those new 3TB hard drives I just added that don't have any data on them yet..
1. The function to remove data from a faulty or old drive to the rest of the pool in a 1 step process I.e click remove drive then get the option to either copy the data to the remaining pool or just eject
2 the option when adding new or replacement drive's to be able to balance them to the rest of the pool again 1 step process I.e insert new drive select add to pool then get the option to populate/balance the drive to the pool or just leave it blank
I think drivepool is a great program but I feel the above would be a great addition and as time goes by the question keeps getting asked "can we balance new drives"
So right now when you remove a drive from the pool, the data isn't copied over to the other drives in the pool?
Yep , i think there is an issue somewhere...but youre not alone. Im fortunate to be getting speeds similar to ArthurHawkins.
Going from a W7 pc (Complete with crappy Realtek Network Chip) to the pool with a 6GB files im averaging about 60 M/bps.Doing the same thing witha folder of iso files (around 70GB) im getting a minimum of 40 M/bps.
Going to a non pooled drive on the server the results are 95- 110 M/bps for the single file and 75M/bps for the folder.
My household often have 3 or 4 films on the pool playing to various devices around the house and there is never a stutter.
All that with a cheap sagem router from my isp and a £25 TP-Link Gigabit switch.
It really is difficult to fathom why some people are getting such poor speeds. Surely if the fault was solely with DrivePool then EVERYONE would have slow speeds...Your theory about it being hardware or driver related is the only possible thing i can think of.
I think it's critical to understand that there is a x8 difference between M/B and M/b. Incidentally m/b isn't a unit. MiB is.
Sure it can be assumed that everyone is using windows and are therefore reporting the copy speeds displayed but understanding the basics gives a good place to start to solve a problem from.
Also just to be pedantic, data doesn't move any faster the better the equipment you have, you can just move more at the same time, once this is understood it is easy to understand that the construction of a particular file, physical location on a mechanical disk and target location on a mechnical disk all play a part in the 'BANDWIDTH' available to copy/move with.
Paramount importance should be paid to the WHS OS disk. Buy the fastest SSD you can afford and keep it only for the OS, so a 160GB - 250GB will suffice.
Also i have found a marked improvement on file copy speed, by using third party copy handlers such as Teracopy and Ultracopier.
Also with Windows 7 I was found swsitching off 'Remote Differential Compression' in windows features in the program section of control panel helps alot with speed.
Fair point, i hadn't considered I was being excessive with an SSD but it makes sense.
However, since a system is only as fast as it's slowest component, and because i don't know all that much about the path data takes, i'm happier knowing any problem i do have isn't the OS HDD bottle-necking.
I didn't have any problems installing WHS 2011 on an OCZ Tech Colossus LT 250GB SSD.
Maybe i've got it backwards but i was sure you had to have minimum 160GB HDD to install WHS 2011.
Testament to how often i've re-installed WHS.
Dashboard is instant.
I'm only using mine as a media server, with off-server physical 1-1 backup, so not using all available features.
The main section is:
[WinPE]
ConfigDisk=1
CheckReqs=0
WindowsPartitionSize=MAX
You might try that and see if it will work.. Most anything that will work on WHS will work on Essentials.. not sure if that is necessarily true the other way around..