Restoring Datasets¶

The Restore feature allows for retrieving archives and datasets that have been sent to long-term storage and subsequently deleted from disk. Files stored in long-term storage, such as tape archiving, are kept for at least 10 years, ensuring that data can be restored when needed.

At EMBL, the restore feature uses a DMApp plugin interface in the background to restore data that were archived with LabID (through the DMApp Archive plugin). For other cases, a default archive/restore process is employed.

Note about legacy archives

Legacy archives (i.e. not archived using the DMApp in the barckground) require a manual action which has to be performed by the the admin of the LabID instance.

Restore individual archives¶

Archives can be restored individually either from the archive list page or from an archive detail page.

Archive list page¶

Restore archive controls on the Archive list pages

Select a single archive and click the Archive button to open the menu where you can access the Restore Archive entry

This will open a popup with information about the archive and datasets that can be recovered. Read about the popup below

Archive detail page¶

Visit the detail page of an archive and click the Restore button in the button bar at the top right of the page

Restore datasets¶

Dataset list page¶

When multiple datasets are selected on the dataset list page, you can click the archive button to open the menu and access the Restore Datasets entry

The Restore popup provides information about the datasets you are trying to recover. You will also be prompted to choose a restore location which by default is set to be the last known location of the files, if you can access it.

Information about datasets¶

The popup informs you about which datasets can and cannot be recovered, as well as the reasons for which a recovery - or recovery at original location - is not possible. Generally, the impossibility to recover a given dataset at its original location reside in lack of permissions to read the files or access rights to the disk where they should be restored.

Restorable dataset list¶

List of datasets that can be restored

A list of the datasets that can be restored is provided. Each dataset entry can be toggled to list the datafile constituting the dataset, as well as the last known location of the datafile copy that will be used for recovery.

Non-Restorable dataset list¶

List of datasets that cannot be restored

A list of the datasets that cannot be restored is provided. Each dataset entry can be toggled to display the datafiles constituting the dataset, as well as the error associated to the datafile. In the above screenshot, the dataset cannot be restored because no archive was found (it hasn't been archived yet!).

Reasons preventing recovery at original location¶

Icon showing the storage volume is offline The storage volume is offline

A storage volume can be offline, this for example occurs when a group leaves the institute.

Icon showing the user lacks permissions on the storage volume User lacks permissions on the storage volume

You lack the necessary permissions to access the storage volume where a given dataset should be restored.

When either of the above reasons prevent recovery at the original location, a restore destination has to be provided.

Reasons preventing succesful recovery¶

Icon showing the archive is past its expiry date The archive is past its expiry date

The archive containing the dataset is past is expiry date (10 years by default). In such case, proper recovery can happen but is not guaranteed.

Restore Destination¶

By default, a given dataset is recovered at its last known location, and therefore remove the need to provide any Restore Destination.

Form status when restoring at original location is possible and enabled

However, in cases where restoring at the original location is not possible or not desired, a restore destination has to be provided.

Form status when restoring at original location is not possible and a valid UNIX path is provided

The restore destination should be a valid UNIX path and the location should be accessible by the technical UNIX user of the LabID instance. When in doubt, set directory permission to 777 for the time of the restore operation, and then restrict access to the directory if needed.