> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Offline Cache Size Parameter

> Configure how much local disk space a Syteca Client can use to cache monitoring data while disconnected from the Application Server.

<Note>
  Applies to Windows, macOS, and Linux Clients. The parameter and its default value are identical across all three; only the configuration path and the underlying cache file differ.
</Note>

If a Client loses its connection to the Application Server, it doesn't discard monitoring data - it writes it to a local cache on disk and sends the cached data automatically as soon as the connection is restored. The **offline cache size** parameter controls how much disk space that local cache is allowed to use.

## Configure the offline cache size

<Steps>
  <Step title="Open the Client or Client Group settings">
    On the **Editing Client** or **Editing Client Group** page, select the **Monitoring (Windows/macOS)** tab.
  </Step>

  <Step title="Set the cache size">
    In the **Advanced Options** section at the bottom, set the **Offline cache size (MB)** value. The default is **500 MB**.
  </Step>
</Steps>

<Frame caption="The Offline cache size (MB) field in the Advanced Options section of the Monitoring tab.">
  <img src="https://mintcdn.com/syteca/0FlD-vkHsBA1azVX/images/administration/clients/parameters/offline-cache-size-advanced-options.png?fit=max&auto=format&n=0FlD-vkHsBA1azVX&q=85&s=73ac05c86f280c6ddedffd97e073c44a" alt="Advanced Options section showing the Offline cache size MB field" width="1900" height="1070" data-path="images/administration/clients/parameters/offline-cache-size-advanced-options.png" />
</Frame>

When the amount of cached monitoring data on the Client computer reaches this limit, the Client stops writing further data to the offline cache until connectivity is restored and the cache is sent.

<Tip>
  Keep the offline cache size at 500 MB or higher. A smaller cache risks data loss during longer outages, since the Client can't buffer more than the configured limit.
</Tip>

## Where the cache is stored

<Tabs>
  <Tab title="Windows">
    Cached data is written to a file named `TempWrite.dat` inside the Windows Client's installation folder.
  </Tab>

  <Tab title="macOS">
    Cached data is written to the macOS Client's local cache in its installation folder.
  </Tab>

  <Tab title="Linux">
    Cached data is written to three files in `/var/.ekran/internal/`:

    * `EkranOfflinePool.dat`
    * `EkranOfflinePool.dat-shm`
    * `EkranOfflinePool.dat-wal`
  </Tab>
</Tabs>

## Move the Linux offline cache to another location

<Warning>
  **NOT AVAILABLE IN SAAS.**
</Warning>

On Linux, the offline cache files can be relocated to a non-default folder (for example, a NAS mount or another drive) by moving them and replacing them with soft links.

<Steps>
  <Step title="Unassign the Client's license">
    On the **Clients** page, unassign the license from the Linux Client to confirm it has no active (**Live**) sessions.
  </Step>

  <Step title="Stop the Client services">
    ```bash theme={"system"}
    sudo systemctl stop Ekran
    sudo systemctl status Ekran
    ```

    The second command confirms the service has stopped.
  </Step>

  <Step title="Stop the offline pool manager service">
    ```bash theme={"system"}
    sudo systemctl stop offlinePoolManager
    sudo systemctl status offlinePoolManager
    ```
  </Step>

  <Step title="Locate the cache files">
    Open `/var/.ekran/internal/`, where `EkranOfflinePool.dat`, `EkranOfflinePool.dat-shm`, and `EkranOfflinePool.dat-wal` are located.
  </Step>

  <Step title="Move the files">
    ```bash theme={"system"}
    sudo mv EkranOfflinePool.dat* /<name_of_folder>/
    ```
  </Step>

  <Step title="Create soft links back to the original location">
    ```bash theme={"system"}
    ln -sri EkranOfflinePool.dat /var/.ekran/internal/EkranOfflinePool.dat
    ln -sri EkranOfflinePool.dat-shm /var/.ekran/internal/EkranOfflinePool.dat-shm
    ln -sri EkranOfflinePool.dat-wal /var/.ekran/internal/EkranOfflinePool.dat-wal
    ```

    <Note>
      In some cases the files' owner needs to be changed to `root`:

      ```bash theme={"system"}
      chown -h root:root EkranOfflinePool.dat*
      ```
    </Note>
  </Step>

  <Step title="Restart the services">
    ```bash theme={"system"}
    sudo systemctl start Ekran
    sudo systemctl start offlinePoolManager
    ```
  </Step>

  <Step title="Reassign the Client's license">
    On the **Clients** page, reassign the license to the Linux Client.
  </Step>
</Steps>

## Related

<CardGroup cols={2}>
  <Card title="Windows Clients" icon="windows" href="/docs/administration/clients/windows">
    Client configuration parameters for Windows.
  </Card>

  <Card title="Linux Clients" icon="terminal" href="/docs/administration/clients/linux">
    Client configuration parameters for Linux.
  </Card>

  <Card title="Disconnected Clients" icon="wifi-off" href="/docs/administration/dashboards/system-health-dashboards#view-disconnected-clients">
    How Syteca detects and reports Clients that have gone offline.
  </Card>

  <Card title="Golden Image Mode" icon="copy" href="/docs/administration/deployment/golden-image-mode">
    Related Client-side configuration for VDI cloning.
  </Card>
</CardGroup>