HPCwiki - User contributions [en]

Galaxy

2026-09-04T14:03:20Z

Prins089:

[[File:Galaxy_project_logo_square.png|alt=Galaxy|right|frameless|253x253px|link=https://galaxyproject.org/]]
Anunna previously hosted a separate Galaxy project server at:

https://galaxy.anunna.wur.nl/

This standalone server has been retired. Galaxy is now available as an application within [[Open OnDemand|Open OnDemand (wiki page)]]. You can access it via [https://apps.anunna.wur.nl/ apps.anunna.wur.nl].

To use Galaxy, log in to Open OnDemand and launch it from the application menu. This provides access to a personal Galaxy Project instance with access to Anunna's compute and storage. The installation is persistent per user, datasets and tools that you upload or change will remain for the next time you run it.

Galaxy

2026-09-04T14:02:03Z

Prins089:

[[File:Galaxy_project_logo_square.png|alt=Galaxy|right|frameless|253x253px|link=https://galaxyproject.org/]]
Anunna previously hosted a separate Galaxy project server at:

https://galaxy.anunna.wur.nl/

This standalone server has been retired. Galaxy is now available as an application within [[Open OnDemand|Open OnDemand (wiki page)]]. You can access it via [https://apps.anunna.wur.nl/ apps.anunna.wur.nl].

To use Galaxy, log in to Open OnDemand and launch it from the application menu. This provides access to Galaxy using the same Anunna environment and storage.

Galaxy

2026-09-04T13:58:50Z

Prins089:

[[File:Galaxy_project_logo_square.png|alt=Galaxy|right|frameless|304x304px]]
Anunna previously hosted a separate Galaxy project server at:

https://galaxy.anunna.wur.nl/

This standalone server has been retired. Galaxy is now available as an application within [[Open OnDemand|Open OnDemand (wiki page)]]. You can access it via [https://apps.anunna.wur.nl/ apps.anunna.wur.nl].

To use Galaxy, log in to Open OnDemand and launch it from the application menu. This provides access to Galaxy using the same Anunna environment and storage.

Galaxy

2026-09-04T13:58:37Z

Prins089:

= Galaxy =
[[File:Galaxy_project_logo_square.png|alt=Galaxy|right|frameless|304x304px]]
Anunna previously hosted a separate Galaxy project server at:

https://galaxy.anunna.wur.nl/

This standalone server has been retired. Galaxy is now available as an application within [[Open OnDemand|Open OnDemand (wiki page)]]. You can access it via [https://apps.anunna.wur.nl/ apps.anunna.wur.nl].

To use Galaxy, log in to Open OnDemand and launch it from the application menu. This provides access to Galaxy using the same Anunna environment and storage.

Galaxy

2026-09-04T13:58:04Z

Prins089:

= Galaxy =
[[File:Galaxy project logo square.png|alt=Galaxy|thumb]]

Anunna previously hosted a separate Galaxy project server at:

https://galaxy.anunna.wur.nl/

This standalone server has been retired. Galaxy is now available as an application within [[Open OnDemand|Open OnDemand (wiki page)]]. You can access it via [https://apps.anunna.wur.nl/ apps.anunna.wur.nl].

To use Galaxy, log in to Open OnDemand and launch it from the application menu. This provides access to Galaxy using the same Anunna environment and storage.

File:Galaxy project logo square.png

2026-09-04T13:57:53Z

Prins089:

galaxy

Galaxy

2026-09-04T13:57:32Z

Prins089:

= Galaxy =

Anunna previously hosted a separate Galaxy project server at:

https://galaxy.anunna.wur.nl/

This standalone server has been retired. Galaxy is now available as an application within [[Open OnDemand|Open OnDemand (wiki page)]]. You can access it via [https://apps.anunna.wur.nl/ apps.anunna.wur.nl].

To use Galaxy, log in to Open OnDemand and launch it from the application menu. This provides access to Galaxy using the same Anunna environment and storage.

Galaxy

2026-09-04T13:57:07Z

Prins089: Created page with "= Galaxy = link=https://galaxyproject.org/ Anunna previously hosted a separate Galaxy project server at: https://galaxy.anunna.wur.nl/ This standalone server has been retired. Galaxy is now available as an application within Open OnDemand (wiki page). You can access it via [https://apps.anunna.wur.nl/ apps.anunna.wur.nl]. To use Galaxy, log in to Open OnDemand and launch it from the appli..."

= Galaxy =

[[File:Galaxy-logo.png|right|250px|alt=Galaxy Project logo|link=https://galaxyproject.org/]]

Anunna previously hosted a separate Galaxy project server at:

https://galaxy.anunna.wur.nl/

This standalone server has been retired. Galaxy is now available as an application within [[Open OnDemand|Open OnDemand (wiki page)]]. You can access it via [https://apps.anunna.wur.nl/ apps.anunna.wur.nl].

To use Galaxy, log in to Open OnDemand and launch it from the application menu. This provides access to Galaxy using the same Anunna environment and storage.

Cluster Architecture Overview

2026-09-03T13:28:47Z

Prins089:

Anunna has a classic, heterogeneous HPC architecture: a set of login nodes that users connect to, a larger pool of compute nodes where the actual work runs, a fast parallel filesystem shared across the whole cluster, and a high-speed network tying it all together. The design is built to grow — nodes and storage can be added over time
[[File:Anunna-conceptual-2.png|none|thumb|1200x1200px]]

== Login nodes ==

You reach the cluster by connecting to <code>login.anunna.wur.nl</code> over SSH (see [[Log in to Anunna]]). The login nodes are the entry point: you use them to edit files, manage your data, and submit jobs. They are shared by everyone, so they are not for heavy computation — anything beyond light, interactive work belongs in a job (see [[Batch Jobs]] and [[Interactive Jobs]]).

== Compute nodes ==

The compute nodes do the actual work. They are heterogeneous: ordinary CPU nodes for most jobs, plus nodes equipped with NVIDIA or AMD GPUs for accelerated workloads. Jobs reach them through the SLURM scheduler, which places each job on a node that matches its requested resources.

* CPU work runs in the <code>main</code> partition.
* GPU work runs in the <code>gpu</code> (NVIDIA) and <code>gpu_amd</code> (AMD) partitions.

For the hardware details of each node type, see [[Compute Hardware Overview]]; for how to select a partition or constrain a job to particular hardware, see [[Partitions / Queues]] and [[Choosing a node (constraints)]].
[[File:Anunna-resources.png|none|thumb|1200x1200px]]

== Storage ==

A [https://en.wikipedia.org/wiki/Lustre_(file_system) Lustre] parallel filesystem (mounted at <code>/lustre</code>) is shared across all nodes and is the cluster's main working storage; your home directory lives on a separate, smaller NFS filesystem. Longer-term and archival storage is available too. For the full picture — quotas, backup behaviour, and which tier to use for what — see [[Storage Systems Overview]].

== Network ==

The nodes and the Lustre filesystem are connected by a high-speed, low-latency interconnect, which is what allows the parallel filesystem and multi-node jobs to perform well. 

== Operating system ==

The cluster runs Ubuntu 24.04 across its nodes. Software is provided through [[Environment Modules | environment modules]] rather than being installed system-wide, so several versions of the same program can coexist.

== See also ==

* [[Compute Hardware Overview]]
* [[Storage Systems Overview]]
* [[Scheduler Overview (Slurm)]]
* [[Log in to Anunna]]

File:Anunna-resources.png

2026-09-03T13:28:39Z

Prins089:

Compute resources

Cluster Architecture Overview

2026-09-03T13:27:58Z

Prins089:

Anunna has a classic, heterogeneous HPC architecture: a set of login nodes that users connect to, a larger pool of compute nodes where the actual work runs, a fast parallel filesystem shared across the whole cluster, and a high-speed network tying it all together. The design is built to grow — nodes and storage can be added over time
[[File:Anunna-conceptual-2.png|none|thumb|1200x1200px]]

== Login nodes ==

You reach the cluster by connecting to <code>login.anunna.wur.nl</code> over SSH (see [[Log in to Anunna]]). The login nodes are the entry point: you use them to edit files, manage your data, and submit jobs. They are shared by everyone, so they are not for heavy computation — anything beyond light, interactive work belongs in a job (see [[Batch Jobs]] and [[Interactive Jobs]]).

== Compute nodes ==

The compute nodes do the actual work. They are heterogeneous: ordinary CPU nodes for most jobs, plus nodes equipped with NVIDIA or AMD GPUs for accelerated workloads. Jobs reach them through the SLURM scheduler, which places each job on a node that matches its requested resources.

* CPU work runs in the <code>main</code> partition.
* GPU work runs in the <code>gpu</code> (NVIDIA) and <code>gpu_amd</code> (AMD) partitions.

For the hardware details of each node type, see [[Compute Hardware Overview]]; for how to select a partition or constrain a job to particular hardware, see [[Partitions / Queues]] and [[Choosing a node (constraints)]].

== Storage ==

A [https://en.wikipedia.org/wiki/Lustre_(file_system) Lustre] parallel filesystem (mounted at <code>/lustre</code>) is shared across all nodes and is the cluster's main working storage; your home directory lives on a separate, smaller NFS filesystem. Longer-term and archival storage is available too. For the full picture — quotas, backup behaviour, and which tier to use for what — see [[Storage Systems Overview]].

== Network ==

The nodes and the Lustre filesystem are connected by a high-speed, low-latency interconnect, which is what allows the parallel filesystem and multi-node jobs to perform well. 

== Operating system ==

The cluster runs Ubuntu 24.04 across its nodes. Software is provided through [[Environment Modules | environment modules]] rather than being installed system-wide, so several versions of the same program can coexist.

== See also ==

* [[Compute Hardware Overview]]
* [[Storage Systems Overview]]
* [[Scheduler Overview (Slurm)]]
* [[Log in to Anunna]]

File:Anunna-conceptual-2.png

2026-09-03T13:27:50Z

Prins089:

Concept diagram Anunna

Backup Policy

2026-09-01T15:05:06Z

Prins089:

Different storage areas on Anunna come with very different backup guarantees. Knowing which is which is essential: some areas are never backed up, and data lost there cannot be recovered. This page summarises the situation; the page for each storage area gives more context.

{| class="wikitable"
|-
! Storage !! Backed up? !! Notes
|-
| [[Home Directory|/home]] || Yes. With a managed backup solution that allows file-level restore || Good for configuration files and small results you can't afford to lose.
|-
| [[Compute Storage|/lustre/nobackup]] || No. || The default Lustre area; cheaper, but lost data cannot be recovered. Keep your own copies of anything important.
|-
| [[Compute Storage|/lustre/backup]] || Yes — a second copy on a separate machine. || A disaster-recovery copy, not a versioned backup. It may help revert a mistake if you report it very quickly, but there is no guarantee.
|-
| [[Compute Storage|/lustre/scratch]] || No. || Temporary area; files may be purged automatically (typically after 30 days).
|-
| [[Archival Storage|/archive]] || Yes — to tape, restorable from roughly a week of history (same schedule as /home). || Warm storage on the login nodes, for WUR users.
|}

== Recommendations ==

* Treat <code>/lustre/nobackup</code> and <code>/lustre/scratch</code> as expendable. Anything you cannot regenerate should also live somewhere that is backed up, or be archived to tape — see [[Archival Storage]].
* A "backup" tier protects against hardware disaster, not against your own mistakes. If you delete something by accident, report it immediately; recovery is best-effort.

== See also ==
* [[Storage Systems Overview]]
* [[Home Directory]]
* [[Compute Storage]]
* [[Archival Storage]]
* [[Quotas]]

Maintenance Schedule

2026-09-01T08:37:12Z

Prins089:

== Anunna maintenance ==
Maintenance windows allow us to safely perform essential updates and upgrades that cannot be carried out while the cluster is in use. By grouping this work into planned downtimes, we keep Anunna secure, reliable and up to date while minimising unexpected disruption.

Anunna is taken down for planned maintenance — firmware and software updates — roughly twice a year. Typically one downtime is scheduled in April or May and another in October, in a week free of teaching, to disrupt usage as little as possible.

During a downtime the cluster is unavailable. Jobs are not scheduled to run across a planned downtime, so check the announced dates when planning long jobs.
== Maintenance schedule ==
{| class="wikitable"
! Scheduled downtime
! Date
! Planned work
! Unavailable services
|-
| Autumn 2026
| 12–16 October 2026
| OS patching Lustre upgrade to version 2.17
| HPC compute Login nodes Web applications Lustre storage
|-
| Spring 2027
|
|
|
|-
| Autumn 2027
|
|
|
|}
== Announcements ==

Planned maintenance is announced in advance — watch the Message of the Day on the [[Portal Overview|Apps Portal]], login nodes and we always send out an announcement in advance over e-mail.
== Reporting problems ==

If something is not working — during or outside maintenance — see [[How to Get Help]].

== See also ==
* [[How to Get Help]]
* [[Cluster Architecture Overview]]

Maintenance Schedule

2026-09-01T08:35:15Z

Prins089:

== Maintenance schedule ==
{| class="wikitable"
! Scheduled downtime
! Date
! Planned work
! Unavailable services
|-
| Autumn 2026
| 12–16 October 2026
| OS patching Lustre upgrade to version 2.17
| HPC compute Login nodes Web applications Lustre storage
|-
| Spring 2027
|
|
|
|-
| Autumn 2027
|
|
|
|}

== Anunna maintenance ==
Anunna is taken down for planned maintenance — firmware and software updates — roughly twice a year. Typically one downtime is scheduled in April or May and another in October, in a week free of teaching, to disrupt usage as little as possible.

During a downtime the cluster is unavailable. Jobs are not scheduled to run across a planned downtime, so check the announced dates when planning long jobs.

== Announcements ==

Planned maintenance is announced in advance — watch the Message of the Day on the [[Portal Overview|Apps Portal]], login nodes and we always send out an announcement in advance over e-mail.
== Reporting problems ==

If something is not working — during or outside maintenance — see [[How to Get Help]].

== See also ==
* [[How to Get Help]]
* [[Cluster Architecture Overview]]

Maintenance Schedule

2026-09-01T08:34:32Z

Prins089:

== Upcoming downtime ==
{| class="wikitable"
! Downtime
! Date
! Planned work
! Unavailable services
|-
| Autumn 2026
| 12–16 October 2026
| OS patching Lustre upgrade to version 2.17
| HPC compute Login nodes Web applications Lustre storage
|-
| Spring 2027
|
|
|
|-
| Autumn 2027
|
|
|
|}

== Anunna maintenance ==
Anunna is taken down for planned maintenance — firmware and software updates — roughly twice a year. Typically one downtime is scheduled in April or May and another in October, in a week free of teaching, to disrupt usage as little as possible.

During a downtime the cluster is unavailable. Jobs are not scheduled to run across a planned downtime, so check the announced dates when planning long jobs.

== Announcements ==

Planned maintenance is announced in advance — watch the Message of the Day on the [[Portal Overview|Apps Portal]], login nodes and we always send out an announcement in advance over e-mail.
== Reporting problems ==

If something is not working — during or outside maintenance — see [[How to Get Help]].

== See also ==
* [[How to Get Help]]
* [[Cluster Architecture Overview]]

SSH Access

2026-08-31T11:12:01Z

Prins089:

This page explains how to connect to Anunna over SSH. Once you are logged in, see [[Login Nodes]] for what the login nodes are for, and [[Policies and Terms of Use]] for the rules that apply.

== Connecting ==

You log in to Anunna using the Secure Shell protocol (SSH) on the default port (TCP 22). The address of the login server is:

login.anunna.wur.nl

You are automatically redirected to a currently valid login server. An SSH client is built in on Linux and macOS; on Windows you usually install one, such as [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] or MobaXTerm.

Note that access may be restricted to certain IP ranges, and SSH may be blocked (see [[Unblocking your IP|here]]) where port 22 is closed by a firewall. (For example, WUR FB-IT does not allow port 22 over WiFi to certain systems.)

'''The login server is an access point only — it is not for CPU- or memory-intensive work.''' Anything beyond light, interactive use belongs in a job; see [[Login Nodes]] and [[Scheduler Overview (Slurm)]].

=== Linux and macOS ===

An SSH client is available from any Linux or macOS terminal:

<syntaxhighlight lang="bash">
ssh <username>@login.anunna.wur.nl
</syntaxhighlight>

If the connection is refused, check if your IP is (temporarily) banned from connecting: https://unban.anunna.wur.nl/unban

=== Windows ===

On Windows you connect with an SSH client such as '''MobaXTerm''' or '''PuTTY'''. In either case, set the remote host to <code>login.anunna.wur.nl</code> and enter your username (not your email address) and WUR password. No characters appear while you type your password — this is normal.

For key-based login, generate an SSH key pair with the client's key generator (MobaKeygen in MobaXTerm, or PuTTYgen for PuTTY), protect it with a passphrase, and add the public key to <code>~/.ssh/authorized_keys</code> on Anunna. PuTTY users can hold the key in Pageant so they do not have to type the passphrase each time. See the [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY homepage] for full instructions.

== Logging in without a password ==

You can configure SSH to log in without typing your password each time; see [[ssh_without_password|SSH without password]].

== Connecting to a compute node ==

To open a shell or a direct connection on a compute node where your job is running, see [[Compute Nodes]].

== See also ==
* [[Unblocking your IP]]
* [[Login Nodes]]
* [[Compute Nodes]]
* [[Data Transfer Methods]]
* [[Create shortcut log-in command]] — SSH aliases and ~/.ssh/config shortcuts
* [[ssh_without_password|SSH without password]]
* [[Scheduler Overview (Slurm)]]

== External links ==
* [http://en.wikipedia.org/wiki/Secure_Shell Secure Shell on Wikipedia]
* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY homepage]

Cluster Architecture Overview

2026-08-28T13:50:41Z

Prins089:

Anunna has a classic, heterogeneous HPC architecture: a set of login nodes that users connect to, a larger pool of compute nodes where the actual work runs, a fast parallel filesystem shared across the whole cluster, and a high-speed network tying it all together. The design is built to grow — nodes and storage can be added over time
[[File:Anunna-conceptual.png|thumb|1200x1200px|none]]
== Login nodes ==

You reach the cluster by connecting to <code>login.anunna.wur.nl</code> over SSH (see [[Log in to Anunna]]). The login nodes are the entry point: you use them to edit files, manage your data, and submit jobs. They are shared by everyone, so they are not for heavy computation — anything beyond light, interactive work belongs in a job (see [[Batch Jobs]] and [[Interactive Jobs]]).

== Compute nodes ==

The compute nodes do the actual work. They are heterogeneous: ordinary CPU nodes for most jobs, plus nodes equipped with NVIDIA or AMD GPUs for accelerated workloads. Jobs reach them through the SLURM scheduler, which places each job on a node that matches its requested resources.

* CPU work runs in the <code>main</code> partition.
* GPU work runs in the <code>gpu</code> (NVIDIA) and <code>gpu_amd</code> (AMD) partitions.

For the hardware details of each node type, see [[Compute Hardware Overview]]; for how to select a partition or constrain a job to particular hardware, see [[Partitions / Queues]] and [[Choosing a node (constraints)]].

== Storage ==

A [https://en.wikipedia.org/wiki/Lustre_(file_system) Lustre] parallel filesystem (mounted at <code>/lustre</code>) is shared across all nodes and is the cluster's main working storage; your home directory lives on a separate, smaller NFS filesystem. Longer-term and archival storage is available too. For the full picture — quotas, backup behaviour, and which tier to use for what — see [[Storage Systems Overview]].

== Network ==

The nodes and the Lustre filesystem are connected by a high-speed, low-latency interconnect, which is what allows the parallel filesystem and multi-node jobs to perform well. 

== Operating system ==

The cluster runs Ubuntu 24.04 across its nodes. Software is provided through [[Environment Modules | environment modules]] rather than being installed system-wide, so several versions of the same program can coexist.

== See also ==

* [[Compute Hardware Overview]]
* [[Storage Systems Overview]]
* [[Scheduler Overview (Slurm)]]
* [[Log in to Anunna]]

Cluster Architecture Overview

2026-08-28T13:50:15Z

Prins089:

Anunna has a classic, heterogeneous HPC architecture: a set of login nodes that users connect to, a larger pool of compute nodes where the actual work runs, a fast parallel filesystem shared across the whole cluster, and a high-speed network tying it all together. The design is built to grow — nodes and storage can be added over time
[[File:Anunna-conceptual.png|left|thumb|1200x1200px]]
== Login nodes ==

You reach the cluster by connecting to <code>login.anunna.wur.nl</code> over SSH (see [[Log in to Anunna]]). The login nodes are the entry point: you use them to edit files, manage your data, and submit jobs. They are shared by everyone, so they are not for heavy computation — anything beyond light, interactive work belongs in a job (see [[Batch Jobs]] and [[Interactive Jobs]]).

== Compute nodes ==

The compute nodes do the actual work. They are heterogeneous: ordinary CPU nodes for most jobs, plus nodes equipped with NVIDIA or AMD GPUs for accelerated workloads. Jobs reach them through the SLURM scheduler, which places each job on a node that matches its requested resources.

* CPU work runs in the <code>main</code> partition.
* GPU work runs in the <code>gpu</code> (NVIDIA) and <code>gpu_amd</code> (AMD) partitions.

For the hardware details of each node type, see [[Compute Hardware Overview]]; for how to select a partition or constrain a job to particular hardware, see [[Partitions / Queues]] and [[Choosing a node (constraints)]].

== Storage ==

A [https://en.wikipedia.org/wiki/Lustre_(file_system) Lustre] parallel filesystem (mounted at <code>/lustre</code>) is shared across all nodes and is the cluster's main working storage; your home directory lives on a separate, smaller NFS filesystem. Longer-term and archival storage is available too. For the full picture — quotas, backup behaviour, and which tier to use for what — see [[Storage Systems Overview]].

== Network ==

The nodes and the Lustre filesystem are connected by a high-speed, low-latency interconnect, which is what allows the parallel filesystem and multi-node jobs to perform well. 

== Operating system ==

The cluster runs Ubuntu 24.04 across its nodes. Software is provided through [[Environment Modules | environment modules]] rather than being installed system-wide, so several versions of the same program can coexist.

== See also ==

* [[Compute Hardware Overview]]
* [[Storage Systems Overview]]
* [[Scheduler Overview (Slurm)]]
* [[Log in to Anunna]]

File:Anunna-conceptual.png

2026-08-28T13:49:16Z

Prins089:

Conceptual diagram of Anunna

Cluster Architecture Overview

2026-08-28T13:47:53Z

Prins089:

Anunna has a classic, heterogeneous HPC architecture: a set of login nodes that users connect to, a larger pool of compute nodes where the actual work runs, a fast parallel filesystem shared across the whole cluster, and a high-speed network tying it all together. The design is built to grow — nodes and storage can be added over time
[[File:Conceptual-diagram.svg|left|frame]]

== Login nodes ==

You reach the cluster by connecting to <code>login.anunna.wur.nl</code> over SSH (see [[Log in to Anunna]]). The login nodes are the entry point: you use them to edit files, manage your data, and submit jobs. They are shared by everyone, so they are not for heavy computation — anything beyond light, interactive work belongs in a job (see [[Batch Jobs]] and [[Interactive Jobs]]).

== Compute nodes ==

The compute nodes do the actual work. They are heterogeneous: ordinary CPU nodes for most jobs, plus nodes equipped with NVIDIA or AMD GPUs for accelerated workloads. Jobs reach them through the SLURM scheduler, which places each job on a node that matches its requested resources.

* CPU work runs in the <code>main</code> partition.
* GPU work runs in the <code>gpu</code> (NVIDIA) and <code>gpu_amd</code> (AMD) partitions.

For the hardware details of each node type, see [[Compute Hardware Overview]]; for how to select a partition or constrain a job to particular hardware, see [[Partitions / Queues]] and [[Choosing a node (constraints)]].

== Storage ==

A [https://en.wikipedia.org/wiki/Lustre_(file_system) Lustre] parallel filesystem (mounted at <code>/lustre</code>) is shared across all nodes and is the cluster's main working storage; your home directory lives on a separate, smaller NFS filesystem. Longer-term and archival storage is available too. For the full picture — quotas, backup behaviour, and which tier to use for what — see [[Storage Systems Overview]].

== Network ==

The nodes and the Lustre filesystem are connected by a high-speed, low-latency interconnect, which is what allows the parallel filesystem and multi-node jobs to perform well. 

== Operating system ==

The cluster runs Ubuntu 24.04 across its nodes. Software is provided through [[Environment Modules | environment modules]] rather than being installed system-wide, so several versions of the same program can coexist.

== See also ==

* [[Compute Hardware Overview]]
* [[Storage Systems Overview]]
* [[Scheduler Overview (Slurm)]]
* [[Log in to Anunna]]

File:Conceptual-diagram.svg

2026-08-28T13:46:42Z

Prins089:

HPC diagram of Anunna

Reporting Usage

2026-07-21T12:30:48Z

Prins089:

This page covers how to see what you and your group are using on Anunna, and what it costs. For job-level monitoring (<code>squeue</code>, <code>sacct</code>, and the rest) see [[Monitoring Jobs]]; for the prices themselves see [[Tariffs]].

== Estimating your costs ==

The <code>get_my_bill</code> script shows your Slurm jobs and estimates their compute costs over a period. Load the <code>anunna</code> module and run it:

<syntaxhighlight lang="bash">
module load anunna
get_my_bill
</syntaxhighlight>

By default, it shows jobs for your user account from the first day of the current month through the current time. Each row includes the job start time, job ID and name, state, allocated CPUs, GPUs and memory, elapsed seconds, and estimated cost. A total is shown at the bottom.

The estimate is based on the resources allocated to each job and its elapsed wall time. It is indicative rather than a final bill; the monthly usage reports are leading.

Useful options:

* <code>-s YYYY-MM-DD</code> or <code>--start YYYY-MM-DD</code> — start the report on this date. The default is the first day of the current month.
* <code>-e YYYY-MM-DD</code> or <code>--end YYYY-MM-DD</code> — end the report on this date, inclusive. The default is the current time.
* <code>-u USER</code> or <code>--user USER</code> — report usage for another Slurm user.
* <code>-g</code> or <code>--group</code> — report all jobs charged to the selected user's default Slurm account. Group output includes a <code>User</code> column.
* <code>-h</code> or <code>--help</code> — show all available options.

Long options that take a value can use either a space or an equals sign, for example <code>--start 2026-01-01</code> and <code>--start=2026-01-01</code> are equivalent.

Examples:

<syntaxhighlight lang="bash">
# Your jobs from a given date through now
get_my_bill --start 2026-01-01

# Your jobs in an inclusive date range
get_my_bill -s 2026-01-01 -e 2026-01-31

# All jobs charged to your group
get_my_bill --group
</syntaxhighlight>

== Cost alerts ==

You can have Anunna email you and e.g. your supervisors when your bill passes a threshold. Configure, change, or remove the alert with:

<syntaxhighlight lang="bash">module load anunna
alert_config.sh</syntaxhighlight>

== Usage reports dashboard ==

A web dashboard with usage and cost reports per group is available at https://reports.anunna.wur.nl/.

Access to group reports is only available for group leads.

Changes/access can be requested through the normal [[Support|support options]].
== Costs and tariffs ==

For the per-hour and per-TB prices used to calculate these figures — compute, GPU, storage, and reservations — see [[Tariffs]].

If your group has a commitment, usage is deducted from it; once you reach around 125% of the commitment, the HPC team will get in touch.

== See also ==
* [[Tariffs]]
* [[Monitoring Jobs]]
* [[Storage Systems Overview]]

Talk:Who Can Access?

2026-07-20T11:28:45Z

Prins089: Created page with "This page should be expanded with text and contact info about the food valley cluster deal. Access for external companies via SRF"

This page should be expanded with text and contact info about the food valley cluster deal. Access for external companies via SRF

Handling Sensitive Data (GDPR, etc.)

2026-07-20T11:19:06Z

Prins089:

Working with confidential or personal data on Anunna is very much discouraged and not allowed without prior consent.

If you want to store and use data that goes beyond the "negligible" [https://support.wur.nl/esc/en/data-storage-guidelines/data-classification?id=kb_article&sysparm_article=KB0015155 data classification], please first read WUR's data-protection [https://support.wur.nl/esc/en/information-security-privacy/privacy-policy?id=kb_article&sysparm_article=KB0016014&table=kb_knowledge&searchTerm=gdpr policy], and then contact us.

== Your responsibilities ==

* Only put sensitive data on Anunna if you are permitted to by the admins, and keep it to the minimum needed.
* Control who can access it — use group permissions carefully (see [[Shared Storage]] and [[Managing Group Members]]).
* Know what is backed up where, and where data goes when it is archived (see [[Backup Policy]] and [[Data Lifecycle Policy]]).

== See also ==
* [[Policies and Terms of Use]]
* [[Network & Security]]
* [[Backup Policy]]
* [[How to Get Help]]

User:Prins089

2026-07-20T11:03:21Z

Prins089: Created page with "[https://www.vcard.wur.nl/Views/Profile/View.aspx?id=88524 Fons Prinsen VCard] System Administrator for Anunna."

[https://www.vcard.wur.nl/Views/Profile/View.aspx?id=88524 Fons Prinsen VCard]

System Administrator for Anunna.

Training Materials

2026-06-26T11:22:37Z

Prins089: newer links to slidesets

This page collects slides and self-study material for working on Anunna. To attend an instructor-led course, see [[Workshops]] and [[2026 Course dates]]; for hands-on tutorials, see [[Tutorials]].

== Latest course slides ==

The most recent slides for the three regular courses:

* [https://wiki.anunna.wur.nl/images/c/cc/WUR_Linux_Basics_Course_Slides.pdf Linux Basics]
* [https://wiki.anunna.wur.nl/images/9/95/Hpc-basics-2026-06.pdf HPC Basics]
* [https://wiki.anunna.wur.nl/images/e/ef/Hpc-advanced-2026-06.pdf HPC Advanced]

== Self-study ==

If you cannot attend a course, these resources let you learn at your own pace:

* [[Linux Basic/Linux Self Assessment]] — check whether your command-line skills are ready for the HPC and container courses.
* [https://labex.io/linuxjourney Linux Journey] — self-paced Linux learning, with free practice virtual machines.
* [https://www.linux-path.com/en Linux Path] — a fork of Linux Journey with additional curated material.
* [https://carpentries.org Software Carpentry] — community lessons on many topics (for the command line, see Learn → Lessons → Unix shell).

See also the [[Linux Basic]] page for more on the Linux fundamentals course.

== Past course sessions ==

Slides from earlier course sessions are kept here for reference.

; 2026 — HPC Advanced
: [[:File:Hpc-advanced-2026-06.pdf|Slides]]
; 2026 — HPC Basics
: [[:File:Hpc-basics-2026-06.pdf|Slides]]
; 2025 — Linux Basics
: [[:File:WUR Linux Basics Course Slides.pdf|Slides]]
; November 2021 — HPC Advanced
: [[:File:HPC advanced course 20211021.pdf|Slides 1]], [[:File:HPC advanced slides 20190528.pdf|Slides 2]]
; October 2021 — HPC Basic
: [[:File:HPC basic course 20211012.pdf|Slides]]
; June 2019 — HPC CUDA / AI (by Dell)
: [[:File:WUR CUDA 210619.pdf|CUDA]], [[:File:WUR CUDA 2 210619.pdf|CUDA 2]], [[:File:WUR AI 101 210619.pdf|AI 101]], [[:File:WUR AI 201 210619.pdf|AI 201]], [[:File:WUR Deep Learning Frameworks 210619.pdf|Deep Learning Frameworks]], [[:File:WUR Deep Learning Lab 210619.pdf|Deep Learning Lab]]
; November 2019 — HPC Basic
: [[:File:HPC basic course 20191111.pdf|Slides]]
; May 2019 — HPC Advanced
: [[:File:HPC advanced course 20190506.pdf|Slides 1]], [[:File:HPC advanced slides 20190528.pdf|Slides 2]]
; May 2019 — HPC Basic
: [[:File:HPC basic course 20190506.pdf|Slides]]
; October 2018 — HPC Advanced
: [[:File:HPC Advanced Slides 20181016.pdf|Slides 1]], [[:File:HPC advanced course 20181008.pdf|Slides 2]]
; October 2018 — HPC Basic
: [[:File:HPC basic course 20181008.pdf|Slides]]
; May 2018 — HPC Advanced
: [[:File:HPC Advanced 20180518-GD.pdf|Slides]]
; November 2017 — HPC Advanced
: [[:File:HPC Advanced course 2017-11-08-JV.pdf|Slides (Jeremie)]], [[:File:HPC Advanced course 2017-11-08-GD.pdf|Slides (Gwen)]], [[:File:Checkpointing 2017-11-08.pdf|Checkpointing]]
; October 2017 — HPC Basic
: [[:File:HPC basic course 20171025.pdf|Slides]]
; June 2017 — HPC Teaching
: [[:File:Connecting with Secure Shell to the HPC 20170606.pdf|Connecting with SSH]], [[:File:Submitting and monitoring jobs on the HPC 20170602.pdf|Submitting and monitoring jobs]]
; 2012 — Sequence Data Analysis Course
: [http://www.basgen.nl/sdac/ Course page]

== See also ==
* [[Workshops]]
* [[Tutorials]]
* [[2026 Course dates]]

Main Page

2026-05-28T13:31:48Z

Prins089:

Anunna is a [http://en.wikipedia.org/wiki/High-performance_computing High Performance Computer] (HPC) infrastructure hosted by [https://www.wur.nl/en/show/supercomputer-anunna-opens-up-more-opportunities-for-data-storage-and-artificial-intelligence-applications.htm Wageningen University & Research Centre]. It is open for use for all WUR research groups as well as other organizations, including companies, that have collaborative projects with WUR.

= About =

* [[History of the Cluster|Historical information on the startup of Anunna]]

== Access Policy ==
[[Access_Policy | Main Article: Access Policy]]

Access needs to be granted actively (by creation of an account on the cluster by FB-IT). Use of resources is limited by the scheduler. Note that the use of Anunna is not free of charge.

= Our Courses and Tutorials =
The Anunna team organizes HPC courses three times a year to strengthen basic & more advanced skills and enable users to make the most effective use of our facility.

* [[Linux Basic]]
* [[HPC Basic]]
* [[HPC Advanced]]
* [[2026 Course dates]]
* [[Tutorials]]

= Using Anunna =
* [[Tariffs |Costs associated with resource usage]]

== Getting support ==
* [[Support|Get support with using Anunna (open a ticket with the HPC team)]]

== Gaining access to Anunna==
Access to the cluster and file transfer are traditionally done via [http://en.wikipedia.org/wiki/Secure_Shell SSH and SFTP].
* [[log_in_to_B4F_cluster | Logging into cluster using ssh]]
* [[file_transfer | File transfer options]]
* [[Services | Alternative access methods, and extra features and services on Anunna]]
* [[Filesystems | Data storage methods on Anunna]]

== Using Anunna for courses (mainly jupyter notebooks) ==
* [[steps_for_courses | Steps involved to run a course on Anunna]]

= Events =

* [[Courses]] that have happened and are happening
* [[Downtime]] that will affect all users
* [[Meetings]] that may affect the policies of Anunna

= Software =
* [[Modules]]
* [[Apptainer]]
* [[Python]]
* [[R]]
* [[Julia]]

== Browser apps ==
This page provides an overview of the GUI-based applications available Anunna, including background information and practical guidance on how to access and use interactive desktops and graphical tools directly from your web browser.

* [[General overview|General Overview]]
* [[Anunna Shell Access]]
* [[Using the File browser|File Browser]]
* [[Jupyter]]
* [[RStudio|R Studio]]
* [[Linux desktop|Linux Desktop]]
* [[Requesting new software|Requesting New Software]]

== Command-line Software ==

==== Cluster Scheduler ====
Anunna uses Slurm as job scheduler.
* [[Using_Slurm | Submit jobs with Slurm]]
* [[node_usage_graph | Be aware of how much work the cluster is under right now with 'node_usage_graph']]
* [[SLURM_Compare | Rosetta Stone of Workload Managers]]

==== [[Globally installed software]] ====

==== [[ABGC_modules |ABGC specific modules]] ====

==== Installation of software by users ====
* [[Domain_specific_software_on_B4Fcluster_installation_by_users | Installing domain specific software: installation by users]]
* [[Setting local variables]]
* [[Installing_R_packages_locally | Installing R packages locally]]
* [[Setting_up_Python_virtualenv | Setting up and using a virtual environment for Python3 ]]
* [[Virtual_environment_Python_3.4_or_higher | Setting up and using a virtual environment for Python3.4 or higher ]]
* [[Installing WRF and WPS]]
* [[Running scripts on a fixed timeschedule (cron)]]

= Useful Notes =

== Being in control of Environment parameters ==

* [[Using_environment_modules | Using environment modules]]
* [[Aliases and local variables]]
* [[Setting local variables]]
* [[Setting_TMPDIR | Set a custom temporary directory location]]
* [[Installing_R_packages_locally | Installing R packages locally]]
* [[Setting_up_Python_virtualenv | Setting up and using a virtual environment for Python3 ]]
* [[Locale_settings]] (how numbers and dates are displayed)

== Controlling costs ==

* [[SACCT | using SACCT to see your costs]]
* [[get_my_bill | using the "get_my_bill" script to estimate costs]]

== Management ==
Product Owner of Anunna is Alexander van Ittersum (Wageningen UR,FB-IT, C&PS). [[User: prins089 | Fons Prinsen (Wageningen UR, FB-IT, C&PS)]] is responsible for [[Maintenance_and_Management | Maintenance and Management]] of the cluster.

* [[Roadmap | Ambitions regarding innovation, support and administration of Anunna ]]

= Miscellaneous =
* [[Bioinformatics_tips_tricks_workflows |Bioinformatics tips, tricks, and workflows]]
* [[Parallel_R_code_on_SLURM | Running parallel R code on SLURM]]
* [[Convert_between_MediaWiki_and_other_formats | Convert between MediaWiki format and other formats]]
* [[Manual GitLab | GitLab: Create projects and add scripts]]
* [[Monitoring_executions | Monitoring job execution]]
* [[Shared_folders | Working with shared folders in the Lustre file system]]
* [[Old_binaries | Running older binaries on the updated OS]]
* [[locale_settings | How to change language settings for yourself]]

= See also =
* [[Maintenance_and_Management | Maintenance and Management]]
* [[About_ABGC | About ABGC]]
* [[Computer_cluster | High Performance Computing @ABGC]]
* [[Lustre_PFS_layout | Lustre Parallel File System layout]]

= External links =
{| width="90%"
|- valign="top"
| width="30%" |
* [https://www.wur.nl/en/Value-Creation-Cooperation/Facilities/Wageningen-Shared-Research-Facilities/Our-facilities/Show/High-Performance-Computing-Cluster-HPC-Anunna.htm SRF offers a HPC facilty]
| width="30%" |
* [http://en.wikipedia.org/wiki/Scientific_Linux Scientific Linux]
* [http://en.wikipedia.org/wiki/Help:Cheatsheet Help with editing Wiki pages]
|}

How to Get Help

2026-04-14T14:15:08Z

Prins089:

This page explains how to request support from the HPC team for your work on Anunna.

== How to request support ==

=== WUR internal users ===
If you are a WUR user, please submit a support ticket via:

* [https://support.wur.nl/esc WUR support portal]
* Select the 'service': '''HPC (Anunna)'''

=== External users ===
If you do not have a WUR account, please instead send an email to:

* '''[mailto:servicedesk.it@wur.nl?subject=HPC%20(Anunna) servicedesk.it@wur.nl]'''
* Include '''"HPC"''' in the subject line

== What to include in your request ==
To help us resolve your issue as quickly as possible, please provide a clear and complete description of your problem.

Include at least:

* A '''concise description''' of the issue
* The '''steps you performed''' before the problem occurred
* Any '''error messages''' (copy/paste preferred)
* Relevant '''job IDs''', filenames, or commands used
* The '''time''' the issue occurred. Especially helpful for failed login attempts etc.

The more precise your report, the faster we can assist you.

How to Get Help

2026-04-14T14:14:41Z

Prins089:

This page explains how to request support from the HPC team for your work on Anunna.

== How to request support ==

=== WUR internal users ===
If you are a WUR user, please submit a support ticket via:

* [https://support.wur.nl/esc WUR support portal]
* Select the 'service': '''HPC (Anunna)'''

=== External users ===
If you do not have a WUR account, please instead send an email to:

* '''[mailto:servicedesk.it@wur.nl?subject=HPC%20(Anunna) servicedesk.it@wur.nl]'''
* Include '''"HPC"''' in the subject line

----

== What to include in your request ==
To help us resolve your issue as quickly as possible, please provide a clear and complete description of your problem.

Include at least:

* A '''concise description''' of the issue
* The '''steps you performed''' before the problem occurred
* Any '''error messages''' (copy/paste preferred)
* Relevant '''job IDs''', filenames, or commands used
* The '''time''' the issue occurred. Especially helpful for failed login attempts etc.

The more precise your report, the faster we can assist you.

Main Page

2026-04-14T12:50:58Z

Prins089: Add link to support page

Anunna is a [http://en.wikipedia.org/wiki/High-performance_computing High Performance Computer] (HPC) infrastructure hosted by [https://www.wur.nl/en/show/supercomputer-anunna-opens-up-more-opportunities-for-data-storage-and-artificial-intelligence-applications.htm Wageningen University & Research Centre]. It is open for use for all WUR research groups as well as other organizations, including companies, that have collaborative projects with WUR.

= About =

* [[History of the Cluster|Historical information on the startup of Anunna]]

== Access Policy ==
[[Access_Policy | Main Article: Access Policy]]

Access needs to be granted actively (by creation of an account on the cluster by FB-IT). Use of resources is limited by the scheduler. Note that the use of Anunna is not free of charge.

= Our Courses and Tutorials =
The Anunna team organizes HPC courses three times a year to strengthen basic & more advanced skills and enable users to make the most effective use of our facility.

* [[Linux Basic]]
* [[HPC Basic]]
* [[HPC Advanced]]
* [[2026 Course dates]]
* [[Tutorials]]

= Using Anunna =
* [[Tariffs |Costs associated with resource usage]]
* [[Support|Get support with using Anunna (open a ticket with the HPC team)]]

== Gaining access to Anunna==
Access to the cluster and file transfer are traditionally done via [http://en.wikipedia.org/wiki/Secure_Shell SSH and SFTP].
* [[log_in_to_B4F_cluster | Logging into cluster using ssh]]
* [[file_transfer | File transfer options]]
* [[Services | Alternative access methods, and extra features and services on Anunna]]
* [[Filesystems | Data storage methods on Anunna]]

== Using Anunna for courses (mainly jupyter notebooks) ==
* [[steps_for_courses | Steps involved to run a course on Anunna]]

= Events =

* [[Courses]] that have happened and are happening
* [[Downtime]] that will affect all users
* [[Meetings]] that may affect the policies of Anunna

= Software =
* [[Modules]]
* [[Apptainer]]
* [[Python]]
* [[R]]
* [[Julia]]

== Browser apps ==
This page provides an overview of the GUI-based applications available Anunna, including background information and practical guidance on how to access and use interactive desktops and graphical tools directly from your web browser.

* [[General overview|General Overview]]
* [[Anunna Shell Access]]
* [[Using the File browser|File Browser]]
* [[Jupyter|Featured Apps]]
* [[Jupyter]]
* [[RStudio|R Studio]]
* [[Linux desktop|Linux Desktop]]
* [[Requesting new software|Requesting New Software]]

== Command-line Software ==

==== Cluster Scheduler ====
Anunna uses Slurm as job scheduler.
* [[Using_Slurm | Submit jobs with Slurm]]
* [[node_usage_graph | Be aware of how much work the cluster is under right now with 'node_usage_graph']]
* [[SLURM_Compare | Rosetta Stone of Workload Managers]]

==== [[Globally installed software]] ====

==== [[ABGC_modules |ABGC specific modules]] ====

==== Installation of software by users ====
* [[Domain_specific_software_on_B4Fcluster_installation_by_users | Installing domain specific software: installation by users]]
* [[Setting local variables]]
* [[Installing_R_packages_locally | Installing R packages locally]]
* [[Setting_up_Python_virtualenv | Setting up and using a virtual environment for Python3 ]]
* [[Virtual_environment_Python_3.4_or_higher | Setting up and using a virtual environment for Python3.4 or higher ]]
* [[Installing WRF and WPS]]
* [[Running scripts on a fixed timeschedule (cron)]]

= Useful Notes =

== Being in control of Environment parameters ==

* [[Using_environment_modules | Using environment modules]]
* [[Aliases and local variables]]
* [[Setting local variables]]
* [[Setting_TMPDIR | Set a custom temporary directory location]]
* [[Installing_R_packages_locally | Installing R packages locally]]
* [[Setting_up_Python_virtualenv | Setting up and using a virtual environment for Python3 ]]
* [[Locale_settings]] (how numbers and dates are displayed)

== Controlling costs ==

* [[SACCT | using SACCT to see your costs]]
* [[get_my_bill | using the "get_my_bill" script to estimate costs]]

== Management ==
Product Owner of Anunna is Alexander van Ittersum (Wageningen UR,FB-IT, C&PS). [[User: prins089 | Fons Prinsen (Wageningen UR, FB-IT, C&PS)]] is responsible for [[Maintenance_and_Management | Maintenance and Management]] of the cluster.

* [[Roadmap | Ambitions regarding innovation, support and administration of Anunna ]]

= Miscellaneous =
* [[Bioinformatics_tips_tricks_workflows |Bioinformatics tips, tricks, and workflows]]
* [[Parallel_R_code_on_SLURM | Running parallel R code on SLURM]]
* [[Convert_between_MediaWiki_and_other_formats | Convert between MediaWiki format and other formats]]
* [[Manual GitLab | GitLab: Create projects and add scripts]]
* [[Monitoring_executions | Monitoring job execution]]
* [[Shared_folders | Working with shared folders in the Lustre file system]]
* [[Old_binaries | Running older binaries on the updated OS]]
* [[locale_settings | How to change language settings for yourself]]

= See also =
* [[Maintenance_and_Management | Maintenance and Management]]
* [[About_ABGC | About ABGC]]
* [[Computer_cluster | High Performance Computing @ABGC]]
* [[Lustre_PFS_layout | Lustre Parallel File System layout]]

= External links =
{| width="90%"
|- valign="top"
| width="30%" |
* [https://www.wur.nl/en/Value-Creation-Cooperation/Facilities/Wageningen-Shared-Research-Facilities/Our-facilities/Show/High-Performance-Computing-Cluster-HPC-Anunna.htm SRF offers a HPC facilty]
| width="30%" |
* [http://en.wikipedia.org/wiki/Scientific_Linux Scientific Linux]
* [http://en.wikipedia.org/wiki/Help:Cheatsheet Help with editing Wiki pages]
|}

How to Get Help

2026-04-14T12:48:38Z

Prins089: Support page written

This page explains how to request support from the HPC team for your work on Anunna.

== How to Request Support ==

=== WUR Internal Users ===
If you are a WUR user, please submit a support ticket via:

* [https://support.wur.nl/esc WUR Support Portal]
* Select the 'service': '''HPC (Anunna)'''

=== External Users ===
If you do not have a WUR account, please instead send an email to:

* '''[mailto:servicedesk.it@wur.nl?subject=HPC%20(Anunna) servicedesk.it@wur.nl]'''
* Include '''"HPC"''' in the subject line

----

== What to Include in Your Request ==
To help us resolve your issue as quickly as possible, please provide a clear and complete description of your problem.

Include at least:

* A '''concise description''' of the issue
* The '''steps you performed''' before the problem occurred
* Any '''error messages''' (copy/paste preferred)
* Relevant '''job IDs''', filenames, or commands used
* The '''time''' the issue occurred. Especially helpful for failed login attempts etc.

The more precise your report, the faster we can assist you.

How to Get Help

2026-04-14T12:44:26Z

Prins089: Created page with "Support"

Support

Archival Storage

2026-03-19T09:26:45Z

Prins089:

= Tapeworm: Automated tape-archival of old datasets =

=== https://tapeworm.anunna.wur.nl/ ===

Tapeworm helps you manage data on <code>/archive</code> by identifying datasets that are no longer actively used and preparing them for tape archival.
The goal is simple: keep our warm storage available for active work, while safely preserving older data on tape.

With Tapeworm, you can:
* See which of your datasets are being considered for tape archival
* Review planned moves before they happen
* Approve, snooze, or block moves when needed
* Add metadata to help describe archived datasets. The metadata is included on tape and can be used to view/retrieve from tape, should you need to do so in the future

If you do nothing, Tapeworm will continue with the planned move after the review period.
That is why we recommend checking your pending actions regularly. You will also receive notification emails about pending actions.

From time to time, the user pages may temporarily be unavailable during maintenance. In that case, Tapeworm will show a short maintenance page instead of the normal interface.

== How Tapeworm works ==

# Tapeworm scans <code>/archive</code> and builds an index of paths and filesystem metadata.
# A dataset discovery step groups those paths into datasets, determines size, owner, and last active use, and makes them available in the GUI. Very small datasets are filtered out and will not be shown.
# A policy engine checks which discovered datasets look stale (for example: 60+ days old and larger than 1GB).
# Matching datasets are marked as planned and shown in your overview.
# You will be notified by email that Tapeworm plans to move data you own
# You can review and change what should happen, or block the move(s) entirely
# If no action is taken, after a wait period of 4 weeks, planned moves can become scheduled and then executed.
# Data is moved to tape, and removed from /archive/

== Who sees what? ==

* Regular users see only their own datasets and actions.
* Group admins/contacts see data for their configured group(s), in addition to their own data.

== User pages ==

=== 1) Overview ===
This is your action page. It shows items that currently need your decision.
[[File:Screenshot from 2026-03-17 15-19-46.png|none|thumb|1400x1400px]]
For each candidate, you can:
* Approve: proceed with the tape move. It will schedule for the next day
* Deny: stop this move, configure an override for this path. Tapeworm will not try to move this dataset/path again, until you choose to remove the override
* Snooze: postpone the decision to a future date
* Edit metadata: add key/value notes for archived data. These values are included on tape and can be used to view/retrieve datasets on tape

You can also select multiple rows and apply actions in bulk.

=== 2) Datasets ===
This page shows your discovered datasets, their sizes, and last activity times. The application has no concept of what data belongs together and should be considered a 'dataset'. If the selections on this page are wrong, you can change how Tapeworm should handle these datasets instead.
[[File:Screenshot from 2026-03-17 15-20-23.png|none|thumb|1400x1400px]]
Important:
* If a dataset already has an active move candidate, scheduling controls are disabled.
The dataset list is informational; move decisions are handled through the Schedule page.

=== 3) Schedule ===
This page shows move candidates and their status over time.
[[File:Screenshot from 2026-03-17 15-20-58.png|none|thumb|1400x1400px]]
Common statuses:
* Planned: under review
* Scheduled: move is planned for a specific date
* Executing / Tape staged / On tape: move is in progress or completed
* Error: move needs admin attention. You may be contacted, maybe we resolve it ourselves :)

Once a move is already executing or completed, schedule-changing actions are locked.

=== 4) Overrides ===
Overrides tell Tapeworm to ignore specific paths in future planning.
[[File:Screenshot from 2026-03-17 15-21-49.png|none|thumb|1400x1400px]]
Use overrides when:
* a project is still active and needs to remain on /archive
* policy suggestions are not appropriate for that location

If you agree that the dataset can in principle be moved to tape, but you don't (yet) know when, you can choose to postpone/snooze the archival instead of overriding it.

Overrides apply to the selected path and everything below it.

=== 5) History ===
This page shows completed archival moves.
When a dataset has been successfully archived and finalized, it is removed from active scheduling pages and moved into history.
[[File:Screenshot from 2026-03-17 15-24-40.png|none|thumb|1400x1400px]]

== Group pages ==

Group admins have a separate set of pages for their group scope:
* Group overview
* Group datasets
* Group schedule
* Group overrides
* Group history

If you manage more than one group, you can switch group scope in the selector at the top of the group pages.

== Notifications (email) ==

Tapeworm sends email updates when actions are pending, dates are approaching, or move state changes happen.

Emails typically include:
* Dataset path
* Size
* Last activity
* Current status
* Review/scheduled date

Notification types you may receive:
* Action required: please approve, snooze, or deny
* Reminder: review date is approaching
* Informational: move status changed (for example scheduled, staging, or completed)
* Escalation: sent to group contacts when no user response is received

Please read these emails carefully — they are your chance to adjust decisions before execution.

== Best practices for users ==

* Check your Overview page regularly
* Use Snooze if you need time to validate impact
* Add metadata when approving important datasets
* Use Overrides for known and persisting exceptions
* If unsure, contact HPC support before a scheduled move date

== FAQ ==

=== What happens if I do nothing? ===
Planned items can move forward automatically after the review window (4 weeks)

=== Can I undo after tape staging? ===
Not directly in Tapeworm. Retrieval is done via the tape/iRODS workflow.
See: https://irods.wur.nl/userguide/tape_retrieval/

=== What does “completed” mean? ===
Completed means Tapeworm saw the tape workflow finish and finalized the move.
Before finalization, the system verifies the archive in iRODS and only then removes the staged source copy.

=== Why is an action button disabled? ===
Usually because the move has already progressed (executing/staged/on tape/error), so schedule edits are no longer valid.

=== Why do some paths on /archive/ not appear as datasets in Tapeworm? ===
Tapeworm only shows paths that are discovered as datasets and pass a minimum-size threshold. Very small paths, single text files, and other tiny items are intentionally filtered out.

== Need help? ==
If anything is unclear, or you think a move is incorrect but you cannot alter it in the provided GUI, please open an HPC support ticket.

Archival Storage

2026-03-17T14:25:07Z

Prins089: images updated to new GUI

= Tapeworm: Automated tape-archival of old datasets =

<div style="border:2px solid #d32f2f; background:#ffebee; padding:12px; margin:12px 0;">
Under construction:
<ul style="margin:8px 0 0 18px;">
<li>This documentation page is under construction and may still contain some gaps.</li>
<li>The Tapeworm application will be "In Production" from March 19.</li>
</ul>
</div>

=== https://tapeworm.anunna.wur.nl/ ===

Tapeworm helps you manage data on <code>/archive</code> by identifying datasets that are no longer actively used and preparing them for tape archival.
The goal is simple: keep our warm storage available for active work, while safely preserving older data on tape.

With Tapeworm, you can:
* See which of your datasets are being considered for tape archival
* Review planned moves before they happen
* Approve, snooze, or block moves when needed
* Add metadata to help describe archived datasets. The metadata is included on tape and can be used to view/retrieve from tape, should you need to do so in the future

If you do nothing, Tapeworm will continue with the planned move after the review period.
That is why we recommend checking your pending actions regularly. You will also receive notification emails about pending actions.

From time to time, the user pages may temporarily be unavailable during maintenance. In that case, Tapeworm will show a short maintenance page instead of the normal interface.

== How Tapeworm works ==

# Tapeworm scans <code>/archive</code> and builds an index of paths and filesystem metadata.
# A dataset discovery step groups those paths into datasets, determines size, owner, and last active use, and makes them available in the GUI. Very small datasets are filtered out and will not be shown.
# A policy engine checks which discovered datasets look stale (for example: 60+ days old and larger than 1GB).
# Matching datasets are marked as planned and shown in your overview.
# You will be notified by email that Tapeworm plans to move data you own
# You can review and change what should happen, or block the move(s) entirely
# If no action is taken, after a wait period of 4 weeks, planned moves can become scheduled and then executed.
# Data is moved to tape, and removed from /archive/

== Who sees what? ==

* Regular users see only their own datasets and actions.
* Group admins/contacts see data for their configured group(s), in addition to their own data.

== User pages ==

=== 1) Overview ===
This is your action page. It shows items that currently need your decision.
[[File:Screenshot from 2026-03-17 15-19-46.png|none|thumb|1400x1400px]]
For each candidate, you can:
* Approve: proceed with the tape move. It will schedule for the next day
* Deny: stop this move, configure an override for this path. Tapeworm will not try to move this dataset/path again, until you choose to remove the override
* Snooze: postpone the decision to a future date
* Edit metadata: add key/value notes for archived data. These values are included on tape and can be used to view/retrieve datasets on tape

You can also select multiple rows and apply actions in bulk.

=== 2) Datasets ===
This page shows your discovered datasets, their sizes, and last activity times. The application has no concept of what data belongs together and should be considered a 'dataset'. If the selections on this page are wrong, you can change how Tapeworm should handle these datasets instead.
[[File:Screenshot from 2026-03-17 15-20-23.png|none|thumb|1400x1400px]]
Important:
* If a dataset already has an active move candidate, scheduling controls are disabled.
The dataset list is informational; move decisions are handled through the Schedule page.

=== 3) Schedule ===
This page shows move candidates and their status over time.
[[File:Screenshot from 2026-03-17 15-20-58.png|none|thumb|1400x1400px]]
Common statuses:
* Planned: under review
* Scheduled: move is planned for a specific date
* Executing / Tape staged / On tape: move is in progress or completed
* Error: move needs admin attention. You may be contacted, maybe we resolve it ourselves :)

Once a move is already executing or completed, schedule-changing actions are locked.

=== 4) Overrides ===
Overrides tell Tapeworm to ignore specific paths in future planning.
[[File:Screenshot from 2026-03-17 15-21-49.png|none|thumb|1400x1400px]]
Use overrides when:
* a project is still active and needs to remain on /archive
* policy suggestions are not appropriate for that location

If you agree that the dataset can in principle be moved to tape, but you don't (yet) know when, you can choose to postpone/snooze the archival instead of overriding it.

Overrides apply to the selected path and everything below it.

=== 5) History ===
This page shows completed archival moves.
When a dataset has been successfully archived and finalized, it is removed from active scheduling pages and moved into history.
[[File:Screenshot from 2026-03-17 15-24-40.png|none|thumb|1400x1400px]]

== Group pages ==

Group admins have a separate set of pages for their group scope:
* Group overview
* Group datasets
* Group schedule
* Group overrides
* Group history

If you manage more than one group, you can switch group scope in the selector at the top of the group pages.

== Notifications (email) ==

Tapeworm sends email updates when actions are pending, dates are approaching, or move state changes happen.

Emails typically include:
* Dataset path
* Size
* Last activity
* Current status
* Review/scheduled date

Notification types you may receive:
* Action required: please approve, snooze, or deny
* Reminder: review date is approaching
* Informational: move status changed (for example scheduled, staging, or completed)
* Escalation: sent to group contacts when no user response is received

Please read these emails carefully — they are your chance to adjust decisions before execution.

== Best practices for users ==

* Check your Overview page regularly
* Use Snooze if you need time to validate impact
* Add metadata when approving important datasets
* Use Overrides for known and persisting exceptions
* If unsure, contact HPC support before a scheduled move date

== FAQ ==

=== What happens if I do nothing? ===
Planned items can move forward automatically after the review window (4 weeks)

=== Can I undo after tape staging? ===
Not directly in Tapeworm. Retrieval is done via the tape/iRODS workflow.
See: https://irods.wur.nl/userguide/tape_retrieval/

=== What does “completed” mean? ===
Completed means Tapeworm saw the tape workflow finish and finalized the move.
Before finalization, the system verifies the archive in iRODS and only then removes the staged source copy.

=== Why is an action button disabled? ===
Usually because the move has already progressed (executing/staged/on tape/error), so schedule edits are no longer valid.

=== Why do some paths on /archive/ not appear as datasets in Tapeworm? ===
Tapeworm only shows paths that are discovered as datasets and pass a minimum-size threshold. Very small paths, single text files, and other tiny items are intentionally filtered out.

== Need help? ==
If anything is unclear, or you think a move is incorrect but you cannot alter it in the provided GUI, please open an HPC support ticket.

File:Screenshot from 2026-03-17 15-24-40.png

2026-03-17T14:24:51Z

Prins089:

File:Screenshot from 2026-03-17 15-21-49.png

2026-03-17T14:22:15Z

Prins089:

File:Screenshot from 2026-03-17 15-20-58.png

2026-03-17T14:21:12Z

Prins089:

File:Screenshot from 2026-03-17 15-20-23.png

2026-03-17T14:20:37Z

Prins089:

File:Screenshot from 2026-03-17 15-19-46.png

2026-03-17T14:20:02Z

Prins089:

Archival Storage

2026-03-17T14:05:42Z

Prins089:

= Tapeworm: Automated tape-archival of old datasets =

<div style="border:2px solid #d32f2f; background:#ffebee; padding:12px; margin:12px 0;">
Under construction:
<ul style="margin:8px 0 0 18px;">
<li>This documentation page is under construction and may still contain some gaps.</li>
<li>The Tapeworm application will be "In Production" from March 19.</li>
</ul>
</div>

=== https://tapeworm.anunna.wur.nl/ ===

Tapeworm helps you manage data on <code>/archive</code> by identifying datasets that are no longer actively used and preparing them for tape archival.
The goal is simple: keep our warm storage available for active work, while safely preserving older data on tape.

With Tapeworm, you can:
* See which of your datasets are being considered for tape archival
* Review planned moves before they happen
* Approve, snooze, or block moves when needed
* Add metadata to help describe archived datasets. The metadata is included on tape and can be used to view/retrieve from tape, should you need to do so in the future

If you do nothing, Tapeworm will continue with the planned move after the review period.
That is why we recommend checking your pending actions regularly. You will also receive notification emails about pending actions.

From time to time, the user pages may temporarily be unavailable during maintenance. In that case, Tapeworm will show a short maintenance page instead of the normal interface.

== How Tapeworm works ==

# Tapeworm scans <code>/archive</code> and builds an index of paths and filesystem metadata.
# A dataset discovery step groups those paths into datasets, determines size, owner, and last active use, and makes them available in the GUI. Very small datasets are filtered out and will not be shown.
# A policy engine checks which discovered datasets look stale (for example: 60+ days old and larger than 1GB).
# Matching datasets are marked as planned and shown in your overview.
# You will be notified by email that Tapeworm plans to move data you own
# You can review and change what should happen, or block the move(s) entirely
# If no action is taken, after a wait period of 4 weeks, planned moves can become scheduled and then executed.
# Data is moved to tape, and removed from /archive/

== Who sees what? ==

* Regular users see only their own datasets and actions.
* Group admins/contacts see data for their configured group(s), in addition to their own data.

== User pages ==

=== 1) Overview ===
This is your action page. It shows items that currently need your decision.
[[File:Tapeworm screen1.png|frame|left]]
For each candidate, you can:
* Approve: proceed with the tape move. It will schedule for the next day
* Deny: stop this move, configure an override for this path. Tapeworm will not try to move this dataset/path again, until you choose to remove the override
* Snooze: postpone the decision to a future date
* Edit metadata: add key/value notes for archived data. These values are included on tape and can be used to view/retrieve datasets on tape

You can also select multiple rows and apply actions in bulk.

=== 2) Datasets ===
This page shows your discovered datasets, their sizes, and last activity times. The application has no concept of what data belongs together and should be considered a 'dataset'. If the selections on this page are wrong, you can change how Tapeworm should handle these datasets instead.

[[File:User datasets.png|frame|none]]

Important:
* If a dataset already has an active move candidate, scheduling controls are disabled.
The dataset list is informational; move decisions are handled through the Schedule page.

=== 3) Schedule ===
This page shows move candidates and their status over time.

[[File:User schedule.png|frame|none]]

Common statuses:
* Planned: under review
* Scheduled: move is planned for a specific date
* Executing / Tape staged / On tape: move is in progress or completed
* Error: move needs admin attention. You may be contacted, maybe we resolve it ourselves :)

Once a move is already executing or completed, schedule-changing actions are locked.

=== 4) Overrides ===
Overrides tell Tapeworm to ignore specific paths in future planning.

[[File:User override.png|frame|none]]

Use overrides when:
* a project is still active and needs to remain on /archive
* policy suggestions are not appropriate for that location

If you agree that the dataset can in principle be moved to tape, but you don't (yet) know when, you can choose to postpone/snooze the archival instead of overriding it.

Overrides apply to the selected path and everything below it.

=== 5) History ===
This page shows completed archival moves.
When a dataset has been successfully archived and finalized, it is removed from active scheduling pages and moved into history.

[[File:User history.png|frame|none]]

== Group pages ==

Group admins have a separate set of pages for their group scope:
* Group overview
* Group datasets
* Group schedule
* Group overrides
* Group history

If you manage more than one group, you can switch group scope in the selector at the top of the group pages.

== Notifications (email) ==

Tapeworm sends email updates when actions are pending, dates are approaching, or move state changes happen.

Emails typically include:
* Dataset path
* Size
* Last activity
* Current status
* Review/scheduled date

Notification types you may receive:
* Action required: please approve, snooze, or deny
* Reminder: review date is approaching
* Informational: move status changed (for example scheduled, staging, or completed)
* Escalation: sent to group contacts when no user response is received

Please read these emails carefully — they are your chance to adjust decisions before execution.

== Best practices for users ==

* Check your Overview page regularly
* Use Snooze if you need time to validate impact
* Add metadata when approving important datasets
* Use Overrides for known and persisting exceptions
* If unsure, contact HPC support before a scheduled move date

== FAQ ==

=== What happens if I do nothing? ===
Planned items can move forward automatically after the review window (4 weeks)

=== Can I undo after tape staging? ===
Not directly in Tapeworm. Retrieval is done via the tape/iRODS workflow.
See: https://irods.wur.nl/userguide/tape_retrieval/

=== What does “completed” mean? ===
Completed means Tapeworm saw the tape workflow finish and finalized the move.
Before finalization, the system verifies the archive in iRODS and only then removes the staged source copy.

=== Why is an action button disabled? ===
Usually because the move has already progressed (executing/staged/on tape/error), so schedule edits are no longer valid.

=== Why do some paths on /archive/ not appear as datasets in Tapeworm? ===
Tapeworm only shows paths that are discovered as datasets and pass a minimum-size threshold. Very small paths, single text files, and other tiny items are intentionally filtered out.

== Need help? ==
If anything is unclear, or you think a move is incorrect but you cannot alter it in the provided GUI, please open an HPC support ticket.

Archival Storage

2026-03-17T14:04:56Z

Prins089:

= Tapeworm: Automated tape-archival of old datasets =

<div style="border:2px solid #d32f2f; background:#ffebee; padding:12px; margin:12px 0;">
Under construction:
<ul style="margin:8px 0 0 18px;">
<li>This documentation page is under construction and may still contain some gaps.</li>
<li>The Tapeworm application will be "In Production" from March 19.</li>
</ul>
</div>

=== https://tapeworm.anunna.wur.nl/ ===

Tapeworm helps you manage data on <code>/archive</code> by identifying datasets that are no longer actively used and preparing them for tape archival.
The goal is simple: keep our warm storage available for active work, while safely preserving older data on tape.

With Tapeworm, you can:
* See which of your datasets are being considered for tape archival
* Review planned moves before they happen
* Approve, snooze, or block moves when needed
* Add metadata to help describe archived datasets. The metadata is included on tape and can be used to view/retrieve from tape, should you need to do so in the future

If you do nothing, Tapeworm will continue with the planned move after the review period.
That is why we recommend checking your pending actions regularly. You will also receive notification emails about pending actions.

From time to time, the user pages may temporarily be unavailable during maintenance. In that case, Tapeworm will show a short maintenance page instead of the normal interface.

== How Tapeworm works ==

# Tapeworm scans <code>/archive</code> and builds an index of paths and filesystem metadata.
# A dataset discovery step groups those paths into datasets, determines size, owner, and last active use, and makes them available in the GUI. Very small datasets are filtered out and will not be shown.
# A policy engine checks which discovered datasets look stale (for example: 60+ days old and larger than 1GB).
# Matching datasets are marked as planned and shown in your overview.
# You will be notified by email that Tapeworm plans to move data you own
# You can review and change what should happen, or block the move(s) entirely
# If no action is taken, after a wait period of 4 weeks, planned moves can become scheduled and then executed.
# Data is moved to tape, and removed from /archive/

== Who sees what? ==

* Regular users see only their own datasets and actions.
* Group admins/contacts see data for their configured group(s), in addition to their own data.

== User pages ==

=== 1) Overview ===
This is your action page. It shows items that currently need your decision.
[[File:Tapeworm screen1.png|none|frame]]
For each candidate, you can:
* Approve: proceed with the tape move. It will schedule for the next day
* Deny: stop this move, configure an override for this path. Tapeworm will not try to move this dataset/path again, until you choose to remove the override
* Snooze: postpone the decision to a future date
* Edit metadata: add key/value notes for archived data. These values are included on tape and can be used to view/retrieve datasets on tape

You can also select multiple rows and apply actions in bulk.

=== 2) Datasets ===
This page shows your discovered datasets, their sizes, and last activity times. The application has no concept of what data belongs together and should be considered a 'dataset'. If the selections on this page are wrong, you can change how Tapeworm should handle these datasets instead.

[[File:User datasets.png|frame|none]]

Important:
* If a dataset already has an active move candidate, scheduling controls are disabled.
The dataset list is informational; move decisions are handled through the Schedule page.

=== 3) Schedule ===
This page shows move candidates and their status over time.

[[File:User schedule.png|frame|none]]

Common statuses:
* Planned: under review
* Scheduled: move is planned for a specific date
* Executing / Tape staged / On tape: move is in progress or completed
* Error: move needs admin attention. You may be contacted, maybe we resolve it ourselves :)

Once a move is already executing or completed, schedule-changing actions are locked.

=== 4) Overrides ===
Overrides tell Tapeworm to ignore specific paths in future planning.

[[File:User override.png|frame|none]]

Use overrides when:
* a project is still active and needs to remain on /archive
* policy suggestions are not appropriate for that location

If you agree that the dataset can in principle be moved to tape, but you don't (yet) know when, you can choose to postpone/snooze the archival instead of overriding it.

Overrides apply to the selected path and everything below it.

=== 5) History ===
This page shows completed archival moves.
When a dataset has been successfully archived and finalized, it is removed from active scheduling pages and moved into history.

[[File:User history.png|frame|none]]

== Group pages ==

Group admins have a separate set of pages for their group scope:
* Group overview
* Group datasets
* Group schedule
* Group overrides
* Group history

If you manage more than one group, you can switch group scope in the selector at the top of the group pages.

== Notifications (email) ==

Tapeworm sends email updates when actions are pending, dates are approaching, or move state changes happen.

Emails typically include:
* Dataset path
* Size
* Last activity
* Current status
* Review/scheduled date

Notification types you may receive:
* Action required: please approve, snooze, or deny
* Reminder: review date is approaching
* Informational: move status changed (for example scheduled, staging, or completed)
* Escalation: sent to group contacts when no user response is received

Please read these emails carefully — they are your chance to adjust decisions before execution.

== Best practices for users ==

* Check your Overview page regularly
* Use Snooze if you need time to validate impact
* Add metadata when approving important datasets
* Use Overrides for known and persisting exceptions
* If unsure, contact HPC support before a scheduled move date

== FAQ ==

=== What happens if I do nothing? ===
Planned items can move forward automatically after the review window (4 weeks)

=== Can I undo after tape staging? ===
Not directly in Tapeworm. Retrieval is done via the tape/iRODS workflow.
See: https://irods.wur.nl/userguide/tape_retrieval/

=== What does “completed” mean? ===
Completed means Tapeworm saw the tape workflow finish and finalized the move.
Before finalization, the system verifies the archive in iRODS and only then removes the staged source copy.

=== Why is an action button disabled? ===
Usually because the move has already progressed (executing/staged/on tape/error), so schedule edits are no longer valid.

=== Why do some paths on /archive/ not appear as datasets in Tapeworm? ===
Tapeworm only shows paths that are discovered as datasets and pass a minimum-size threshold. Very small paths, single text files, and other tiny items are intentionally filtered out.

== Need help? ==
If anything is unclear, or you think a move is incorrect but you cannot alter it in the provided GUI, please open an HPC support ticket.

File:Tapeworm screen1.png

2026-03-17T14:04:44Z

Prins089:

tapeworm_screen1

Archival Storage

2026-03-17T13:58:21Z

Prins089:

= Tapeworm: Automated tape-archival of old datasets =

<div style="border:2px solid #d32f2f; background:#ffebee; padding:12px; margin:12px 0;">
Under construction:
<ul style="margin:8px 0 0 18px;">
<li>This documentation page is under construction and may still contain some gaps.</li>
<li>The Tapeworm application will be "In Production" from March 19.</li>
</ul>
</div>

=== https://tapeworm.anunna.wur.nl/ ===

Tapeworm helps you manage data on <code>/archive</code> by identifying datasets that are no longer actively used and preparing them for tape archival.
The goal is simple: keep our warm storage available for active work, while safely preserving older data on tape.

With Tapeworm, you can:
* See which of your datasets are being considered for tape archival
* Review planned moves before they happen
* Approve, snooze, or block moves when needed
* Add metadata to help describe archived datasets. The metadata is included on tape and can be used to view/retrieve from tape, should you need to do so in the future

If you do nothing, Tapeworm will continue with the planned move after the review period.
That is why we recommend checking your pending actions regularly. You will also receive notification emails about pending actions.

From time to time, the user pages may temporarily be unavailable during maintenance. In that case, Tapeworm will show a short maintenance page instead of the normal interface.

== How Tapeworm works ==

# Tapeworm scans <code>/archive</code> and builds an index of paths and filesystem metadata.
# A dataset discovery step groups those paths into datasets, determines size, owner, and last active use, and makes them available in the GUI. Very small datasets are filtered out and will not be shown.
# A policy engine checks which discovered datasets look stale (for example: 60+ days old and larger than 1GB).
# Matching datasets are marked as planned and shown in your overview.
# You will be notified by email that Tapeworm plans to move data you own
# You can review and change what should happen, or block the move(s) entirely
# If no action is taken, after a wait period of 4 weeks, planned moves can become scheduled and then executed.
# Data is moved to tape, and removed from /archive/

== Who sees what? ==

* Regular users see only their own datasets and actions.
* Group admins/contacts see data for their configured group(s), in addition to their own data.

== User pages ==

=== 1) Overview ===
This is your action page. It shows items that currently need your decision.

[[File:User overview 3.png|frame|none]]

For each candidate, you can:
* Approve: proceed with the tape move. It will schedule for the next day
* Deny: stop this move, configure an override for this path. Tapeworm will not try to move this dataset/path again, until you choose to remove the override
* Snooze: postpone the decision to a future date
* Edit metadata: add key/value notes for archived data. These values are included on tape and can be used to view/retrieve datasets on tape

You can also select multiple rows and apply actions in bulk.

=== 2) Datasets ===
This page shows your discovered datasets, their sizes, and last activity times. The application has no concept of what data belongs together and should be considered a 'dataset'. If the selections on this page are wrong, you can change how Tapeworm should handle these datasets instead.

[[File:User datasets.png|frame|none]]

Important:
* If a dataset already has an active move candidate, scheduling controls are disabled.
The dataset list is informational; move decisions are handled through the Schedule page.

=== 3) Schedule ===
This page shows move candidates and their status over time.

[[File:User schedule.png|frame|none]]

Common statuses:
* Planned: under review
* Scheduled: move is planned for a specific date
* Executing / Tape staged / On tape: move is in progress or completed
* Error: move needs admin attention. You may be contacted, maybe we resolve it ourselves :)

Once a move is already executing or completed, schedule-changing actions are locked.

=== 4) Overrides ===
Overrides tell Tapeworm to ignore specific paths in future planning.

[[File:User override.png|frame|none]]

Use overrides when:
* a project is still active and needs to remain on /archive
* policy suggestions are not appropriate for that location

If you agree that the dataset can in principle be moved to tape, but you don't (yet) know when, you can choose to postpone/snooze the archival instead of overriding it.

Overrides apply to the selected path and everything below it.

=== 5) History ===
This page shows completed archival moves.
When a dataset has been successfully archived and finalized, it is removed from active scheduling pages and moved into history.

[[File:User history.png|frame|none]]

== Group pages ==

Group admins have a separate set of pages for their group scope:
* Group overview
* Group datasets
* Group schedule
* Group overrides
* Group history

If you manage more than one group, you can switch group scope in the selector at the top of the group pages.

== Notifications (email) ==

Tapeworm sends email updates when actions are pending, dates are approaching, or move state changes happen.

Emails typically include:
* Dataset path
* Size
* Last activity
* Current status
* Review/scheduled date

Notification types you may receive:
* Action required: please approve, snooze, or deny
* Reminder: review date is approaching
* Informational: move status changed (for example scheduled, staging, or completed)
* Escalation: sent to group contacts when no user response is received

Please read these emails carefully — they are your chance to adjust decisions before execution.

== Best practices for users ==

* Check your Overview page regularly
* Use Snooze if you need time to validate impact
* Add metadata when approving important datasets
* Use Overrides for known and persisting exceptions
* If unsure, contact HPC support before a scheduled move date

== FAQ ==

=== What happens if I do nothing? ===
Planned items can move forward automatically after the review window (4 weeks)

=== Can I undo after tape staging? ===
Not directly in Tapeworm. Retrieval is done via the tape/iRODS workflow.
See: https://irods.wur.nl/userguide/tape_retrieval/

=== What does “completed” mean? ===
Completed means Tapeworm saw the tape workflow finish and finalized the move.
Before finalization, the system verifies the archive in iRODS and only then removes the staged source copy.

=== Why is an action button disabled? ===
Usually because the move has already progressed (executing/staged/on tape/error), so schedule edits are no longer valid.

=== Why do some paths on /archive/ not appear as datasets in Tapeworm? ===
Tapeworm only shows paths that are discovered as datasets and pass a minimum-size threshold. Very small paths, single text files, and other tiny items are intentionally filtered out.

== Need help? ==
If anything is unclear, or you think a move is incorrect but you cannot alter it in the provided GUI, please open an HPC support ticket.

Archival Storage

2026-03-13T14:55:50Z

Prins089:

= Tapeworm: Automated tape-archival of old datasets =

<div style="border:2px solid #d32f2f; background:#ffebee; padding:12px; margin:12px 0;">
Under construction:
<ul style="margin:8px 0 0 18px;">
<li>This documentation page is under construction and may still contain some gaps.</li>
<li>The Tapeworm application will be "In Production" from March 19.</li>
</ul>
</div>

=== https://tapeworm.anunna.wur.nl/ ===

Tapeworm helps you manage data on <code>/archive</code> by identifying datasets that are no longer actively used and preparing them for tape archival.
The goal is simple: keep our warm storage available for active work, while safely preserving older data on tape.

With Tapeworm, you can:
* See which of your datasets are being considered for tape archival
* Review planned moves before they happen
* Approve, snooze, or block moves when needed
* Add metadata to help describe archived datasets. The metadata is included on tape and can be used to view/retrieve from tape, should you need to do so in the future

If you do nothing, Tapeworm will continue with the planned move after the review period.
That is why we recommend checking your pending actions regularly. You will also receive notification emails about pending actions.

From time to time, the user pages may temporarily be unavailable during maintenance. In that case, Tapeworm will show a short maintenance page instead of the normal interface.

== How Tapeworm works ==

# Tapeworm scans <code>/archive</code> and builds an index of paths and filesystem metadata.
# A dataset discovery step groups those paths into datasets, determines size, owner, and last active use, and makes them available in the GUI. Very small datasets are filtered out and will not be shown.
# A policy engine checks which discovered datasets look stale (for example: 30+ days old and larger than 1GB).
# Matching datasets are marked as planned and shown in your overview.
# You will be notified by email that Tapeworm plans to move data you own
# You can review and change what should happen, or block the move(s) entirely
# If no action is taken, after a wait period of 4 weeks, planned moves can become scheduled and then executed.
# Data is moved to tape, and removed from /archive/

== Who sees what? ==

* Regular users see only their own datasets and actions.
* Group admins/contacts see data for their configured group(s), in addition to their own data.

== User pages ==

=== 1) Overview ===
This is your action page. It shows items that currently need your decision.

[[File:User overview 3.png|frame|none]]

For each candidate, you can:
* Approve: proceed with the tape move. It will schedule for the next day
* Deny: stop this move, configure an override for this path. Tapeworm will not try to move this dataset/path again, until you choose to remove the override
* Snooze: postpone the decision to a future date
* Edit metadata: add key/value notes for archived data. These values are included on tape and can be used to view/retrieve datasets on tape

You can also select multiple rows and apply actions in bulk.

=== 2) Datasets ===
This page shows your discovered datasets, their sizes, and last activity times. The application has no concept of what data belongs together and should be considered a 'dataset'. If the selections on this page are wrong, you can change how Tapeworm should handle these datasets instead.

[[File:User datasets.png|frame|none]]

Important:
* If a dataset already has an active move candidate, scheduling controls are disabled.
The dataset list is informational; move decisions are handled through the Schedule page.

=== 3) Schedule ===
This page shows move candidates and their status over time.

[[File:User schedule.png|frame|none]]

Common statuses:
* Planned: under review
* Scheduled: move is planned for a specific date
* Executing / Tape staged / On tape: move is in progress or completed
* Error: move needs admin attention. You may be contacted, maybe we resolve it ourselves :)

Once a move is already executing or completed, schedule-changing actions are locked.

=== 4) Overrides ===
Overrides tell Tapeworm to ignore specific paths in future planning.

[[File:User override.png|frame|none]]

Use overrides when:
* a project is still active and needs to remain on /archive
* policy suggestions are not appropriate for that location

If you agree that the dataset can in principle be moved to tape, but you don't (yet) know when, you can choose to postpone/snooze the archival instead of overriding it.

Overrides apply to the selected path and everything below it.

=== 5) History ===
This page shows completed archival moves.
When a dataset has been successfully archived and finalized, it is removed from active scheduling pages and moved into history.

[[File:User history.png|frame|none]]

== Group pages ==

Group admins have a separate set of pages for their group scope:
* Group overview
* Group datasets
* Group schedule
* Group overrides
* Group history

If you manage more than one group, you can switch group scope in the selector at the top of the group pages.

== Notifications (email) ==

Tapeworm sends email updates when actions are pending, dates are approaching, or move state changes happen.

Emails typically include:
* Dataset path
* Size
* Last activity
* Current status
* Review/scheduled date

Notification types you may receive:
* Action required: please approve, snooze, or deny
* Reminder: review date is approaching
* Informational: move status changed (for example scheduled, staging, or completed)
* Escalation: sent to group contacts when no user response is received

Please read these emails carefully — they are your chance to adjust decisions before execution.

== Best practices for users ==

* Check your Overview page regularly
* Use Snooze if you need time to validate impact
* Add metadata when approving important datasets
* Use Overrides for known and persisting exceptions
* If unsure, contact HPC support before a scheduled move date

== FAQ ==

=== What happens if I do nothing? ===
Planned items can move forward automatically after the review window (4 weeks)

=== Can I undo after tape staging? ===
Not directly in Tapeworm. Retrieval is done via the tape/iRODS workflow.
See: https://irods.wur.nl/userguide/tape_retrieval/

=== What does “completed” mean? ===
Completed means Tapeworm saw the tape workflow finish and finalized the move.
Before finalization, the system verifies the archive in iRODS and only then removes the staged source copy.

=== Why is an action button disabled? ===
Usually because the move has already progressed (executing/staged/on tape/error), so schedule edits are no longer valid.

=== Why do some paths on /archive/ not appear as datasets in Tapeworm? ===
Tapeworm only shows paths that are discovered as datasets and pass a minimum-size threshold. Very small paths, single text files, and other tiny items are intentionally filtered out.

== Need help? ==
If anything is unclear, or you think a move is incorrect but you cannot alter it in the provided GUI, please open an HPC support ticket.

Using a hardware key for better security

2026-03-05T08:25:26Z

Prins089:

WUR employees can get a Yubikey hardware key for free at the servicedesk in Forum.

With that key, you can implement multifactor authentication for your SSH connections.

Depending on you choices and setup, you can make it very secure, so that without the key, pin and password your SSH key won't be able to be used.

The steps below are adaptations of https://developers.yubico.com/SSH/Securing_SSH_with_FIDO2.html

=== Different levels of security/annoyance ===
There are different levels of security you can apply, each being more secure, but also introducing an extra step before you have an active session.

There a three "interactions" that can be used:

# Enforce/use a password to unlock your SSH key
# Enforce/use a PIN to unlock the hardware key
# Enforce/use touching the hardware key to get access

This then leads to the following 4 scenarios:

# Use SSH key password, pin and touch for each new SSH session (no SSH agent)
# Use pin and touch for each new SSH session (use SSH agent for password)
# Use touch for each new SSH session (use SSH agent for password, but no PIN enforcement in key)
# Use SSH key password and touch for first SSH session (pass in SSH agent, no PIN and touch enforcement in key)

The last one is the least intrusive, and as an attacker would need physical access to your device to circumvent your security, this is probably fine for most people.

This is thus the scenario that we'll describe below in detail.

For scenario 1 & 2, add <code>-O verify-required</code> to the <code>ssh-keygen</code> command to enforce PIN enforcement in key.

For scenarios 1, 2 & 3, do not add <code>-O no-touch-required</code> to the <code>ssh-keygen</code> command to enforce touch enforcement in key.

=== Linux ===

==== Create your key: ====
(do this on your laptop or desktop)
ssh-keygen -t ed25519-sk -O resident -O no-touch-required -O application=ssh:anunna -C "[Your comment to identify this key on the server]"
The options are:

* <code>-t ed25519-sk</code> : Type of key, this is the more secure option
* <code>-O resident</code> : Store the SSH key on your hardware key, makes it easier to use on another machine
* <code>-O no-touch-required</code> : No need to touch the hardware key every time
* <code>-O application=ssh:anunna.wur.nl</code> : identifier for the key on your hardware key
* <code>-C "[Your comment to identify this key on the server]"</code> : identifier for the key on the server

An example exchange looks like this:
user001@LAPTOP:~ % ssh-keygen -t ed25519-sk -O resident -O no-touch-required -O application=ssh:anunna -C "first.lastname@wur.nl"
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter PIN for authenticator:
You may need to touch your authenticator again to authorize key generation.
Enter file in which to save the key (/Users/user001/.ssh/id_ed25519_sk):
Enter passphrase for "/Users/user001/.ssh/id_ed25519_sk" (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /Users/user001/.ssh/id_ed25519_sk
Your public key has been saved in /Users/user001/.ssh/id_ed25519_sk.pub

==== Copy your key: ====
To be able to log in, the server will have to have the public part of your key.

For that, copy the contents of your public key, in my case <code>/Users/user001/.ssh/id_ed25519_sk.pub</code> to <code>$HOME/.ssh/authorized_keys</code>

To allow touchless entry, we'll need to tell the SSH daemon to allow that:
# Copy over key
ssh login.anunna.wur.nl "umask 0077; mkdir -p ~/.ssh; echo 'no-touch-required $(cat ~/.ssh/id_ed25519_sk.pub)' >> ~/.ssh/authorized_keys"
# Check for key
ssh login.anunna.wur.nl 'tail -1 .ssh/authorized_keys'

==== Key use ====
On the machine that you created the key, there will be a stub file added to point ssh-agent to the hardware key, so that machine should work out of the box.

On other machines, you can load the private SSH key from the hardware key with
ssh-add -K
After this all, you should be able to login without issue.

=== MacOS ===
For MacOS, we can mostly do the same as for Linux, except that we will have to install openssh, as the default SSH stack doesn't work with hardware keys.

So:
brew install openssh
Besides that, you will have to replace the MacOS ssh-agent with the one from openssh:
# Download the plist
curl --silent --output ~/Library/LaunchAgents/com.homebrew.ssh-agent.plist <nowiki>https://gist.githubusercontent.com/partikus/cd45013b1274af8ae63b17030d89176c/raw/d34dfae3872dec38137e8a51780fbcb95380034c/com.homebrew.ssh-agent.plist</nowiki>

# disable the default ssh-agent
launchctl disable gui/$UID/com.openssh.ssh-agent
launchctl stop gui/$UID/com.openssh.ssh-agent

# enable the homebrew ssh-agent
launchctl bootstrap gui/$UID ~/Library/LaunchAgents/com.homebrew.ssh-agent.plist

# verify installation (you should see com.homebrew.ssh-agent)
launchctl list | grep ssh
If there are issues with the MacOS ssh-agent, try a reboot, do another verify, and only the homebrew one should be present.

After this, open a new terminal , and follow the Linux flow.

=== Windows ===
(needs to be filled by a Windows user)

Archival Storage

2026-03-03T15:39:52Z

Prins089:

= Tapeworm: Automated tape-archival of old datasets =

<div style="border:2px solid #d32f2f; background:#ffebee; padding:12px; margin:12px 0;">
Warning:
<ul style="margin:8px 0 0 18px;">
<li>This documentation page is under construction and may contain errors.</li>
<li>The Tapeworm application is in beta and may contain errors.</li>
</ul>
</div>

=== https://tapeworm.anunna.wur.nl/ ===

Tapeworm helps you manage data on <code>/archive</code> by identifying datasets that are no longer actively used and preparing them for tape archival.
The goal is simple: keep our warm storage available for active work, while safely preserving older data on tape.

With Tapeworm, you can:
* See which of your datasets are being considered for tape archival
* Review planned moves before they happen
* Approve, snooze, or block moves when needed
* Add metadata to help describe archived datasets. The metadata is included on tape and can be used to view/retrieve from tape, should you need to do so in the future

If you do nothing, Tapeworm will continue with the planned move after the review period.
That is why we recommend checking your pending actions regularly. You will also receive notification emails about pending actions.

== How Tapeworm works ==

# Tapeworm scans <code>/archive</code> and builds an index of datasets, size, owner, and last active use.
# A policy engine checks which datasets look stale (for example: 30+ days old and larger than 1GB).
# Matching datasets are marked as planned and shown in your overview.
# You will be notified by email that Tapeworm plans to move data you own
# You can review and change what should happen, or block the move(s) entirely
# If no action is taken, after a wait period of 4 weeks, planned moves can become scheduled and then executed.
# Data is moved to tape, and removed from /archive/

== Who sees what? ==

* Regular users see only their own datasets and actions.
* Group admins/contacts see data for their configured group(s), in addition to their own data.

== User pages ==

=== 1) Overview ===
This is your action page. It shows items that currently need your decision.

[[File:User overview 3.png|left|frame]]

For each candidate, you can:
* Approve: proceed with the tape move. It will schedule for the next day
* Deny: stop this move, configure an override for this path. Tapeworm will not try to move this dataset/path again, until you choose to remove the override
* Snooze: postpone the decision to a future date
* Edit metadata: add key/value notes for archived data. These values are included on tape and can be used to view/retrieve datasets on tape

You can also select multiple rows and apply actions in bulk.

=== 2) Datasets ===
This page shows your discovered datasets, their sizes, and last activity times. The application has no concept of what data belongs together and should be considered a 'dataset'. If the selections on this page are wrong, you can change how Tapeworm should handle these datasets instead.

[[File:User datasets.png|left|frame]]

Important:
* If a dataset already has an active move candidate, scheduling controls are disabled.
The dataset list is informational; move decisions are handled through the Schedule page.

=== 3) Schedule ===
This page shows move candidates and their status over time.

[[File:User schedule.png|left|frame]]

Common statuses:
* Planned (or planned + notified): under review
* Scheduled: move is planned for a specific date
* Executing / Tape staged / On tape: move is in progress or completed
* Error: move needs admin attention. You may be contacted, maybe we resolve it ourselves :)

Once a move is already executing or completed, schedule-changing actions are locked.

=== 4) Overrides ===
Overrides tell Tapeworm to ignore specific paths in future planning.

