Skip to main content

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise
CrashPlan for Small Business

Incydr, no.

CrashPlan for Enterprise, yes.

Code42 for Enterprise, yes.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

Other available versions:

Cloud

HOME
GETTING STARTED
RELEASE NOTES
FAQS
SYSTEM STATUS
Code42 Support

Real-time changes not detected due to case sensitivity

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise
CrashPlan for Small Business

Incydr, no.

CrashPlan for Enterprise, yes.

Code42 for Enterprise, yes.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

Other available versions:

Cloud

Overview

Under certain circumstances on Windows, the Code42 app'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, the Code42 app'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

The Code42 app on Windows devices

Considerations

This scenario affects administrators when preparing to deploy the Code42 app to user devices. For example:

  1. You create a Code42 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 Code42 console

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

  1. Sign in to your Code42 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.
  • Was this article helpful?