To share information between the Linux VDI and Atos HPC
Just use the shared $HOME or $PERM filesystems. See for more information on the filesystem layout of the platform.
To share information between the Linux VDI and your end-user-device (eg Windows or Mac laptop)
The first method available is to use OneDrive on both platforms. On Mac and Windows there is a native client that show as a native folder and in Linux VDI it is possible to mount OneDrive as disk unit too. See How to configure and mount OneDrive - Linux Virtual Desktop VDI FAQ for more information.
The second method available involves setting up Teleport in your end-user-device and the using scp or rsync to copy data to and from your device into to Linux VDI. Please check Teleport SSH Access for more information about how to correctly configure Teleport. Do keep in mind that, as stated in Missing features and known issues - Linux Virtual Desktop VDI, the host name of your Linux VDI may change after system upgrades, so you may need to edit your $HOME/.ssh/config file to adapt it to host name changes
Please be aware that Teleport is not designed for high data transfer throughputs so if you are transferring large amounts of data you want to try the third method
The third method is the FTP service in ecaccess. With this service you will be able to access all ECMWF filesystem with a fast protocol, so it might be better suited for large fast transfers. Please check the documentation at the ECaccess User Guide
To copy information from your current Leap42 $HOME and $PERM filesystems into the new corresponding filesystems
"Legacy" filesystems will be available for some time, so you should be able to just "cp" those files. See How can I access legacy filesystems - Linux Virtual Desktop VDI FAQ for more details. However, be aware that legacy systems will be switched off at some point during the migration process so please ensure that you copy any required information as soon as possible.
However, you may still want to use rsync as a convenient way of copying only changed files. Eg
$ rsync -av /originfilesystem /destinationfilesystem
Either the origin or the destination of rsync can be remote, but not both.