[[File:User override.png|left|frame]]

Use overrides when:
* a project is still active and needs to remain on /archive
* policy suggestions are not appropriate for that location

If you agree that the dataset can in principle be moved to tape, but you don't (yet) know when, you can choose to postpone/snooze the archival instead of overriding it.

Overrides apply to the selected path and everything below it.

=== 5) History ===
This page shows completed archival moves.
When a dataset has been successfully archived and finalized, it is removed from active scheduling pages and moved into history.

[[File:User history.png|left|frame]]

== Group pages ==

Group admins have a separate set of pages for their group scope:
* Group overview
* Group datasets
* Group schedule
* Group overrides
* Group history

If you manage more than one group, you can switch group scope in the selector at the top of the group pages.

== Notifications (email) ==

Tapeworm sends email updates when actions are pending, dates are approaching, or move state changes happen.

Emails typically include:
* Dataset path
* Size
* Last activity
* Current status
* Review/scheduled date

Notification types you may receive:
* Action required: please approve, snooze, or deny
* Reminder: review date is approaching
* Informational: move status changed (for example scheduled, staging, or completed)
* Escalation: sent to group contacts when no user response is received

Please read these emails carefully — they are your chance to adjust decisions before execution.

== Best practices for users ==

* Check your Overview page regularly
* Use Snooze if you need time to validate impact
* Add metadata when approving important datasets
* Use Overrides for known and persisting exceptions
* If unsure, contact HPC support before a scheduled move date

