From e40f2c0507d9f1ba666511fcaba40f92bb0eb3fc Mon Sep 17 00:00:00 2001 From: Arno Kaimbacher Date: Wed, 19 Apr 2023 17:00:27 +0200 Subject: [PATCH] - describe disaster recovery plans --- DataArchitectureDiagram.md | 73 +++++++++++++++------------ DisasterManagement.md | 101 ++++++++++++++++++++++++++++++++++++- 2 files changed, 142 insertions(+), 32 deletions(-) diff --git a/DataArchitectureDiagram.md b/DataArchitectureDiagram.md index 79ed0f5..8db4055 100644 --- a/DataArchitectureDiagram.md +++ b/DataArchitectureDiagram.md @@ -3,65 +3,76 @@ ![Image](./data_diagram.drawio.svg) # 1. Data Sources -TETHYS collects and manages scanned geological maps, spatial data sets, and other types of research outputs. + +TETHYS collects and manages scanned geological maps, spatial data sets, and other types of research outputs. The general guideline for publishing research data (manual, p. 11-2) is providing information on how to prepare data sources for deposit (helpful for depositors and repository staff): -* the types of file formats that are acceptable, -* what kind of data can be included in the research data repository, -* the file upload limits, -* what CC licenses can be used, -* the strategy for deleting datasets, -* how to handle the use of external research data, -* the required use of keywords -* Note that the uploaded data will be reviewed. + +- the types of file formats that are acceptable, +- what kind of data can be included in the research data repository, +- the file upload limits, +- what CC licenses can be used, +- the strategy for deleting datasets, +- how to handle the use of external research data, +- the required use of keywords +- Note that the uploaded data will be reviewed. # 2. Metadata Schema -The **Metadata format guidelines** (manual, p. 8-10) on the other hand, provides information on the specific types of metadata that should be included with the data. This may include information on the format and structure of the metadata, as well as the types of information that should be included. Tethys RDR is using three metadata standards (**Dublin Core, DataCite and ISO10130**) as well as one descriptive metadata element (dataset type). The dataset type is one of the following metadata elements: Analysis, Measurements, Monitoring, Remote Sensing, Geographic Information System (GIS), Models, and Mixed Type. + +The **Metadata format guidelines** (manual, p. 8-10) on the other hand, provides information on the specific types of metadata that should be included with the data. This may include information on the format and structure of the metadata, as well as the types of information that should be included. Tethys RDR is using three metadata standards (**Dublin Core, DataCite and ISO10130**) as well as one descriptive metadata element (dataset type). The dataset type is one of the following metadata elements: Analysis, Measurements, Monitoring, Remote Sensing, Geographic Information System (GIS), Models, and Mixed Type. # 3. Storage Infrastructure + This is the physical or virtual infrastructure used to store the data and metadata in the repository. By using **PostgreSQL**, TETHYS is able to manage large volumes of metadata and provide fast and secure access to this information. The data files are stored on an **Ubuntu file server** with **ext4**partition. # 4. Data processing and curation workflows + ... # 5. Discovery and access systems + TETHYS supports data discovery in various ways ## TETHYS REST API -Tethys Metadata and File downloads can be queried by a REST API (Representational State Transfer Application Programming Interface), + +Tethys Metadata and File downloads can be queried by a REST API (Representational State Transfer Application Programming Interface), which allows repository staff to interact with the Tethys system and retrieve metadata and data files programmatically. -* **metadata API**: e.g.: [metadata for dataset 209](https://tethys.at/api/dataset/200) -* **file download**: e.g. [file for dataset 209: api/file/download/1009](https://www.tethys.at/api/file/download/1009) - +- **metadata API**: e.g.: [metadata for dataset 209](https://tethys.at/api/dataset/200) +- **file download**: e.g. [file for dataset 209: api/file/download/1009](https://www.tethys.at/api/file/download/1009) ## Tethys Frontend + The datasets can always be found through the Data Frontend, https://tethys.at/search, browsing by subject, author, language or year, or by searching the metadata fields title, author or keyword. To enhance the discoverability of the datasets, TETHYS RDR stimulates adding as many metadata and other relevant documentation as possible. ## Solr Search Index - All visible metadata and some metadata extracted from data files are indexed and searchable by Solr. - ## DataCite DOI Fabrica - Tethys Repository assigns a DOI for each published dataset. - Therefore the datasts are also accessible via DOI Fabrica: e.g. https://doi.datacite.org/dois/10.24341%2Ftethys.200 +All visible metadata and some metadata extracted from data files are indexed and searchable by Solr. + +## DataCite DOI Fabrica + +Tethys Repository assigns a DOI for each published dataset. +Therefore the datasts are also accessible via DOI Fabrica: e.g. https://doi.datacite.org/dois/10.24341%2Ftethys.200 + +# 6. Authentication and authorization systems: -# 6. Authentication and authorization systems: TETHYS provides an Access Control List (ACL) system that is used to manage users, user roles and permissions. ![title](./tethys_acl.png) -* accounts: This table stores information about the users of the system. Each user is assigned a unique identifier, and the table includes fields for the user's name, email address, and timestamps. -* roles: This table stores information about the roles that are available in your application. Each role has a unique identifier and a name that describes the role. TETHYS is using the following rules: - * admin role: for editing user accounts, roles and permissions - * submitter role: Submitters submit original research datasets. Submitters are responsible for ensuring that their submissions meet the repository's guidelines and standards. - * editor role: TETHYS editors are responsible for overseeing the content and quality of the research repository. They review submissions to ensure they meet the repository's standards and may provide feedback to submitters. They may also work with reviewers to ensure that submissions are evaluated fairly. - * reviewer role: Reviewers are responsible for evaluating submissions to the research repository. They may be assigned specific submissions to review, and they provide feedback on the quality and relevance of the research. Reviewers typically have expertise in the field related to the research and may be asked to provide a written report or score to help the editor make a decision about whether to accept or reject the submission. - +- accounts: This table stores information about the users of the system. Each user is assigned a unique identifier, and the table includes fields for the user's name, email address, and timestamps. -* permissions: This table stores information about the permissions that are available for the roles. Each permission has a unique identifier, a name that describes the permission, and a short code that represents the permission. +- roles: This table stores information about the roles that are available in your application. Each role has a unique identifier and a name that describes the role. TETHYS is using the following rules: -* role_has_permissions: This table stores the relationship between roles and permissions. Each row in this table represents a role that has been granted a specific permission. + - admin role: for editing user accounts, roles and permissions + - submitter role: Submitters submit original research datasets. Submitters are responsible for ensuring that their submissions meet the repository's guidelines and standards. + - editor role: TETHYS editors are responsible for overseeing the content and quality of the research repository. They review submissions to ensure they meet the repository's standards and may provide feedback to submitters. They may also work with reviewers to ensure that submissions are evaluated fairly. + - reviewer role: Reviewers are responsible for evaluating submissions to the research repository. They may be assigned specific submissions to review, and they provide feedback on the quality and relevance of the research. Reviewers typically have expertise in the field related to the research and may be asked to provide a written report or score to help the editor make a decision about whether to accept or reject the submission. -* link_account_roles: This table stores the relationship between users (Accounts) and roles. Each row in this table represents a user that has been assigned a specific role. +- permissions: This table stores information about the permissions that are available for the roles. Each permission has a unique identifier, a name that describes the permission, and a short code that represents the permission. +- role_has_permissions: This table stores the relationship between roles and permissions. Each row in this table represents a role that has been granted a specific permission. - # 7. Preservation systems - .... +- link_account_roles: This table stores the relationship between users (Accounts) and roles. Each row in this table represents a user that has been assigned a specific role. + +# 7. Preservation systems + +.... diff --git a/DisasterManagement.md b/DisasterManagement.md index 5d08b7b..9d75071 100644 --- a/DisasterManagement.md +++ b/DisasterManagement.md @@ -1 +1,100 @@ -Welcome to the Wiki. \ No newline at end of file +

