Difference between revisions of "DANS Data Management"
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
===Uploading data=== | ===Uploading data=== | ||
− | Data can be uploaded from 'twister11.dans.knaw.nl' using the [DANS_Upload Upload] procedure. | + | Data can be uploaded from 'twister11.dans.knaw.nl' using the [[DANS_Upload Upload]] procedure. |
* create a new directory with the name of the archive. As an example we use the 'Crome' archive: | * create a new directory with the name of the archive. As an example we use the 'Crome' archive: | ||
mkdir -p ~/dans/Crome/ | mkdir -p ~/dans/Crome/ | ||
Line 19: | Line 19: | ||
* copy over the scripts from the repository | * copy over the scripts from the repository | ||
cp -a ~/dans/scripts/* . | cp -a ~/dans/scripts/* . | ||
− | |||
===Compressing data=== | ===Compressing data=== |
Revision as of 09:46, 10 May 2012
DANS Data Management
One of the main goals of DANS is to to longer-term management of a variety of data. The goal of the DANS Data Management project is to allow DANS to reliably back up their data onto BiG Grid storage resources.
'Reliably' means that the consistency of the data can be verified by DANS engineers at any given time. For this, a set of tools and procedures have been developed to allow DANS engineers to
- upload data from DANS to the grid (in 'tarball' format)
- compress the data stored on the grid
- verify the MD5 checksums of all data stored inside the tarballs on the grid
Uploading data
Data can be uploaded from 'twister11.dans.knaw.nl' using the DANS_Upload Upload procedure.
- create a new directory with the name of the archive. As an example we use the 'Crome' archive:
mkdir -p ~/dans/Crome/
- In this directory create another directory with the same name; this directory will contain the list of files and directories that need to be uploaded
cd ~/dans/Crome mkdir Crome
- copy over the scripts from the repository
cp -a ~/dans/scripts/* .