We can't live with that as our fireproof solution. So basically if we encountered a serious problem (data is on raidz2 + going to a nearline raidz2) then we'd be a week or more without data. Tech said that it'd be about a 3 day turn around on hard drives, and more considering the size of our backup. I thought since they had offices in the bay area that they would have a data center close to me and that backup speeds would be decent as well as response time in an emergency. They also claim not to throttle, but the best I could manage is roughly 8.5Mbps sustained, which their tech on the phone was impressed by. One is in Milwaukee and the other in Atlanta. Looks like they only have TWO data centers. Update: So after all that I think we're moving away from crashplan. The second file also contains a line with orgtype that will need to be changed to "BUSINESS" as wellĪs above, find the line with "authority" and change the address to contain "pro" at the end of crashplan.Īfter those changes, I restarted my jail, and my GUI app connected instantly and had ZERO problems connecting to the crashplan server and saw my storage on my jail just fine. In the first file there's one line that says "orgtype" and the variable needs to be "BUSINESS"Ĭouple lines down where it says "authority" the address needs to be changed from ":443" to :443" usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml usr/pbi/crashplan-amd64/share/crashplan/conf/ The two files that need to be modified are: So what's happening is that the gui app that's tunneling is talking to a service that has some xml files that's pointing it to the WRONG address in order for your account to validate with your PRO account. (the following is assuming you have a CrashplanPRO account) I got it working, and indeed, the standard free version has some code differences.
0 Comments
Leave a Reply. |