Merge branch 'merge-preview-in-main' into 'main'

Automated merge from preview to main

See merge request !892

doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md

@@ -72,6 +72,50 @@ old storages will be purged, probably by the end of November.
 
 The process of syncing data from `/warm_archive` to `/data/walrus` is still ongoing.
 
+### Transfer Data to New Home Directory
+
+Your personal (old) home directory at Taurus will not be automatically transferred to the new Barnard
+system. **You are responsible for this task.** Please do not copy your entire home, but consider
+this opportunity for cleaning up you data. E.g., it might make sense to delete outdated scripts, old
+log files, etc., and move other files to an archive filesystem. Thus, please transfer only selected
+directories and files that you need on the new system.
+
+The well-known [datamover tools](../../data_transfer/datamover/) are available to run such transfer
+jobs under Slurm. The steps are as follows:
+
+1. Login to Barnard: `ssh login[1-4].barnard.tu-dresden.de`
+1. The command `dtinfo` will provide you the mountpoints
+
+    ```console
+    marie@barnard$ dtinfo
+    [...]
+    directory on datamover      mounting clusters   directory on cluster
+
+    /data/old/home              Taurus              /home
+    /data/old/lustre/scratch2   Taurus              /scratch
+    /data/old/lustre/ssd        Taurus              /lustre/ssd
+    [...]
+    ```
+
+1. Use the `dtls` command to list your files on the old home directory: `marie@barnard$ dtls
+   /data/old/home/marie`
+1. Use `dtcp` command to invoke a transfer job, e.g.,
+
+   ```console
+   marie@barnard$ dtcp --recursive /data/old/home/marie/<useful data> /home/marie/
+   ```
+
+   **Note**, please adopt the source and target paths to your needs. All available options can be
+   queried via `dtinfo --help`.
+
+!!! warning
+
+    Please be aware that there is **no synchronisation process** between your home directories at
+    Taurus and Barnard. Thus, with the very first transfer, they will become divergent.
+
+    We recommand to **take some minutes for planing the transfer process**. Do not act with
+    precipitation.
+
 ## Software
 
 Please use `module spider` to identify the software modules you need to load. Like

doc.zih.tu-dresden.de/docs/jobs_and_resources/migration_2023.md

@@ -66,11 +66,13 @@ of the action items.
 Why do users need to copy their data? Why only some? How to do it best?
 
 * The sync of hundreds of terabytes can only be done planned and carefully.
-(/scratch, /warm_archive, /projects). The HPC team will use multiple syncs
-to not forget the last bytes. During the downtime, /projects will be migrated.
-* User homes are relatively small and can be copied by the scientists.
+(`/scratch`, `/warm_archive`, `/projects`). The HPC team will use multiple syncs
+to not forget the last bytes. During the downtime, `/projects` will be migrated.
+* User homes (`/home`) are relatively small and can be copied by the scientists.
 Keeping in mind that maybe deleting and archiving is a better choice.
-* For this, datamover nodes are available to run transfer jobs under Slurm.
+* For this, datamover nodes are available to run transfer jobs under Slurm. Please refer to the
+section [Transfer Data to New Home Directory](../barnard_test#transfer-data-to-new-home-directory)
+for more detailed instructions.
 
 ### A Graphical Overview