== FAQ ==

=== What happens if I do nothing? ===
Planned items can move forward automatically after the review window (4 weeks)

=== Can I undo after tape staging? ===
Not directly in Tapeworm. Retrieval is done via the tape/iRODS workflow.
See: https://irods.wur.nl/userguide/tape_retrieval/

=== What does “completed” mean? ===
Completed means Tapeworm saw the tape workflow finish and finalized the move.
Before finalization, the system verifies the archive in iRODS and only then removes the staged source copy.

=== Why is an action button disabled? ===
Usually because the move has already progressed (executing/staged/on tape/error), so schedule edits are no longer valid.

=== Why do I see “planned + notified”? ===
That means the dataset move is planned and a notification has already been sent.

== Need help? ==
If anything is unclear, or you think a move is incorrect but you cannot alter it in the provided GUI, please open an HPC support ticket.

File:User history.png

2026-03-03T15:35:42Z

Prins089: Prins0891 uploaded a new version of File:User history.png

File:User history.png

2026-03-03T15:32:45Z

Prins089:

Archival Storage

2026-03-03T15:25:46Z

Prins089:

= Tapeworm: Automated tape-archival of old datasets =

<div style="border:2px solid #d32f2f; background:#ffebee; padding:12px; margin:12px 0;">
Warning:
<ul style="margin:8px 0 0 18px;">
<li>This documentation page is under construction and may contain errors.</li>
<li>The Tapeworm application is in beta and may contain errors.</li>
</ul>
</div>

