Zum Hauptinhalt gehen
 

Wie können wir helfen?

Suche

[en] Back up Files and Manage Disk Space

  • Aktualisiert

[en] Overview

[en] If you use Standard Stack, you should back up important files and directories on a schedule consistent with your corporate usage and retention requirements. It's also a good idea to monitor directories that might grow based on your Acrolinx usage patterns.

[en] Directories and Files

[en] There are several directories and files are important to the core functionality of your Acrolinx Platform and contain data that is specific to your installation. Some of these live inside the core-server container and some of them are accessible via the configuration directory. The files and directories that live in the configuration directory include:

  • [en] Reuse repositories

    <config directory>/data/reuse/<LANGUAGE_ID>/<REPOSITORY_NAME>

    [en] This directory stores reuse repositories.

  • [en] The server configuration files

    <config directory>/server/bin/

    [en] The server configuration files control the performance, logging, and connectivity of the Acrolinx Platform.

  • [en] The language configuration files

    <config directory>/data/<LANGUAGE_ID>/configuration.properties

    [en] Each installed language in the path <config directory>/data/<LANGUAGE_ID>/ has a copy of this file (where <LANGUAGE_ID> is a two-letter abbreviation of each installed language). Each of these files defines the behavior of the writing guidance for the given language.

  • [en] The configuration directory

    /home/acrolinx/config

    [en] The configuration directory stores the overlay copies for all files that you use to configure the Acrolinx Platform. When you install Acrolinx, you create an empty configuration directory. You then add files to the configuration directory and restart the Acrolinx Platform. After the platform restarts, it loads updated settings from files that it detects in the configuration directory. All other standard settings load from the container images.

[en] To free up disk space when a short downtime is acceptable, you can remove temporary files. To do this, delete and restart the core server pod with the following command:

 kubectl -n acrolinx delete pod acrolinx-core-server-0

[en] Change the Maximum File Size Limit for Uploaded Files

[en] There are several parts of the Dashboard where users can upload relatively large files. You can configure an upper size limit for such files. For example, terminology database backups or reporting database backups can take several minutes to upload. You might change this limit if you notice that file uploads are placing an unnecessary burden on your server.

  • [en] By default, the Acrolinx Platform accepts files up to a maximum of 1 GB.

  • [en] The maximum configurable value for this property is 2,147,483,648 bytes, which is about 2 GB.

  • [en] If you set the value to zero, there’s no upper size limit at all

[en] This limit doesn’t apply to image uploads or license file uploads, which have their own hard-coded limit of 20 MB.

[en] To change the maximum file size limit for uploaded files, follow these steps:

  1. [en] Open your overlay of the core server properties file.

    [en] You find the overlay for the core server properties file in the following location:

    <config directory>/server/bin/coreserver.properties

  2. [en] Add the following property:

    jetty.maxFormContentSize=[BYTES]

    [en] For example, to set a file size limit of 500 MB add the property as follows:

    jetty.maxFormContentSize=500000000

  3. [en] Save your changes and restart the Acrolinx Platform.