Install Crashplan directly to Linux alongside UnraidĬons: Same as above with additional concern that I could break an Unraid dependency or that an Unraid upgrade could break Crashplan. As I stated above, I REALLY don’t want to start over with my backup. Run Crashplan as a Docker container in UnraidĬons: Not sure Dockerized Crashplan app is officially supported (?), Worried about migrating CP backup set from Windows filesystem to Linux filesystem.

Pros: fairly straightforward to map the same drive letters and adopt the existing backup setĬons: Overhead of a running in a VM, resources will be constrained compared to bare metal installation Run Crashplan in a windows VM under Unraid, backing up the NAS folders as mounted drives Pros: this is basically how I’m running todayĬons: the Windows machine has to be on for backups to occur, and all of the data has to make a round trip through the Windows machine for NAS to NAS local backups.

I’m considering several options:Ĭontinue running Crashplan on the Windows machine, backing up the NAS folders as mounted drives. I haven’t decided what I should do to maintain my crashplan backups. My upstream internet bandwidth is 20Mbps and my CP archive is about 6TB, so moving to a competing service would be fairly painful. the parity-protected array writes are the bottleneck. My new Unraid NAS has 20 cores, 128GB of RAM and a dedicated 10GbE connection to my Windows machine, so beefy VMs are possible and network file transfers are not a bottleneck. I am migrating from a Windows 10 machine with a bunch of USB HDD’s and Crashplan for local + cloud backups

Crashplan synology docker