=== https://tapeworm.anunna.wur.nl/ ===

Tapeworm helps you manage data on <code>/archive</code> by identifying datasets that are no longer actively used and preparing them for tape archival.
The goal is simple: keep our warm storage available for active work, while safely preserving older data on tape.

With Tapeworm, you can:
* See which of your datasets are being considered for tape archival.
* Review planned moves before they happen.
* Approve, snooze, or block moves when needed.
* Add metadata to help describe archived datasets. The metadata is included on tape and can be used to view/retrieve from tape, should you need to do so in the future.

If you do nothing, Tapeworm will continue with the planned move after the review period.
That is why we recommend checking your pending actions regularly. You will also receive notification emails about pending actions.

== How Tapeworm works ==

# Tapeworm scans <code>/archive</code> and builds an index of datasets, size, owner, and last active use.
# A policy engine checks which datasets look stale (for example: 30+ days old and larger than 1GB).
# Matching datasets are marked as planned and shown in your overview.
# You will be notified by email that Tapeworm plans to move data you own
# You can review and change what should happen, or block the move(s) entirely
# If no action is taken, after a wait period of 4 weeks, planned moves can become scheduled and then executed.
# Data is moved to tape, and removed from /archive/

== Who sees what? ==

* Regular users see only their own datasets and actions.
* Group admins/contacts see data for their configured group(s), in addition to their own data.

