Package Details: crashplan-pro 6.9.4-1

Git Clone URL: (read-only)
Package Base: crashplan-pro
Description: An business online/offsite backup solution
Upstream URL:
Keywords: backup crashplan
Licenses: custom
Conflicts: crashplan
Submitter: glittershark
Maintainer: aaronm-cloudtek
Last Packager: aaronm-cloudtek
Votes: 23
Popularity: 0.276589
First Submitted: 2013-08-27 17:10
Last Updated: 2019-04-23 00:42

Pinned Comments

SmashedSqwurl commented on 2018-12-19 15:10

@gadicc, I added some pacman hooks to handle setting/unsetting the immutable flag:

Sets immutable flag after install/upgrade:

Operation = Upgrade
Operation = Install
Type = Package
Target = crashplan-pro

Description = Set immutability of Crashplan Pro upgrade directory
When = PostTransaction
Exec = /usr/bin/bash -c "rm -rf /opt/crashplan/upgrade/*; chattr +i /opt/crashplan/upgrade"`

Unsets immutable flag before upgrade/remove:

Operation = Upgrade
Operation = Remove
Type = Package
Target = crashplan-pro

Description = Undo immutability of Crashplan Pro upgrade directory
When = PreTransaction
Exec = /usr/bin/bash -c "chattr -i /opt/crashplan/upgrade"```

Latest Comments

1 2 3 4 5 6 ... Next › Last »

fishtix commented on 2019-04-22 21:51

Updating a few lines in the PKGBUILD will install the latest version, and I can confirm that it appears to operate properly with Code42/Crashplan servers. Line5: pkgver=6.9.4 Line6: _pkgtimestamp=1525200006694 Line7: _pkgbuild=502 Line20: sha256sums=('4defd4d385b77ab19358d8a811ac4eab17aaf8b5928464121cd8b9e516d07055'

fryfrog commented on 2019-04-17 15:12

@dark-saber, the flag out of date button is perfect for letting them know. :)

dark-saber commented on 2019-04-17 11:38

CrashPlanSmb_6.9.4_1525200006694_502_Linux.tgz is out.

roknir commented on 2019-04-02 13:22

From an email I received from CrashPlan:

Important Product Update

The CrashPlan for Small Business Code42 app is intended to back up your user’s business files (pictures, music, documents, etc.), not your operating system or applications. For this reason, we have always recommended you not include applications or large files in your selection as they may not backup correctly. We have allowed you to back those things up, but beginning in May 2019, we are making some additional changes to our file exclusions and will be disallowing the backup of applications, VM image files, and some backup files.

After this change is applied, you will likely see your file selection and backup archive size go down and benefit from faster restores, syncs, and backups. The new excludes are listed below and a full list of excludes can be found here ( Applications: /Users/<username>/Applications, /Applications/, /Program Files/, /Program Files (x86)/ VM image files: .hdd, .hds, .pvm, .pvs, .vdi, .vfd, .vhd, .vmc, .vmdk, .vmem, .vmsd, .vmsn, .vmss, .vmtm, .vmwarevm, .vmx, .vmxf, .vsv, .nvram, .vud, .xva Backup files: .bck, .bkf Other files: .tmp, .part, .rbf, .tib, .sparseimage

muncrief commented on 2019-03-28 21:01

It just seems unethical to hold data hostage fryfrog, especially for twice the price. But as I said I see that most companies do it now, and it looks like BackBlaze at least demands less ransom than others.

I'll have to think about things for awhile though. Setting and removing the sticky bit isn't that big of a deal, and one of my major concerns is that I have years of backups with CrashPlan, and may have inadvertently or mistakenly deleted data I may need some day. If I move from CrashPlan that data will be gone forever.

Thank you for your suggestions though, as they forced me to look around and see how much the landscape has changed since I last dealt with this issue about 4 years ago.

fryfrog commented on 2019-03-28 20:39

Unless my calculations are way off... it'd be ~$35/mo to maintain 7T of backup and ~$70 to restore that full 7T.

I think Amazon recently announced a much, much cheaper super deep glacier that has a low per month resting cost, but I didn't see how much it was to restore.

muncrief commented on 2019-03-28 20:34

I assume fryfrog and butler360 are addressing me, and thank you for your responses.

I wasn't aware how far CrashPlan had fallen, but if it's that bad I guess I'll have to try and make sure I recover whatever I may need and switch to something else. However I did do a gigantic 3TB restore about 6 months ago, and got back everything but 8GB successfully. I was a bit surprised that the problem was checksum errors on the lost files though.

In any case, the problem is that I have 7TB of data that must be continuously backed up, and I don't know of any other company that can do that economically on Linux. I looked at BackBlaze sometime ago, and again just now, but while their backup prices are only a bit high (~ $35 for 7TB as far as I can tell), their restore prices are actually separate, and astronomical. In fact I think they encroach upon being absolutely predatory. I mean seriously, I didn't even know companies did that, but at least according to the charts BackBlaze provides they're less predatory than others.

So I welcome suggestions for any and all viable alternatives. But if I can't find any I'll just have to turn the sticky bit off and on for now, and hope that, if the community can't find a solution, CrashPlan will fix it sometime in the future.

fryfrog commented on 2019-03-28 20:03

I'm with @butler360, I've migrated away from Crashplan too. I'm using Backblaze's B2 for storage, which has been fine so far. I use Duplicity, but it seems unmaintained and I'd look at other software first.

butler360 commented on 2019-03-28 19:58

Honestly I'd just find another way to do your backups. Crashplan was pretty decent for a number of years, but they've actually 100% lost all of my data on their end before and since transitioning to the SMB plan it's been getting worse and worse.

muncrief commented on 2019-03-28 19:55

By the way, I forgot to mention that I have the same identical problem on both of my computer systems, and reinstalled my main system from scratch just to make sure there wasn't something installation specific about the problem.

CrashPlan also acknowledges that others, even those with supported systems, are experiencing the same problem. However they claim a temporary workaround is to issue a "pause,restart" command in the CrashPlan app. However I tried this and all the ways I could think of to stop and restart CrashPlan and it didn't change anything. The sticky bit has to be removed or restore won't work.