It looks like you're new here. If you want to get involved, click one of these buttons!
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,
Firstly M4 is just briliant ! Great work Alex, how you get all this done I don't know.
The upgrade went well except now Crashplan is trying to backup everything all again, all .5TB of it. Any ideas how to fix this, I was under the impression Crashplan would recognize the same files ?
Comments
This can still take some time as I think all the hashes have to be recalculated locally (i.e. reading every file in its entirety), but still much faster than a backup to an empty destination.
Edit... Here is my Crashplan Central backup of just over 300GB - still running
since I upgraded to M4 yesterday, but not long to go. The network
connection is throttled at 800 kbit/s, the much faster speed showing is
because it measures this by the size of the files even though only the
hashes are exchanged over the network.
eda, do you use crashplan in conjunction with the server build in backup, or do you have the WHS internal backup disabled? Will crashplan backup to WHS V1?
Thanks
Rufus Roper
Yes it apears after 4 days of what looked like to be backing up it was just checking.
It did use some bandwidth but nowhere near the amount of data. Good job Crashplan (again)
1) I also use WHS Server backup, but just for the C drive. Crashplan doesn't do system image backups (i.e. to restore a system including OS, applications, settings etc), only files.
2) Yes, Crashplan can backup to any system with Crashplan installed, including WHS 2011, WHS v1 (based on Win Server 2003), other versions of Windows, Linux and Mac OS X. The catch on WHS v1 is that UNC paths are not properly supported by Crashplan, and backing up Drive Extender data is not supported via \Shares\ due to concerns about potential data corruption (although no one has reported an actual problem with just reading the data). The workaround I used was here: http://www.mylifewired.com/686/properly-setting-up-crashplan-for-whs/