Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
hpc-compendium
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ZIH
hpcsupport
hpc-compendium
Commits
995276ab
Commit
995276ab
authored
1 year ago
by
Martin Schroschk
Browse files
Options
Downloads
Patches
Plain Diff
WIP Restructore for better guidance
parent
04d4f7ce
No related branches found
No related tags found
2 merge requests
!920
Automated merge from preview to main
,
!918
Barnard cleanup
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md
+28
-6
28 additions, 6 deletions
...zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md
with
28 additions
and
6 deletions
doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md
+
28
−
6
View file @
995276ab
...
...
@@ -60,11 +60,15 @@ below. In order to support the data life cycle management, the well-known
All old filesystems will be shutdown by the end of 2023.
To work with your data from Taurus you might have to move/copy them to the new storages.
For this, we have four new
[
datamover nodes
](
/data_transfer/datamover
)
that have mounted all storages
of the old Taurus and new Barnard system. Do not use the datamovers from Taurus, i.e., all data
transfer need to be invoked from Barnard!
### Workspaces on Barnard
The filesystems
`/data/horse`
and
`/data/walrus`
can be accessed via workspaces. Please refer to the
[
workspace page
](
../../data_lifecycle/workspaces/
)
, if you are not familiar with workspace
s concept
and the corresponding commands.
[
workspace page
](
../../data_lifecycle/workspaces/
)
, if you are not familiar with
the
workspace
concept
and the corresponding commands.
| Filesystem (use with parameter
`--filesystem=<filesystem>`
) | Max. Duration in Days | Extensions | Keeptime in Days |
|:-------------------------------------|---------------:|-----------:|--------:|
...
...
@@ -86,11 +90,29 @@ and the corresponding commands.
[...]
```
For this, we have four new
[
datamover nodes
](
/data_transfer/datamover
)
that have mounted all storages
of the old Taurus and new Barnard system. Do not use the datamovers from Taurus, i.e., all data
transfer need to be invoked from Barnard!
### Data Migration to New Filesystems
!!! hint
Since all old filesystems of Taurus will be shutdown by the end of 2023, your data needs to be
migrated to the new filesystems on Barnard. This migration comprises
*
your personal
`/home`
directory,
*
your workspaces on
`/ssd`
,
`/beegfs`
and
`/scratch`
.
!!! note "It's your turn"
**You are responsible for the migration of your data**. With the shutdown of the old
filesystems, all data will be deleted.
!!! note "Make a plan"
We highly recommand to **take some minutes for planing the transfer process**. Do not act with
precipitation.
Please **do not copy your entire data** from the old to the new filesystems, but consider this
opportunity for **cleaning up your data**. E.g., it might make sense to delete outdated scripts,
old log files, etc., and move other files to an archive filesystem.
!!! hint "Generic login"
In the following we will use the generic login `marie`
([cf. content rules on generic names](../contrib/content_rules.md#data-privacy-and-generic-names)).
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment