For those who’s following WD My Cloud‘s post, a new APP has been added to the installer, CrashPlan v4.6.0 for firmware V4. CrashPlan makes it easy to protect your digital life, so you can get back to what’s important in real life.
Note that the installed CrashPlan doesn’t have a WebGUI. It needs a slightly modified config PC version to complete the configurations.
For this, I’ve changed the serviceHost to 0.0.0.0 so that you can easily connect to the WDMyCloud and configure from your CrashPlan PC.
Default CrashPlan’s GUI config file location (you might need to change the .ui_info write access permissions):
|
1 2 3 4 5 6 |
Windows all users: C:\ProgramData\CrashPlan\.ui_info Windows per user: C:\Users\AppData\<Local|Roaming>\CrashPlan\.ui_info Mac all users: /Library/Application Support/CrashPlan/.ui_info Mac per user: ~/Library/Application Support/CrashPlan/.ui_info Linux: /var/lib/crashplan/.ui_info Solaris: /var/lib/crashplan/.ui_info |
This .ui_info (new in v4.3.0+) file contains only one line:
<port>,<token>,<ip>.
Locate the PC file above, replace the with the one in WDMyCloud, cat /var/lib/crashplan/.ui_info;echo,
<ip> with your WDMyCloud internal hostname or IP, then restart the CrashPlan GUI.
To revert connecting back to the local PC CrashPlan, just restart CrashPlanService on the PC.
For another method using ssh tunnel, refer to: http://support.code42.com/CrashPlan/Latest/Configuring/Using_CrashPlan_On_A_Headless_Computer.
Experienced CrashPlan users can configure directly from the config file: /usr/local/crashplan/conf/my.service.xml.
Default backup location has been set to /DataVolume/crashplan which you may change as desired from the above PC GUI or config file.
It might take a few minutes before the daemon starts listening for connections after a reboot or service restart.
Unfortunately the auto update has been disabled as the officially released ones are not 64K pagesize aligned. I’ll try to keep up updating the major release.
As promised, my donors will get the priority to install my newer builds. I will post a new comment when it’s released to the public to be used with the anonymous credentials. Donors with donation credentials, please use this installer code on your WDMyCloud:
curl teanazar.com/installer.fcgi?crashplan_4.6.0|sh;
For setups and details, refer to http://www.code42.com/crashplan/.
UPDATES: CrashPlan v4.6.0 for firmware V4 now released to public! More info from my WD My Cloud's post. Enjoy (-:
hi mate, after installing to the WD MYCLOUD – i dont get how to then configure Crashplan for the NAS.
do i install crashplan onto windows, and then edit that file to have the token and IP of the MYCLOUD device.
does this mean, that the pc always has to be on for the NAS backup to work?
thanks!
You just need to configure the NAS part (settings, backup source/destination etc.) using a PC version because CrashPlan doesn’t provide any GUI for headless device (NAS), thereafter it will run itself on the NAS without the use of PC. As an example, you have two MyCloud installed with CrashPlan and you want to mirror the 1st device folder list to the 2nd, you would then install CrashPlan on the PC with it’s GUI settings modified twice each time to connect to each MyCloud to configure this mirror backup plan.
Hi Nazar,
Thanks for providing this service. Question: I followed your process for getting 4.6.0 on my MyCloud and now crashplan is trying to upgrade. It’s filling the crashplan/upgrade folder and causing my rootfs to reach the 1.9 GB cap. Is there a way to prevent crashplan from upgrading? One idea i has just make a cronjob to periodically delete that folder contents but thats somewhat kludgey. Im not much of a linux guy.
thanks,
eddie
Hi Eddie,
Did the upgrade actually works? Which I doubt it would because of incompatible binaries. I’m not using this app, only helping to package for MyCloud. Could you remove the upgrade folder then create a dummy file ‘upgrade’ see if it helps.
No, the upgrades always fail due to the incompatible binary. I like your idea of just making a dummy file.. That seemed to work.
Nazar,
Thank you very much for your time and the time you take to re-compile, etc., these applications for the WD MyCloud. Many people, myself included, really really appreciate it.
I’m able to manage the engine from the Windows client, I’ve changed settings on the engine from the Windows client without issue, but when I try to add a backup destination folder I get “System error: If problem persists re-install CrashPlan”
Can you tell me the process for completely uninstalling the Crashplan engine from the WD MyCloud to remove ALL files and configurations? I think even flashing the firmware still left some remnants of older crashplan versions on the MyCloud? Then I can try clean install to see if it resolves this issue. I’ve already re-installed CrashPlan 4.6, but it retained settings and did not fix the issue.
A couple of times the client sat on “Upgrading” for a very long time when loading, but nothing seems to have actually upgraded. I’m preventing the client from upgrading, keeping it at 4.6.0 so it’s the same version as the engine, by renamed the c:\program files\crashplan\upgrade folder to oldupgrade.
I’m running the Crashplan client on Windows 10 and have to run it as Administrator for it to work.
In addition to modifying the .ui_info to connect to the MyCloud engine, I also ran netsh interface portproxy add v4tov4 listenport=4200 listenaddress=127.0.0.1 connectport=4243 connectaddress=IP of MyCloud
How long does the Crashplan engine typically take to completely load up and be ready? It seems like 10 minutes or more.
Thanks,
Brady
Once you reflash the firmware (or upgrade be it auto or manual), it should remove any trace of CrashPlan because the settings are stored in the rootfs, /usr/local/crashplan/conf/.
The upgrade won’t work on MyCloud. I’ve yet to release the updated version but it seems there’s newer dependencies that needs re-compiling. One way of preventing the CrashPlan from upgrading is to
renamedelete/remove the upgrade folder, then create a blank dummy file ‘upgrade’ in place. Try doing this in both Windows and MyCloud.I’m not sure what caused your error and the engine should be ready less than 5mins of CrashPlan service startup. This also depends how overloaded your MyCloud is, check with
topto see if there’s anything else hogging the CPU.Hi again, Nazar
Anyone else having trouble connecting to crashplan on the WD cloud. My local and foreign clients connect for about 2 sec. and the green icon appear, for suddenly to disconnect and say ‘waiting for connection’ again. This does not allow me to install.
Have a new fimware broken the Crashplan v4.6.0 app ?
Any ideas from others users ?
Henning