Backup

Snapshots

The data in your home directories is protected by nightly file system snapshots, which are kept for at most 7 days. In order to access theses snapshots, look into the directory /dss/dsshome1/.snapshots/. In this directory you'll find the individual snapshots as subdirectories, which have the date and time at which the snapshot was taken encoded as YYYY-MM-DD_HHMM in their directory name. In order to restore files you can simply copy them back to your HOME directory. A little tool may help you to access the snapshots:

    module load lrztools
    SN {file| deleted file| directory|deleted dierectory]

Tape Backup

Additionally the data in your home directories is also protected by nightly backups to tape. However, due to security reasons these backups are not directly accessible by the users. If you really need to have data in your home directory restored that cannot be found in the snapshots anymore, please submit a ticket to the Servicedesk for SuperMUC-NG. But bear in mind that this is a man power consuming activity and may take some time to complete.

In the future we also plan to replicate data on HOME asynchronously to a secondary system and keep more than 7 snapshots. However, this may still take some months to implement.

Please note that, as on SuperMUC, no automated backups in any way will be taken for the WORK or SCRATCH file systems.

SuperMUC-NG Archive (Data Science Archive)

The new SuperMUC-NG Data Science Archive (DSA) is able to process increased data volumes and rates that are created by SuperMUC-NG projects and also provide much more convenience in managing and sharing this data within LRZ but also on a world-wide basis.

DSA is available to all SuperMUC-NG compute projects. If your project has no quota for the DSA yet, please submit (master users only) a request for DSA volume to the Servicedesk for SuperMUC-NG.

Details on the usage of DSA can be found here.

Details on the management of DSA (for Master Users) can be found here.

Legacy HPC Archives

Status and future of the Archive System/Data of SuperMUC

Write access to the SuperMUC Archive

Please treat the old SuperMUC archive as a "read only" storage system, since no more additional storage capacity will be provided.
Stored data is still accessible but new volumes of data must be stored on the DSA system.

Access to the legacy archive system and data of SuperMUC is currently possible via the special login node: skx-arch.supermuc.lrz.de

Change of access policy to the archive data

The access policy to the tape archive on SuperMUC-NG differs from the policy on SuperMUC! Access rights on SuperMUC were granted to individuell users (only the users who wrote the data could access it), whereas on SuperMUC-NG the rights are granted to the particular project.

Permissions to access the data will now be granted to all users of a project i.e., all users in a group can retrieve data from other users of the project group.
The previous policy was that only the users who wrote the data could access it.
If you project is for example ‘pr12ab’, you can see the members of this group by
getent group pr12ab-d
This change also affects data stored before the transition of the archive to SuperMUC-NG

If the new policy is not appropriate for you, the master user/project manager must put a request to the Servicedesk for SuperMUC-NG. We will then restrict the access only to the master user/project manager of the project. However, all other user in the project group will have no access.

Explicitly specifying the target project

Please note that because of the new, user centric usage model of SuperMUC-NG, you have to explicitly specify the project name on the dsmc command line, whose archive data you want to access. This is done by using the -se option. E.g. dsmc archive -se=prXXXX myFile

Details on the usage can be found here.

Status and future of the Archive Data of HLRB2 and HLRB1

We still retain the archive data of HLRB2 and HLRB1. However, due to technical and security reasons users don't have access to the data via self service. If you need data from these archives, please submit a ticket to the Servicedesk for SuperMUC-NG.