On Sep 6, 2012, at 9:29 AM, Fourie Joubert wrote:
Hi Folks
Our current galaxy version is pretty old (git updates are causing problems),
and we are running very low on space in our filesystem which hosts
/xxx/galaxy/database/files.
I need to start with a clean galaxy install (possibly on a new server) on a
new file system (a large Lustre volume, which is also mounted on our cluster).
I do need to migrate the shared data libs, histories, workflows, etc. from
the old Galaxy installation.
Most of the shared data lib stuff is symlinks, which will require a change to
the root path.
Would it possibly be feasible to use a schema-updated copy of our current
database for the new install, and do a search-and-replace procedure on the
file paths in the database to deal with the new root path for the files?
Anyone know which tables are involved?
Any tips and advice regarding a migration of Galaxy would be really
appreciated.
Best regards!
Fourie
Hi Fourie,
Dumping the database and loading it on the new server, then modifying paths is
your best bet. You can update the pats with SQL directly or a small script.
The relevant paths are in Galaxy's 'dataset' table.
--nate
--
--
Prof Fourie Joubert
Bioinformatics and Computational Biology Unit
Department of Biochemistry
University of Pretoria
fourie.joub...@.up.ac.za
http://www.bi.up.ac.za
Tel. +27-12-420-5802
Fax. +27-12-420-5800
-
This message and attachments are subject to a disclaimer. Please refer
to www.it.up.ac.za/documentation/governance/disclaimer/ for full details.
___
Please keep all replies on the list by using reply all
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
___
Please keep all replies on the list by using reply all
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/