thanks
ANyone got an anwser to 2?
Ken already gave you a basic answer. It depends on how fast your network is, but with 2.5 TB of data, it's going to take quite a while no matter how fast your network is. If you were able to transfer data to your server 1 Gb/s - the current maximum for consumer-grade equipment, it would take 5 1/2 hours (and there is no way you'll ever get close to that speed due to other bottlenecks, i.e. hard drive write speeds). Just as I guess, I would say a realistic time would be 24-36 hours (and that's assuming your network is Gb LAN).
Can I break it down?
The only way to "break it down" is by temporarily moving files off of your client, backing up what's left, then add the other files back and back it up again. (And, at 2.5 TB, I would have to bet a good chunk of that is videos. If you put those in the Videos share on the server, you won't have to back them up at all.)
On a separate note: its going to get more and more common that people will have this amount of data to backup. Hey microsoft! You need to
1) enable failed backups to resume. I know it wont be easy, but if you try really hard you'll find a way
2) give people more info on progress.
3) give people more feedback on where their backup bottlekneck might be
WHS has great potential, very impressive how easy it is to get the basics working, but the devil as always is in the details.
