Storage of Video Files

Description of JumpServer Recording Storage Directory and Retention Duration Configuration

Recording (Persistence) Directory Configuration

The global main configuration file path is: /opt/jumpserver/config/config.txt.

The default persistence directory is: /data/jumpserver. To view the currently configured persistence directory in the environment, you can execute: cat /opt/jumpserver/config/config.txt | grep “VOLUME_DIR” on the JumpServer server.

Note: If you need to change the storage directory for video files, you must adjust the entire persistence directory of JumpServer.

Retention Duration for Audit Data

First, open the system settings page of JumpServer, click on , and then switch to the page.

Here, we can configure the retention period for audit data, including <Session log retention days (day)>, which retains records of sessions, recordings, and commands. This setting only affects database storage and does not impact external storage, such as OSS.

Recording Retention Logic

All successfully uploaded recordings are saved here: /data/jumpserver/core/data/media/replay/

Linux Session Recording

For Linux-type recordings, they are initially generated in the koko directory at /data/jumpserver/koko/data/replays. After compression, they are uploaded to the core storage path at /data/jumpserver/core/data/replays, and then the temporary directory for koko recordings is deleted locally.

Windows Session Recording

For Windows-type recordings, they are initially generated in the lion directory at /data/jumpserver/lion/data/replays. After compression, they are uploaded to the core storage path at /data/jumpserver/core/data/replays, and then the temporary directory for lion recordings is deleted locally.

Note: The recording retention logic is similar for other components, such as razor, xrdp, chen, and other connection components.

External Recording Storage

JumpServer supports storing recordings in object storage services. Currently supported external recording storage options include: S3, Ceph, Swift, OSS, Azure, OBS, COS, and SFTP.

Note: Recordings from external storage

1. When playing recordings from the browser, the recording file will first be downloaded to the local directory of the server (not the user’s local machine).
2. The recording will not be deleted after playback is completed (there will be a copy of the recording file both locally and on OSS).
3. The browser caches the parsing address of the recording stored on the server.

Configure Object Storage Services

Open the System settings page in JumpServer, click to switch to the