...
External connections to the NHR systems in Berlin or Göttingen require that an SSH key pair is used for authentication. More details can be found here. The location of the private key file can be specified when calling scp or rsync on the user's local machine. Some examples including both data transfer directions are shown below.
...
Data transfer in the context of a batch job is restricted due to limited network access of the compute nodes. Please send a message to the support mailing list in case you need further help.
Data Transfer between NHR@ZIB and NHR@Göttingen with legacy accounts
Data transfer with legacy accounts between a Berlin and a Göttingen login node using scp or rsync works right out of the box - that is, without specifying any keys or passwords. This is enabled through host-based authentication which is active by default. Legacy accounts are those which are opened before 1 April 2024.
| Hinweis |
|---|
For internal this data transfer, please always use the host name alone, omitting the domain suffix ".nhr.de" or "hlrn.de". You can use the generic names blogin, glogin or specific names like blogin5, glogin2, etc.. This way NHR internal links are used which are faster than external routes. The latter are used when specifying fully qualified host names (blogin.hlrn.de or glogin.hlrn.de) which is not recommended here. |
...