ln -s /root/crashplan-docker-synology/S99crashplandocker.sh /usr/local/etc/rc.d/S99crashplandocker.sh.Note: If you don't have git installed, install the ipkg package manager and install it.Install the Docker package via the DSM Package Manager.Stop or uninstall existing CrashPlan instances.Back up your CrashPlan configuration files related to any currently installed instances of CrashPlan, in case you decide to switch back to your previous setup.Docker experience shouldn't be necessary, but can't hurt :)īefore trying to run CrashPlan in a Docker container, it's a good idea to:.You are comfortable connecting to your Synology device using SSH and running terminal commands.Your Synology device supports Docker (check compatibility here).You have a CrashPlan account, a Synology device and some experience using them together.Issues with the 4.4.1 release, I decided to see if Docker would be a smoother way forward. They certainly made it much easier to deal with CrashPlan updates,īut it was still fairly common for me to have issues after new releases. I have been running the PC Load Letter CrashPlan Packagesįor a long time. It has been tested successfully in the following configurations: This is an attempt to get CrashPlan running on a Synology NAS inside a Docker container. I hope that it is useful to the rest of you who are planning your migrations.
Like many of you, I'll be revisiting other backup options that I previously rejected and many new ones that have arisen over the past few years.įernandoMiguel has created an excellent sheet comparing various cloud backup/storage offerings. Still, this leaves a question for those of us currently relying on CrashPlan for Home. Running CrashPlan from a NAS has always been a neglected use case from a support perspective, so this move isn't all that surprising. Existing subscriptions will be honored through October of 2018 (see this announcement for more information). As of 2017-August-22, Code42 no longer offers CrashPlan for Home.
0 kommentar(er)
