Skip to content

Data Transfer from/to the Perun Cluster Located at TUKE

The Perun cluster is operated at the Technical University of Košice (TUKE) and provides dedicated infrastructure for transferring data between the Slovak Academy of Sciences (SAS) and TUKE. Dedicated data transfer nodes are provided for this purpose, allowing data to be transferred without placing unnecessary load on the Perun login nodes.

The recommended tools for data transfer are rsync and scp. The dedicated transfer nodes and their connection to TUKE are described below, followed by an overview of the available data transfer utilities.

Data Transfer Nodes

Transfers must be executed via dedicated data transfer nodes:

  • data01
  • data02

These nodes are optimized for high-throughput data movement and are connected via a 2 × 100 Gb/s link to TUKE. Filesystems such as /home and /project are directly mounted on these nodes, allowing efficient direct transfers. The service is available to all integrated users without additional setup.

Both transfer nodes are accessible via the ssh command from Perun login nodes:

ssh data01

On the TUKE side, the corresponding transfer endpoints are:

  • 10.101.40.16
  • 10.101.40.17

In the following examples, <TUKE_HOST> refers to either one of these addresses.

Login nodes

The use of login nodes for large data transfers is discouraged. The data01 or data02 nodes should always be used to ensure that data transfers do not unnecessarily affect the performance and stability of the login nodes.

Prerequisites

The following conditions must be met to use the transfer service:

  • The account must be integrated with TUKE.
  • Valid SSH access must be available.
  • The connection must be made through data01 or data02.

If the account has not yet been integrated, the procedure described in the User Account Integration section must be followed.

Data Transfer Utilities

Data transfers between SAS and the TUKE site of the Perun cluster are performed using SSH-based tools. The supported utilities are:

  • rsync – recommended for most use cases
  • scp – suitable for simple, one-time transfers

Detailed instructions for using these utilities are provided in the data transfer documentation.

rsync over scp

For most scenarios, rsync is preferred due to its efficiency and ability to resume interrupted transfers. scp is more suitable for small or simple operations where ease of use is the main consideration.

Created by: Andrej Sec, Marek Štekláč, Marek Štekláč