CrashPlan for Remote Backups

  • Posted June 3, 2013

Does anyone use (or have used) CrashPlan on their DigitalOcean droplets for remote backups? I’m looking into it and am interested in learning whether anyone recommends against; has best practices to share; or has better alternatives to recommend?


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Thanks for your insight @ryan! In light of your explanation, I elected to follow your advice re: rsync.

ampsonic – Totally right. dumb copy-paste error. :\

Hi Ryan, I think your 2nd link is incorrect (duplicate of first link.) Not sure, but maybe you meant to post this?

Hi! I work for Code 42, makers of CrashPlan, and unfortunately I don’t have any personal experience with Droplets directly. In looking through the support documentation and comparing to other similar situations, I would say that while it might be possible to install the CrashPlan client on a droplet, the additional cost of running it alongside your application would likely be significant. <br> <br>CrashPlan uses a decent amount of RAM to monitor the files in your backup selection and back them up automatically. While this amount is small compared to today’s Desktops and Laptops (or even a dedicated server), for a cloud service like Digital Ocean, it could easily push you into a higher pricing bracket and/or reduce the performance of your application. <br> <br>If you wanted to back up using CrashPlan, it’d probably be better to set up a regular rsync process to send back to your computer, then use CrashPlan on that computer to send the backups offsite. DigitalOcean has provided instructions on configuring rsync here: <br> <br> <br> <br>If you did want to experiment with CrashPlan on a Droplet, you’d want to use our unsupported instructions for headless installation and initial configuration. These are here: <br> <br>