Incorrect capitalization in the file selection

Overview

When you add directories or files to your organization's backup file selection, the capitalization of file paths and file names in the Code42 console must match the file paths and names on users' devices. If they don't match, those files may be removed from the backup.

This article describes problems that can arise from using incorrect capitalization in file paths and names, and how to avoid the problem.

Problems with incorrect capitalization

If you use incorrect capitalization when entering a file selection, you may encounter the following problems:

You enter incorrect capitalization of a directory, and find that older versions of the files under that directory are not retained.
You enter incorrect capitalization of a file name, and find that older versions of the file are not retained.

If you enter a file path with incorrect capitalization, older versions of the files in the original path are pruned from the archive when archive maintenance runs. The pruned files cannot be restored to the archive.

Operating system differences

If you have directories or files on your device whose names are identical except for capitalization, the Code42 agent handles them differently depending on your operating system.

Windows and Mac

Windows and Mac are not case-sensitive file systems by default, and therefore the Code42 agent does not recognize directories or file names that differ only in capitalization as being distinct. On a Windows or Mac device, if you select two files for backup whose names differ only in casing, only one of the backed up files can be downloaded.

Linux

Linux is a case-sensitive file system, meaning it treats directories and files with different capitalization as distinct, even if they are otherwise spelled the same. The Code42 agent obeys Linux case-sensitivity rules in that it recognizes separate directories that differ only in capitalization, and it backs up separate files that differ only in capitalization. On Linux devices you can download backed up files that differ only in capitalization as separate files.

Recommended solution

To avoid problems with case-sensitivity and incorrect capitalization, do not create directories or files whose names differ only in capitalization, whether you have Windows, Mac, or Linux devices. To correct problems with capitalization, follow the steps below.

Change the file selection from the Code42 console

Before archive maintenance runs, use the Code42 console to correct the file selection. If files are pruned during archive maintenance, they cannot be restored to the archive.

Sign in to your Code42 console.
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.
Test that files are backing up correctly.
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.

Search