From e1a876422e1259d2d81f3936f2d611b92b3024ca Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Fri, 8 Dec 2023 13:08:30 +0100
Subject: [PATCH] Replace warm_archive with walrus
---
doc.zih.tu-dresden.de/docs/data_transfer/datamover.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md b/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md
index e65e8084f..2be180379 100644
--- a/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md
+++ b/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md
@@ -82,7 +82,8 @@ To identify the mount points of the different filesystems on the data transfer m
!!! note
The [warm archive](../data_lifecycle/warm_archive.md) and the `projects` filesystem are not
writable from within batch jobs.
- However, you can store the data in the `warm_archive` using the Datamover nodes via `dt*` commands.
+ However, you can store the data in the [`walrus` filesystem](../data_lifecycle/working.md)
+ using the Datamover nodes via `dt*` commands.
## Transferring Files Between ZIH Systems and Group Drive
--
GitLab