- May 2, 2017 at 12:50 #996
Is anyone successfully running Crashplan on QTS 4.3.3? Can you share your experience?
I use the Crashplan app provided by the QNAP store. I would like to update to the latest QTS version (4.3.3), but I’m not sure if the app will run on the 64 bit system. I tried using QNAP’s compatibility tool to check it, but I can’t seem to get the tool to run on my system.
Any tips/ideas will be appreciatedMay 2, 2017 at 20:14 #1008
I can’t say for sure, but that version is mentioned on dynek/crashplan-qpkg changelog on github:
sorry ARM users, no more support. rejoice x86 users, QTS 4.3.3 enable…
I’ve caught your post on Qnap’s forums, but more importantly dynek (the package author) exchanging some info on another topic as well, that you might have missed:
The topic is mostly about CrashPlan 4.8.0_45 not working with QTS 4.3.3.AdvertisementMay 4, 2017 at 10:49 #1028
Just for reference of other visitors, I saw there a suggestion (from user alexyeung) that may help, that refers to virtualize CrashPlan using Docker, just like it can be done on a Synology NAS:
dynek has done great work developing a qpkg for Crashplan. The downside, is that whenever Crashplan pushes an update, the app stops working until dynek can fix it (QNAP Forum Thread).
The alternative is to run Crashplan within a Container Station virtual docker. With this solution, Crashplan works normally even after updates:
Setup CrashPlan on QNAP using Docker virtualisationMay 4, 2017 at 11:53 #1033
Thanks! I’ll try both methods to see which works best for me.May 4, 2017 at 12:02 #1034
Thanks! I’ll try both methods to see which works best for me.
No problem! One other thing I remembered is that you can also try to block the auto-upgrade procedure entirely, just like we do it on Synology NAS‘, you’ll just need to consider that the folder locations are different (here’s a reference of these folders, including for QNAP).
So in theory, if you are able to install the package created by dynek you should be able to block the upgrade process right after installation and before it runs (i.e. because after running it will try to start the upgrade process).
These commands should work (if the folder location is correct):
cd /share/MD0_DATA/.qpkg/CrashPlan sudo mv upgrade upgrade.tmp sudo touch upgrade sudo chmod 444 upgrade
I don’t know if it’s necessary to ‘sudo‘ but it won’t hurt.
If you do try this and it works do report back!
- You must be logged in to reply to this topic.