Skip to main content

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, yes.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to version 5.

Other available versions:

Cloud | Version 6 | Version 4Link: What version am I on?

Code42 Support

Real-time changes not detected due to case sensitivity

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to version 5.

Other available versions:

Cloud | Version 6 | Version 4Link: What version am I on?

Overview

Under certain circumstances on Windows, CrashPlan's real-time file watcher does not identify changed files in your backup selection if files are removed and then re-added in a different case. However, CrashPlan's daily scan will still back up the entire file selection once per day, regardless of case.

For a similar issue at a user level, see Case Sensitivity And Real-Time Backup.

Affects

CrashPlan for Small Business (previously CrashPlan PRO) and Code42 CrashPlan (previously CrashPlan PROe) on Windows

Considerations

This scenario affects administrators when preparing a CrashPlan for Small Business or Code42 CrashPlan deployment. For example:

  1. You create a CrashPlan configuration to back up a specific folder, such as C:/Example_Folder
  2. You deploy your users' devices according to an image that includes that folder in a different case, such as C:/example_folder
  3. The real-time file watcher does not monitor the actual folder on the user's device

Recommended solutions

Change the file selection from the administration console

You can use the administration console to correct the file selection.

  1. Sign in to your administration console.
  2. Add the correct file path to the include filters for a device or organization, or your entire Code42 environment.
    The scope of this step depends on the scope of the incorrect file path in your Code42 environment.
  3. Test that files are backing up correctly.
  4. If applicable, remove the incorrect file path from the include filters for a device or organization, or your entire Code42 environment.
    The scope of this step depends on the scope of the incorrect file path in your Code42 environment.