I'm just trying out CrashPlan
. After using ReadyNAS Vault for a few years at one customer, we have started to have tons of problems with extremely high load averages when ReadyNASVault is running (mostly memory and IO wait), to the point where all the shares on the ReadyNAS become extremely slow or non-responsive. Vault Services has been trying (somewhat, their support effort leaves a lot to be desired) to figure it out for weeks now and cannot (I even gave their developers SSH access to the box). So now I'm looking for an alternative and this looks promising.
One concern I have about allowing the CrashPlan
client to bind to the actual IP of the ReadyNAS is security. I wonder if they recommend doing an SSH tunnel because there is no real security between the CrashPlan
client and the CrashPlan
Daemon. There doesn't appear to be any authentication mechanism and I'm not sure if the traffic between the client and daemon is even encrypted (I'll take a trace and look at it when I have a chance). At least with SSH you have to authenticate and the communication between the CrashPlan
client and daemon is going to be encrypted.
For a home user, this may not be a big concern, but I tend to be pretty paranoid about security
I do have a few additional questions:
1. Do future Radiator updates cause any issues with Java and/or Crashplan
? Do you have to re-install Java and/or Crashplan
after an update? Do you lose your configuration?
2. Any long time performance issues with Java? Seems that Java wouldn't be the most efficient choice for a backup client.
3. How is Crashplan
support? Better than Vault Services?
4. What is the local backup location on the ReadyNAS used for (when you install Crashplan
it asks you to pick a directory this)? Is that if you have other Crashplan
clients backup to the ReadyNAS?
fs1011 wrote:works perfect for me.
However, the crashplan instruction for running the client from PC is really not need. Here is what I did and works perfectly (I did have some help from an IT geek at work:) :
- Access your NAS through SSH and go into the folder where CrashPlan is installed
- Edit (vi) conf/my.service.xml
- There's a line that says ServiceHost. Fill out the IP of your NAS (the one from your LAN like 192.168.1.2)
- Save the file and restart the CrashPlan service
- On your computer (the one you want to control your NAS backups from), look for a file called ui.properties in Program Files/CrashPlan
- Edit the file and uncomment the serviceHost line and modify 127.0.0.1 with the IP of your NAS (for instance 192.168.1.2).
Finally, open CrashPlan.