+ File Restore with the command line tool +

+"IBM Spectrum Protect" is a data protection and recovery software solution that helps to manage backup and recovery operations. + +For TETHYS up to **90 incremental versions** of each data file will be backed up and are available for recovery. This means that there are 90 instances of the data that have been backed up at different points in time. These versions are typically created based on the backup schedule and retention policies defined by the computer center of the „GeoSphere Austria“. + +## Recovery Tool + +Command line restore examples for the versio 8.1.17 can be found here:\ + https://www.ibm.com/docs/en/spectrum-protect/8.1.17?topic=data-command-line-restore-examples + +How TO: + +- change into the direcotiry of the IBM backup archive client: + ```bash + cd /opt/tivoli/tsm/client/ba/bin + ``` +- start the backup client wit admin rights: + ```bash + sudo dsmc + ``` +- general help + ```bash + Protect> help restore + ``` + +## Examples + +### **1. Restoring a single file from a selection of existing versions** + +```bash +Protect> restore /etc/host -pick -inactive /tmp/restored/ +``` + + + + + + + + + + + + + + +
Means:
+ Restoring the file /etc/hosts to a new target directory "/tmp/restored/" with manual selection (-pick) of the desired versions. The specification of "-inactive" is necessary to get also already deleted or changed versions of the file displayed. +
+ Subsequently, the following result is to be output. The column A/I means: +
+ A = letzte gültige Version (aktiv) +
+ I = Inaktive Versionen, die nicht mehr auf der Produktiv-Platte stehen +
+ You select the required version by entering the selection number at the front. + In the example, the older of two versions is to be restored werden. +
+
+ + + + + + +
tsm>   restore  /etc/host  -pick  -inactive  /tmp/restored/
+ Restore function invoked.
+ TSM Scrollable PICK Window - Restore
+
+ #    Backup Date/Time        File Size A/I  File
+ ----------------------------------------------------------------------------------------
+ 1. | 12/05/08   13:18:21       1.69 KB  A   /etc/hosts
+ 2. | 11/21/08   10:16:19        726  B    I   /etc/hosts
+     |
+     0---------10--------20--------30--------40--------50--------60--------70--------80------
+ <U>=Up  <D>=Down  <T>=Top  <B>=Bottom  <R#>=Right  <L#>=Left
+ <G#>=Goto Line #  <#>=Toggle Entry  <+>=Select All  <->=Deselect All
+ <#:#+>=Select A Range <#:#->=Deselect A Range  <O>=Ok  <C>=Cancel
+
+ pick>   2
+ + + + + +

+ Database Backup +

+.... \ No newline at end of file