What Files and Extensions are Excluded from the AXIS CloudSync Process

Overview

As an administrator, you can restrict file types from being synchronized to the server using policy settings. Specifically, the Excluded Extensions policy lists default excluded extensions that can optionally be modified to accommodate the needs of an organization. Using this policy, you can help protect organizations and user accounts from files that might contain malicious code. Other file types, such as temporary and system files and folders, are permanently blocked from the system (hard-coded).

This article will provide information on hard-coded excluded directories and extensions, as well as default excluded extensions that are configurable through policies.

Hard-Coded Excluded Extensions

Temporary Files

Temporary files, which are usually created by applications when saving or editing a file, are hard-coded as excluded extensions. These files include:

Temporary Folders

Temporary folders are also hard-coded as excluded from the sync process. These folders include:

System Files and Folders

System files and folders are also hard-coded as excluded from the sync process.  These system files and folders include:

Folders Excluded from Being Backed Up

AXIS CloudSync allows end users to back up folders that exist on their local machine. Certain folders, however, are excluded from being backed up (these mostly apply to Mac OS X).

Default Excluded Extensions Configurable Through Policy Settings

Administrators can also define additional excluded extensions using policies. The Excluded Extensions policy setting maintains the following list of default excluded extensions; however, these can be modified according to the needs and preferences of the individual organization.

Note: Information displayed in the following table was collected from FileInfo.com. For more information, please reference FileInfo.com.