Online Backup Pricing Cloud Backup Pricing CrashPlan. Just $10 USD per month per computer. We want to help your business as much as possible during this crisis. So we are offering a free 30-day trial. No strings attached and you can cancel anytime. No cost to install. Easy file protection.
When you install CrashPlan on a second computer, you will have the option to “Adopt” your former computer. This will allow you to use the previous machine’s archive, backup file selection and backup settings. It will also deactivate the previous computer so that no.
The monthly cost is very reasonable and worth every penny.”. Karyn B., Outsourced IT Professional. Get started with a free trial of CrashPlan today. Just $10 USD per month for each computer after your free trial. No cost to install. Easy file protection. No cost to restore files. Dedicated Support.
CrashPlan for Small Business New Interface. Our desktop client upgraded to the Version 6 Code42 app. The new CrashPlan for Small Business delivers an improved user interface that makes backup and recovery easier and more intuitive. The release started November 28, 2017 and is available to all customers and trial users.

What is contained in my archive?

The CrashPlan app divides the backup into several files at the destination and builds archives containing the following information:

Here is a step by step guide to install Crashplan on a NAS or headless Linux based server, and then get it all setup for your liking. The instructions will be very similar for most Linux / NAS variations. I just went through this process on my home NAS, which runs OpenMediaVault. I’m going to assume you are using a Windows client to manage.

Archive File	Contents
GUID file	A file named for the 18 digit GUID for your system
Archive properties status file	Lists the current properties of the archive, including: size, last completed, next backup, and last archive maintenance.
Data containment folder	Contains the encrypted data from your backup and a manifest of all blocks of data backed up in your archive.
File to-do queue	Index of files remaining to be backed up.
The file scan status	Information on the last time the file selection was scanned. If CrashPlan is currently scanning, current progress is stored.
File manifest	Index of file information for all selected files.
Block manifest	Index of block information for all selected files.
File version history data	File and block information for all previous versions of the selected files.
Backup retention policy	Information regarding frequency and versions settings for your backup.
Transaction log	A log of operations that happened on the archive.

I like CrashPlan. They support a wider range of operating systems than some of their competitors, they have a simple pricing model, unlimited storage & retention, and a nice local, mobile, and web interfaces. I’ve been a customer for a few years now, and recently have switched a few of my clients’ businesses over to them, too.

What I don’t like is that they don’t seem to support Linux very well, which is typical of companies when their installed base is mostly Windows & Mac. Most notably, their install instructions are sparse and they don’t tell you what packages you need to have installed, which is important because cloud VMs and whatnot are usually “minimal” installations. I’ve attempted to open a support case, but they suggested running a “headless” client, which is both unsupported and a huge pain. And then they closed the support case, because it’s unsupported! DOH.

So here’s how I get CrashPlan installed on Linux in case it helps others, and maybe Code42 themselves.

Parameters:

As of this writing the CrashPlan software is version 3.7.0.
I am doing this on Red Hat Enterprise Linux, CentOS, and Oracle Enterprise Linux 5, 6, and 7 servers.
These servers have outbound access to the Internet.
I am using a Windows 7 desktop.
This document assumes you’ve done some things with Linux before.
This document assumes you’re logging in as yourself and then using sudo to run things as root.
Your mileage may vary, and my ability to help you is limited. I don’t work for Code42. That said, if you can improve this document please let me know how.

1. Your Linux server has to have a few packages on it to enable basic X Windows support for the CrashPlan GUI. Most cloud servers are built with a minimal installation and don’t have these. On Enterprise Linux variants you can issue the command:

This will get you xterm, so you can test the setup, xauth which is part of the X Windows authentication setup, and the fonts the client will need. It also grabs wget, which the CrashPlan installer will use to retrieve a copy of the Java Runtime Environment.

2. You need to forward X Windows (X11) graphics to your desktop. To do this you need what’s called an X Server, and you need an SSH client that can forward X11 packets. Given that you did #1 already you probably have SSH. I’m on Windows, so I use:

Xming — http://sourceforge.net/projects/xming/ — the X Server you need

PuTTY — http://www.chiark.greenend.org.uk/~sgtatham/putty/ — a free SSH client

I actually use Van Dyke’s SecureCRT — http://www.vandyke.com/products/securecrt/ — but it’s a commercial product. IMO, totally worth it if you spend a lot of time logged into UNIX hosts, though. Both it and PuTTY can forward X11.

Install these things. Run Xming (not Xlaunch, etc.) and your SSH client of choice. Xming may trigger a firewalling prompt under Windows. The X Windows data will be coming across the SSH connection you’re about to establish, so you shouldn’t need to open anything up.

3. Set up a new SSH connection, or edit an existing one, and tell it to Enable X11 Forwarding. Here’s where the X11 option is in PuTTY:

Open that connection.

4. Run ‘xterm’:

You should see:

If you get this error on the console:

Check to make sure Xming is running. If you get:

Forwarding isn’t working when you logged in. Check your settings, and check to make sure that xauth and xterm got installed correctly. If you’re ssh’ing from a command line, like on a Mac or through a second server you might need:

5. Close xterm – you can either type ‘exit’ like in a normal shell or just close the window like a normal window. That was just to check to make sure forwarding was working.

6. Put the CrashPlan installer on the Linux server. My favorite way to do this is to copy the direct download link from CrashPlan and paste it into wget, but you can use sftp, scp, Zmodem[0], whatever.

Then expand it:

7. Run the installer as root. The CrashPlan service needs to run as root if you want it to back up the whole system, and the installer will want to put startup files in the right spots so CrashPlan starts after a reboot. This is a good idea.

8. Answer questions, read the EULA. You can get out of the EULA by hitting ‘q’. I let it put everything in the default locations.

9. Let it start the CrashPlanDesktop app. In a few moments you should see the GUI pop up. Log in, do your thing. You will likely have to adjust what it’s backing up if you want it to get system files and such. Be careful, though, because it’ll back up things that change, and a lot of system files change a lot. You might want to consider lowering the backup frequency in that case.

Crashplan For Home Download

10. If the CrashPlan GUI didn’t start you can try running it manually:

Crashplan Server Address

If you get errors about permissions check your forwarding again (run xterm). If you’re trying to run it with sudo you might be getting permission errors. X Windows has some authentication in it so people can’t just pop windows open on your desktop. You can give root permission, though, by copying your .Xauthority file to ro

How To Install Crashplan Free Trial