There are certain limitations for FSA due to differences in the way Windows and UNIX handle file naming. UNIX is case sensitive and allows two directories or files at the same level with the same name, but differing in case (for example, DIR and dir). Windows is not case sensitive, and maps two such objects to the same object. In this situation, cached data may be incorrect.

In this case, working with members that have the same name, but differ in case can cause potential problems with the member revisions that are selected for the archive. Proxy-side aliases are case sensitive when matched from the client.

For example, problems with member revisions can occur if a file name varies only in case (such as a file named header.c and one named HEADER.C) and information is passed from a UNIX client through a Windows proxy to a UNIX Integrity Lifecycle Manager server.