#Crashplan update how to#
#Crashplan update install#
#Crashplan update update#
#Crashplan update upgrade#

Also change the Port and IP address to match your NAS and save the file. ui_info file in a text editor and replace the token in there with the one you have copied from the NAS. Then: cd /var/lib/crashplanĪnd you should get something like this: 4243,bacae745-deaa-4d74-bbaf-7a4c4afd8c35,0.0.0.0 ^^^^ ^^^^^^^^^^^^^^^^^^^^ ^^^^^^^Ĭopy the bit in the middle and go to where you’ve installed the Crashplan client somewhere and find the. Run up Bash on Windows (what, you don’t have bash installed on Windows?) and ssh to the NAS.

#Crashplan update install#

You’ll need to install the client UI on an actual PC so that you can configure the backup service on the NAS. The package for the NAS only installs the backup service on the NAS. And the client UI: which provides you the interface to configure and maintain the backup service. The backup service: which actually does all of the work for backing up files. When you install Crashplan on Windows it actually installs two components. The UI token is needed for the Crashplan client to connect to the backup service running on the NAS.

#Crashplan update upgrade#

This will run the downloaded upgrade from Crashplan manually and shouldn’t run into issues this time.

Not exactly sure what CPIO does but it seems essential to applying the upgrade from Crashplan. Copy CPIO sudo su -Ĭp /var/packages/CrashPlan/target/bin/cpio /bin If you’ve been lazy like me, you’ll need to download one of the previous releases (which requires an oracle login). If you’ve done it on time, it’ll be the latest release.

#Crashplan update update#

I figure it’d be more predictable since patters is going to update his package regularly anyway.Īnyway patters will tell you which version of Java 8 SE runtime to download and provide a link. Turns out I was wrong but I had already switched to the dedicated package. I had hypothesised that the upgrade download was being triggered because the Java package wasn’t found or something. I haven’t fully tested it personally but it seemed it like was working last time I tried. If you’re using Synology’s Java 8 package, you can probably skip this step.

#Crashplan update how to#

OK, detailed steps because sometimes we can’t always remember how to do things exactly. If you remember what you need to do from this, you need read no further. A new UI token will probably be generated and I’ll need to update the VM where I manage the NAS’s instance in order to connect to it again.The upgrade will need to be run manually from the Synology’s shell. After installation, Crashplan will likely download an upgrade and it will fail causing the package to stop running.Java needs to be either installed separately or downloaded separately.There are three main points I need to remember. However, being an unsupported configuration, sometimes updating the instance gets a bit tricky. One of the brilliant members of the Synology user community, namely PC Load Letter (patters), has packaged the Linux version of Crashplan that we may all reap the benefits. Unfortunately, this isn’t exactly a supported configuration for Crashplan. This has the benefit of providing a local backup for all my family’s machines and also a way for me to backup the data on the NAS to Crashplan’s cloud. But enough about that.Īs you may have gathered from the title, I run my Crashplan instance on my Synology NAS. The short is Crashplan is a great choice despite the limited choices I do have. Fortunately, I am lucky enough to live in an area where I can get fibre and the upload speeds really aren’t anything to complain about. Since Australia is more or less known for it’s backwater internet speeds, there isn’t much more you can expect living here. It’s one of the few cloud backup services that actually has a presence in Australia. Even though many people complain about it’s slow upload speeds (mainly in the US). So you may have noticed, I use Crashplan for my backups.