== User pages ==

=== 1) Overview ===
This is your action page. It shows items that currently need your decision.

[[File:User overview 3.png|left|frame]]

For each candidate, you can:
* Approve: proceed with the tape move. It will schedule for the next day.
* Deny: stop this move, configure an override for this path. Tapeworm will not try to move this dataset/path again, until you choose to remove the override.
* Snooze: postpone the decision to a future date.
* Edit metadata: add key/value notes for archived data. These values are included on tape and can be used to view/retrieve datasets on tape.

You can also select multiple rows and apply actions in bulk.

=== 2) Datasets ===
This page shows your discovered datasets, their sizes, and last activity times. The application has no concept of what data belongs together and should be considered a 'dataset'. If the selections on this page are wrong, you can change how Tapeworm should handle these datasets instead.

[[File:User datasets.png|left|frame]]

Important:
* If a dataset already has an active move candidate, scheduling controls are disabled.
The dataset list is informational; move decisions are handled through the Schedule page.

=== 3) Schedule ===
This page shows move candidates and their status over time.

[[File:User schedule.png|left|frame]]

Common statuses:
* Planned (or planned + notified): under review.
* Scheduled: move is planned for a specific date.
* Executing / Tape staged / On tape: move is in progress or completed.
* Error: move needs admin attention. You may be contacted, maybe we resolve it ourselves :).

