#CRASHPLAN NAS SYNOLOGY PDF#
#CRASHPLAN NAS SYNOLOGY INSTALL#
#CRASHPLAN NAS SYNOLOGY UPDATE#
#CRASHPLAN NAS SYNOLOGY WINDOWS 10#

some of the Finder comments I set, and the PDF reader Skim stores annotations in extended attributes). This may or may not be important to you, but metadata can contain what I consider data (e.g. If you’re not willing to consider Arq Backup and are only choosing between CrashPlan and Backblaze, a few things to keep in mind (not trying to be overly negative, these are just the things that have stopped me from using Backblaze – they might not matter to you):īackblaze discards a lot of metadata when it backs up files. But the recent email about limiting deleted files to 90 days made it easy, so I’ve finally cancelled!

Seems highly unlikely at this point (and given I had a pretty recent local backup that I restored from at the time), but CrashPlan had many years’ worth of deleted files, so I couldn’t bring myself to cancel it. My internal SSD failed 2+ years ago (before I started using Arq), and part of me was worried that I might still come across some file that I’d failed to recover properly. However, I hadn’t cancelled my CrashPlan subscription. (You can also use the Arq software to backup to other cloud storage that you pay for separately if preferred.) You simply pay for the amount of backup storage space you need, and it’s reasonably priced.

Arq Backup is great – it backs up whatever files you ask it to, includes all metadata (even old Mac bits like resource forks) and keeps them for as long as you want (whether they are on internal or removal media). Would highly recommend you look into setting something like this up as it will run way more natively on the NAS, especially in conjunction with way more full-featured backup apps like duplicacy or borg.I started moved my cloud backup to Arq Backup after the previous change CrashPlan made to file excursions. The prevailing expectation with cloud storage providers appears to be that you use B2 or some such to store your backups (Google Workspace may be a fixed price option too). All of these together led me to close out my CP sub after 10+ years.

#CRASHPLAN NAS SYNOLOGY UPDATE#

On top of which - they have been promising an update to that Java app ever since they upped their prices, which does not look like it’s happening. This is completely unacceptable to me for a backup. Also a number of recent threads with horror stories of restoring from CP (search for them): lost/corrupted data, archives inexplicably and irrevocably unavailable in a disaster recovery scenario etc. One thing to keep in mind is that CP is clearly cracking down on this use-case and keeps closing off ways in which people have been running their app on NAS boxes. The VM approach would be a feasible solution on the face of it, though the docker image has been kept well up to date in my past experience. Mount the desired NAS shares on the virtual machine (this will make the shares available to the virtual machine's file system).Ĭonfigure CrashPlan to create offsite backups of the mounted shares.Ĭould this be a feasible solution to the problem described above?

#CRASHPLAN NAS SYNOLOGY INSTALL#

Install CrashPlan on the virtual machine.

#CRASHPLAN NAS SYNOLOGY WINDOWS 10#

Install a Windows 10 or Ubuntu virtual machine on the NAS using the Virtual Machine Manager.Īllocate a sufficient amount of RAM to the virtual machine (CrashPlan is based on Java and eats up a lot of RAM). Should we circumvent this problem by following the steps below?

IMHO, it looks like a makeshift solution that may stop working if the developer decides to abandon the project. The following Docker solution, which seems to be maintained by only one person, appears to be the only one that works currently: The problem, however, is that CrashPlan is nowhere to be found in the Package Center on DSM v6.2.3 even if you set the trust level to 'any publisher'.Ī compatible version of CrashPlan used to be available at, which is a community source, but the package no longer works properly. Currently, we use CrashPlan as our online backup and file hosting service. We have a Synology NAS with a whopping 64 GB of RAM, and we'd like to dedicate the NAS to handling all offsite backups. I've already asked this elsewhere, but for good measure, I'm posting it here too.

Crashplan nas synology