Internal AFM directories

AFM uses .afm, .ptrash, .pconflicts, and .afm/.afmtrash as internal directories.

AFM uses the following internal directories.
Important: Do not alter or remove any of these directories.
  1. The .afm directory: Present in the cache and the home.

    The mmafmconfig enable command creates this directory in the home cluster. The mmafmconfig disable command removes the directory from home. The .afm directory is created in the cache when you create a fileset, and is valid throughout the lifetime of the cache fileset.

  2. The .ptrash directory: Present in the cache.

    The existing .ptrash directory is applicable to the RO and LU modes.

    For these modes, when a directory along with files or directories is moved to a cache fileset, and the same directory is removed from the home fileset, then the cache fileset directory is moved to the .ptrash directory.

  3. The .pconflicts directory: Present in the cache.
  4. The .afm/.afmtrash directory: Present in the home.

    This directory is created at the home when the mmafmconfig enable command is run, or AFM creates it automatically from the cache after the relationship is initialized. Directories that are conflicting at the home are moved to this cache directory to resume replication successfully.

If an SW or IW mode fileset has deletion conflict for a file, the conflict is resolved by removing the file from the cache and moving it to .ptrash. A conflict occurs when a file in the home is removed but still exists in the cache because the cached version has outstanding changes. A file with outstanding changes in the cache not yet copied to home is called dirty. Files that are moved from the .ptrash or .pconflicts directory by using the mv command are treated as local files to the cache fileset and are not queued to the home. However, if these files are copied, for example, by using the cp command to the cache, they are queued to the home as new files.