Once a move is already executing or completed, schedule-changing actions are locked.

=== 4) Overrides ===
Overrides tell Tapeworm to ignore specific paths in future planning.

[[File:User override.png|left|frame]]

Use overrides when:
* a project is still active and needs to remain on /archive
* policy suggestions are not appropriate for that location

If you agree that the dataset can in principle be moved to tape, but you don't (yet) know when, you can choose to postpone/snooze the archival instead of overriding it.

Overrides apply to the selected path and everything below it.

=== 5) History ===
This page shows completed archival moves.
When a dataset has been successfully archived and finalized, it is removed from active scheduling pages and moved into history.

[[File:User history.png|left|frame]]

History helps you answer:
* what was moved,
* when it moved,
* where it went on tape.

== Group pages ==

Group admins have a separate set of pages for their group scope:
* Group overview
* Group datasets
* Group schedule
* Group overrides
* Group history

If you manage more than one group, you can switch group scope in the selector at the top of the group pages.

== Notifications (email) ==

Tapeworm sends email updates when actions are pending, dates are approaching, or move state changes happen.

Emails typically include:
* dataset path,
* size and last activity,
* current status,
* review/scheduled date.

Notification types you may receive:
* Action required: please approve, snooze, or deny.
* Reminder: review date is approaching.
* Informational: move status changed (for example scheduled, staging, or completed).
* Escalation: sent to group contacts when no user response is received.

Please read these emails carefully — they are your chance to adjust decisions before execution.

== Best practices for users ==

* Check your Overview page regularly.
* Use Snooze if you need time to validate impact.
* Add metadata when approving important datasets.
* Use Overrides for known exceptions.
* If unsure, contact HPC support before a scheduled move date.

== FAQ ==

=== What happens if I do nothing? ===
Planned items can move forward automatically after the review window (typically 4 weeks).

=== Can I undo after tape staging? ===
Not directly in Tapeworm. Retrieval is done via the tape/iRODS workflow.
See: https://irods.wur.nl/userguide/tape_retrieval/

=== What does “completed” mean? ===
Completed means Tapeworm saw the tape workflow finish and finalized the move.
Before finalization, the system verifies the archive in iRODS and only then removes the staged source copy.

=== Why is an action button disabled? ===
Usually because the move has already progressed (executing/staged/on tape/error), so schedule edits are no longer valid.

=== Why do I see “planned + notified”? ===
That means the dataset move is planned and a notification has already been sent.

== Need help? ==
If anything is unclear, or you think a move is incorrect but you cannot alter it in the provided GUI, please open an HPC support ticket.