Leifgg

I am running (testing…) CrashPlan in an Ubuntu VM and that works fine. You can mount the host filesystem from the VM. Mount points will be different from what you have today so you need to go through the process “Adopting another computer”. It will take some time if you have a lot of data. The only thing I haven’t got working is real time monitoring of the files on the host meaning that CrashPlan only finds new/changed files when doing a full scan that is once per day as default.

The recommended default mapping suggested (not mandatory) from unRAID 6.2 is said to be /mnt/user/appdata/crashplan for as system using User Shares. When you change mappings the Container gets downloaded again with version 4.3.0, that’s why it will go through the auto update again.

I have been using CrashPlan for about 10 months and have experienced the difficulties as well that the last two updates created however it is possible to get a client to run on a Windows PC and connect to the Docker Container. I agree that memory usage is high especially on large backup sets. Recommendation is 1 GB per 1 TB or 1 million files. I would expect that the real-time monitoring of files is what’s causing this. I have not seen any indication of memory leaks on my system. Alternatives is deepening on your needs, is it an offsite storage location or a backup service? I haven’t seen any real alternatives to backup solutions that can run on then unRAID OS or in a container that CrashPlan can. Currently I have installed CrashPlan on an Ubuntu VM on my unRAID system. I have only experimented with it for a week but it looks promising. The setup is not difficult but there are a few tweaks needed to get it up and running.

Never happened to me (heard that one before… ) Suggest checking the log located at your server in log folder at the location where your config is stored. Look for history.log and service.log to start with a see if you can get some hints there. If you see that the version is 4.4.1 that is a good sign. Basically poke around and look for logs with latest time stamps.

Was the server running when you made the changes to my.service.xml? If it was you probably need to restart the CrashPlan container. Then you also need to copy the new files to your PC as well. Have you Disable CrashPlan Backup Service on your PC?

The CrashPlan Desktop container is currently not working, it needs to be updated to version 4.4.1 since it doesn’t update itself as CrashPlan container does. The Windows client is your option at this moment.

It’s probably not as easy as updating the app in the container, the folder mappings inside the container is also likely needed to be updated as well.

Check that the changes in my.service.xml on the server is done. If they are ok leave the CrashPlan Docker running and don’t update it! It must have been able to auto updated 4.4.1 to work. You can check the logs on the server. Check that ui.properties on your PC is ok. Copy the .identity file and the .ui_info file to your PC and change .ui_info file. Reboot your PC and try again...

Guide is in my signature

They provide solutions for individual’s as well. Have a look here: https://www.code42.com/store/ The setup on unRAID is mainly for backing up the server to the CrashPlan cloud, it doesn’t do client backup to the CrashPlan Cloud (at least not directly). Either you do local backup of the clients to the unRAID server and then to the CrashPlan Cloud or have a look on their “Family” subscription.

NTFS is supported, is it mounted? My plan is to do a guide about it in CrashPlan doc as soooon I get some time.

Nothing to do until the maintainer of the Desktop Docker is able to update it latest version and do any changes needed to get it working again.

That’s because the CrashPlan Docker has auto updated itself to 4.4.1 and the CrashPlan Docker Desktop doesn’t.

Since CrashPlan 4.4.1 is now publicly available at their home page I have made an update to the Setup Guide (v1.1) that is linked in my signature. The changes made are only related to the Windows client and how the .ui_info and the .identity files are managed as mentioned in previous posts. But there are still some problems! As long as your CrashPlan Docker is running you will be able to connect with the Windows Client and it will survive a reboot of the PC as well but the .ui_info and the .identity files gets updated as soon as the CrashPlan Docker is restarted making it impossible for the Windows Client to connect again until you manually copy and modify the files. If anybody have some brilliant ideas on how to fix that pls let us know....

Thanks for your feedback guys! The guide will be updated with the latest changes when time permits. My intention is also to include info on how to backup to/from other sources like a USB disk and another unRAID server.

I have been in contact with CrashPlan and they say that 4.4.0 for Windows 64 bit will be available within a week or two.

Updated the both ui_info and ui.properties and still having issues connecting Here's some logs from the docker Crashplan: Thanks for this! Have you been able to find a direct download link for Windows 64 bit version as well?

Many other UPS manufacturers have implemented support for APCUPSD. Have you tried to connect it? There is also the NUT plugin for unRAID http://lime-technology.com/forum/index.php?topic=42375.0 that you could have a look at however I am not sure about UPS sharing over Ethernet yet. Regarding ways to trigger the power down you might check here http://lime-technology.com/forum/index.php?topic=42375.0

The APC UPS daemon available in unRAID already supports sharing UPS over Ethernet. Works as long as you have a UPS that is compatible with APCUPSD.

I have submitted a ticket to CrashPlan support asking for a download link to the Windows version 4.4.0 but no reply yet…

Testing the update right now. Have you been able to find 4.4.0 for download?

CrashPlan has released version 4.4.0 and the CrashPlan Docker will be automatically updated. http://support.code42.com/Release_Notes/CrashPlan_For_Home/4.4.0 It looks like this release is incompatible with version 4.3.0 since the CrashPlan Desktop Docker no longer can connect to the backup engine. It seems be the same for the Windows client. I haven’t been able to locate version 4.4.0 for download on CrashPlan yet. Has anybody else found it?

Dockers should not be affected by the changes from 6.0 to 6.1, only some plugins. Just updated from 6.0.1 to 6.1.2... forced me into an update of crashplan 4.3 from 4.2. Great work here! Thanks. I have the advanced extra paramater in both crashplan and desktop dockers... is this correct? It appears to be working. The extra parameter "--volumes-from CrashPlan" is only needed in the CrashPlan Desktop Docker.

You could install the Docker cAdvisor and see if that works for you. It’s available through the Community Applications plugin. You can read about it here: https://github.com/google/cadvisor and here: http://blog.tutum.co/2014/08/07/using-cadvisor-to-monitor-docker-containers/

You are almost there….! The folder you are looking for is unRaid. That folder is mapped to your folder Q located in the share called Other. So just browse for the unRaid folder in the MakeMKV file dialogue.