CrashPlan crashing (itself) and the host machines
We run CrashPlan for Business (PRO) on several Windows servers and wanted share some of the observations about the local app and the service itself.
Pricing is straight forward: it is a flat rate for unlimited data backup. $10/m per machine is dirt cheap. Additionally, the CP client app allows you to back up your data to the CrashPlan cloud but also to the other computer or folders (at no additional free).
CP uses Blowfish for encrypting your backed data and it’s a client-side encryption. There’s an ability to reset the encryption password through a security question.
CrashPlan, support versioning and it’s enabled by default.
Crashplan utilizes a sophisticated delta-update algorithm along with automatic compression. Which means that CP splits your files into small data chunks. Then each chunk is compressed and encrypted accordingly to your settings. It also supports de-duplication, which means that duplicated files are only uploaded to the backup server only once. This also means that of you move / rename files CP does not need to upload it all over again.
The bad & the ugly
On numerous occasions throughout the 2016 Crash Plan updates seemed to have failed crippling the CP instance on many servers. Just last in July we had a situation with two instances of the CP PRO installed and running on the Windows 2012 R2 server. After having removed on from Programs and Features it ran for a few week and it had crashed completely.
Attempting to start the CP service failed so we resorted to “the usual” (recommended by very scarce tech support): download the most recent version,reinstall it and reboot…
Strangely we’ve found that some machines were running two instances of Crash Plan; apparently one 64-bit and the other 32-bit version.
My understanding is that you may encounter VSS issues if the version of your operating system and the CrashPlan app are not compatible. i.e. if you are running 32-bit version of the CrashPlan app a 64-bit version of Windows and vice versa. One would think that there should be some kind of mechanism preventing installing two instances of the same app on the system?
One of the common events logged by Windows running CP Pro is Event ID: 1000
Log Name: Application
Source: Application Error
Date: 8/8/2016 11:20:03 AM
Event ID: 1000
Task Category: (100)
Faulting application name: CrashPlanTray.exe, version: 184.108.40.206, time stamp: 0x562691e6
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18264, time stamp: 0x56e1b34d
Exception code: 0xe06d7363
Fault offset: 0x00015b68
Faulting process id: 0x7578
Faulting application start time: 0x01d1f176c7beec96
Faulting application path: E:\Program Files\CrashPlan\CrashPlanTray.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 93b2b2e0-5d7b-11e6-8106-bc764e20acd9
Faulting package full name:
Faulting package-relative application ID:
<Provider Name=”Application Error” />
<TimeCreated SystemTime=”2016-08-08T15:20:03.000000000Z” />
While we haven’t discovered a common thread or found a permanent fix yet, reinstalling the program appears to work in a short run.
As much as Code42 markets its product’s simplicity and ease of use, it looks like it still needs a lot of TLC.