StephenB wrote:Very helpful! I was able to get this running fairly quickly thanks to your detailed step by step.
One detail (post install) - the Crashplan client will show your shares twice - as links (with an arrow as part of the icon) and under the "C" folder. It won't back up the links, you need to select the folders under the "C" folder. If you try the other way, the backup "succeeds", but doesn't back anything up.
demusss wrote:Does it backup files on the NAS to Crashplans servers? Or enable to backup files from local PCs and friends to the NAS?
RedDeath wrote:Great guide!!!
Thank you very much for this!
* Install RootSSH Add-on
* SSH as root
* run: Apt-get update
* run: apt-get install nano (viewtopic.php?f=36&t=42794)
* echo deb http://archive.debian.org/debian-backports etch-backports main non-free >> /etc/apt/sources.list
* (additional info comes from: viewtopic.php?f=61&t=18139&hilit=CrashPlan&start=30)
* run: apt-get update
* run: dpkg-reconfigure debconf and select the "Dialog" option (1) and "Medium" prompt level (3) This is necessary so that the sun JRE license agreement can be displayed and accepted
* run: apt-get install sun-java6-jre
* run: dpkg-reconfigure debconf and select the "Dialog" option (1) and "Noninteractive" and "High" prompt level (3)
* run: wget http://download.crashplan.com/installs/ ... _Linux.tgz
* run: tar -xvf CrashPlan_3.2.1_Linux.tgz
* run: cd CrashPlan-install
* run: ./install.sh
* Choose the following settings:
Do you accept and agree to be bound by the EULA? (yes/no) yes
What directory do you wish to install CrashPlan to? [/usr/local/crashplan]
/usr/local/crashplan does not exist. Create /usr/local/crashplan? (y/n) [y]
What directory do you wish to link the CrashPlan executable to? [/usr/local/bin]
What directory do you wish to store backups in? [/usr/local/var/crashplan] /c/backup/crashplan-local
What directory contains your SYSV init scripts? [/etc/init.d]
What directory contains your runlevel init links? [/etc/rc2.d]
CrashPlan will install to: /usr/local/crashplan
And put links to binaries in: /usr/local/bin
And store datas in: /c/backup/crashplan-local
Your init.d dir is: /etc/init.d
Your current runlevel directory is: /etc/rc2.d
Is this correct? (y/n) [y] y
Unpacking /./CrashPlan_3.2.1.cpi ...
Starting CrashPlan Engine ... Using standard startup
CrashPlan has been installed and the Service has been started automatically.
Press Enter to complete installation.
* run: nano /usr/local/crashplan/conf/my.service.xml
* On the line that says ServiceHost. Replace 127.0.0.1 with IP of the NAS (the one from your LAN like 192.168.1.100) and then save the file and exit nano
* run: /usr/local/crashplan/bin/CrashPlanEngine restart
* On your computer (the one you want to control your NAS backups from), look for a file called ui.properties in c:\Program Files\CrashPlan\conf
* Edit the file and uncomment (delete the #) the serviceHost line and replace 127.0.0.1 with the IP of your NAS (for instance 192.168.1.100).
* Start Crashplan client on your computer and login
* In Crashplan, go to Destinations and click select. Choose "backup/crashplan/crashplan-local"
* Go to Settings -> "Inbound from other computers" and click Configure
* Note Backup code to use for friends and other computers
* Change "Default backup archive location" to /c/backup/crashplan-inbound (note this folder must be created ahead of time)
* Remove WAN speed throttling
* Enable Backup Sets
* Create a System Files Set (to crashplan central and crashplan-local (folder)) and a Media Set (for /c/media)
Additional helpful links:
* http://linuxhints.blogspot.com/2011/02/ ... dless.html
* http://innerfusion.tumblr.com/post/6168 ... in-7-steps
I have reviewed your logs and I have a few questions about the hardware that CrashPlan is running on. They appear to be NAS devices themselves, they are running a Netgear Linux Kernel for ReadyNAS. Running CrashPlan directly on a NAS device is an unsupported configuration and I would not be able to assist in troubleshooting anything caused by running CrashPlan in an unsupported way. However, I can tell you that the set of logs from the machine named "NAS-Home-2" indicate that there are too many open files.
Every operating system imposes a limit on the number of "files" a process may have open at any one time. More accurately, the OS imposes a limit on the number of file descriptors a process may have open at any one time, but for our purposes the difference isn't significant. CrashPlan will occasionally bump up against these limits; it's not common by any means but we do see it sometimes for very large archives (i.e. archives with lots of files).
Linux defines both a system-wide and a per-process limit on the number of open files a process can open. It's best to always begin with the per-process limit for two reasons:
Changing this value instead of the system-wide value minimizes the impact on the rest of the system
It's likely to be the lesser value anyway
You can use the "ulimit" command (actually a shell builtin on most platforms now) to get the limit for this process on the number of open files:
This value can be set using a variation on the above command:
ulimit -n 4096
On rare occasions you may find yourself increasing this limit to a value that exceeds the system-wide limits. When this occurs the only option available is to modify the system-wide values. This should be a fairly rare occurence but if it does come up the following commands should prove helpful.
You can view the current system-wide limit using the proc file system:
This value can be set for the current system by writing to the same file:
echo "4096" > /proc/sys/fs/file-max
Note that modifying the proc file system will not cause the change to be preserved across restarts. In order to make this change permanent you'll need to modify /etc/sysctl.conf.
Open /etc/sysctl.conf (you'll need to be root)
Edit (or add if not present) the "fs.file-max" parameter
Save the file and exit
Note that editing this file will not bring about a change in the running system. To do this you'll need to re-apply all the settings defined in /etc/systctl.conf (including the changes you just made). The following command will do it:
sysctl -p /etc/sysctl.conf
The above instructions are for a normal Linux distro and not a custom built one like the Netgear Linux distro but it should work for you.
Users browsing this forum: No registered users and 0 guests