Biology Reference
In-Depth Information
which data are migrated from the “live mirror” to the “staging server”
and back again. I have excerpted the following instructions from the
technical document used by the release coordinator:
Firstly, check there is enough space for the new databases, e.g. in /mysql/
data_3306/databases/df -h /mysql
# Release 50: 1000G 342G 658G 35% /mysql
You should be able to see how much space is required here (may be out of
date):
http://www.ensembl.org/info/webcode/requirements.html http://www
.ensembl.org/info/webcode/installation/index.html
Release 50: Total required = 632.8 GB
Next you will need to modify the following script:
cd /ensembl-personal/release_coordination/scripts
. . .
Now, run the script. For release 50:
cd /ensembl-personal/release_coordination/scripts
perl get_databases_from_ens-livemirror_to_ens_staging.pl 50
The script generates an appropriate input fi le,
ens-livemirror_to_ens_staging_databases
to use with
ensembl/misc-scripts/CopyDBoverServer.pl
To actually copy the databases across from ens-livemirror to ens-staging you
must be on ens-staging and logged in as mysqlens. Ask a previous release
coordinator for the password if you don't already know it.
ssh ens-staging
su—mysqlens
Now run the copy script:
cd ensembl/misc-scripts/
perl CopyDBoverServer.pl -pass ensembl /path/to/fi le/ens
livemirror_to_ens_staging_databases
Save and check the output from this script.
37
These instructions describe in detail the procedures used to copy data-
bases from the “live mirror” to the “staging server.” The crucial knowl-
edge in this document is about
where
to fi nd the various databases
and the programs to move them. The “scripts” are short Perl programs
(for example, get_databases_from_ens-livemirror_to_ens-staging.pl—
the purpose of the program is made obvious by its name) that are used
