---
title: "Transfer Modes"
slug: "guide/configuration/server-start-up-file/global-file-cache/transfer-modes"
sidebar:
  order: 42
---

<a id="ref-e279eea27f8f"></a>
<a id="ref-da6115b456cc"></a>

## Synopsis

`egr.eai.fscache.transfer_modes=<list-of-transfer-modes>`

**Default Value:** `copy`

The value of this option must be a possibly empty, comma-separated list of `copy`, `symlink`, `hardlink` and `link`, with `link` being a shortcut for both `symlink` and `hardlink`.

The option lists the transfer modes considered for use by the Online Configurator whenever a file must be transferred between the cache and a sessions working directory.

The `copy` mode is always considered, whether or not it is listed by this option.

If the use of extended attributes is disabled (see §[Use of Extended Attributes](/pCon/configuratorOnline/specs/guide/configuration/server-start-up-file/global-file-cache/use-of-extended-attributes#ref-9705b525ad31)), the link transfer modes are not considered, even if they are listed by this option.

From the list of configured transfer modes, the cache selects the transfer mode it deems best for the operation in question. It does not, however, consider the capabilities of the underlying operating system or file system. In particular, if the file cache and the session cache are stored on different file systems, the `hardlink` mode must not be used.

From a performance point-of-view, `hardlink` is the most efficient, shortly followed by `symlink`. The `copy` mode is the least efficient, as in addition to the metadata operations necessary to write or update the directory and i-node, it also requires the complete file data to be read and written, which may be quite resource consuming, especially for large files.
