Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
habrok:migration:migration_habrok [2023/05/10 11:26] – [Migration to Hábrók] camarocicohabrok:migration:migration_habrok [2026/01/14 10:17] (current) – [Partitions] Remove gelifes pedro
Line 72: Line 72:
 ==== Data migration ==== ==== Data migration ====
  
-The data in the home directories and /data of Peregrine will be made available read-only on the login nodes of Hábrók for a period of three months (until July 1st 2023). +The data in the home directories and /data of Peregrine was available read-only on the login nodes of Hábrók for a period of three months (until July 1st 2023), and is no longer available.
- +
-This will allow you to migrate the data on these file systems to Hábrók at your leisure, and to select which data is still relevant on the new cluster. +
- +
-**The data on Peregrine /scratch will not be migrated, since it is temporary space only.** +
- +
-The Peregrine storage areas can be reached in ''/mnt/pg-home'' and ''/mnt/pg-data''.+
  
 +**The data on Peregrine /scratch was not be migrated, since it is temporary space only.**
 ===== Hardware classes ===== ===== Hardware classes =====
  
Line 94: Line 89:
 ===== Partitions ===== ===== Partitions =====
  
-In Hábrók four main partitions are available: regular, himem, parallel and gpu. The partitions correspond to the hardware classes in the table above. Besides this the gelifes partition is accessible to the members of the GELIFES research institute.+In Hábrók four main partitions are available: regular, himem, parallel and gpu. The partitions correspond to the hardware classes in the table above. <del>Besides this the gelifes partition is accessible to the members of the GELIFES research institute.</del>
  
 All these partitions are subdivided into a short, medium and long partition, which you as a user don’t have to select as this will be done automatically, based on job length.  All nodes in a class are available in the short sub-partition, a large part in the medium sub-partition and a limited fraction in the long sub-partition. All these partitions are subdivided into a short, medium and long partition, which you as a user don’t have to select as this will be done automatically, based on job length.  All nodes in a class are available in the short sub-partition, a large part in the medium sub-partition and a limited fraction in the long sub-partition.
Line 105: Line 100:
  
 ^ Partition ^ Description ^ ^ Partition ^ Description ^
-| regular   | Partition for the standard CPU nodes | +| regular            | Partition for the standard CPU nodes | 
-| himem     | Partition for the nodes with a large amount of memory | +| himem              | Partition for the nodes with a large amount of memory | 
-| parallel  | Partition for nodes with a fast, low-latency interconnect. This partition is meant for jobs that use multiple nodes and require high bandwidth or low latency.| +| parallel           | Partition for nodes with a fast, low-latency interconnect. This partition is meant for jobs that use multiple nodes and require high bandwidth or low latency.| 
-| gpu       | Partition with the GPU nodes. More details in the GPU section below.| +| gpu                | Partition with the GPU nodes. More details in the GPU section below.| 
-| gelifes   | Partition with the nodes owned by the GELIFES institute. |+|<del> gelifes </del>|<del> Partition with the nodes owned by the GELIFES institute. </del>|
  
 +Note: the ''gelifes'' partition has been decommissioned as the nodes that made it up are now out of support.
 ===== GPUs ===== ===== GPUs =====
  
Line 118: Line 114:
  
 Please see [[habrok:additional_information:known_issues|]] Please see [[habrok:additional_information:known_issues|]]
 +
 +===== FAQ =====
 +
 +==== Will my Peregrine account work on Hábrók? ====
 +
 +Because there are quite a number of inactive accounts on Peregrine, we have decided not to automatically migrate the accounts to Hábrók, so your account on Peregrine will not automatically work on Hábrók. 
 +
 +If you want to use the new cluster, you need to request access to it by using the  [[https://iris.service.rug.nl/|Self-Service Portal IRIS]]. 
 +
 +Please go to Research and Innovation Support → Computing and Research Support Facilities → High Performance Computing Cluster → Request Hábrók Account.
 +
 +==== Will my data be automatically moved from Peregrine to Hábrók? ====
 +
 +We will not automatically move your data from Peregrine to Hábrók. The filesystems on Peregrine, ''/home'' and ''/data'' will be made available read-only on Hábrók for three months after Peregrine shuts down. You will have this time to move your data to permanent storage on Habrok. 
 +
 +**The data on Peregrine /scratch will not be migrated, since it is temporary space only.**
 +
 +==== How do I migrate data to Habrok? ====
 +
 +The best tool for copying data from one location to the other is ''rsync''. Here is an example showing how to synchronize a directory with files from the Peregrine ''/data'', available under ''/mnt/pg-data'' on the login nodes to the new ''/projects'' on Hábrók:
 +<code>
 +rsync -av /mnt/pg-data/p123456/important_data/ /projects/p123456/important_data/
 +</code>
 +Note the slashes at the end of the source and the destination. The following flags have been used:
 +  * ''-a'': archive to copy everything recursively including file ownership and permissions
 +  * ''-v'': verbose to show the progress
 +You can also enable compression using ''-z'', but this will only speed up the transfer of highly compressible data. Since sufficient bandwidth should be available for the transfers compression will probably only add overhead.
 +
 +The best thing about using ''rsync'' is that you can restart the transfer in case of failures, and ''rsync'' will just continue where it stopped.
 +
 +==== How do I migrate data from a group folder to Habrok? ====
 +
 +The group folders will also be available at ''/mnt/pg_data/pg-group'', and we are currently creating new groups on Habrok. These groups will have a similar naming pattern as on Peregrine, e.g. ''pg-group'' becomes ''hb-group''. We will then add the users to these new groups, and the new group will be the owner of the folder ''/mnt/pg_data/pg-group''. From this point, the data can be copied over to Habrok using ''rsync'', as explained above. The location for the group folder on Habrok will be ''/projects/hb-group''.
 +