[#GALAXY-139] Document backup and restore procedures

Galaxy

Document backup and restore procedures

Created: 03/Mar/08 02:56 PM Updated: 15/Dec/08 01:15 PM

Component/s:

Documentation

Affects Version/s:

1.0-beta-2

Fix Version/s:

1.x Backlog

Time Tracking:

Not Specified

Labels:
User impact:	High
Affects Docs:	Yes

Description

« Hide

Backup and restore procedures for a Galaxy repository need to be well documented and tested. There doesn't appear to be any documentation on the correct procedures to do this. And hopefully it should be
possible to fully backup the repository and galaxy configuration without stopping the galaxy server (if it's not, then a feature request should be spawned).

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Dan Diephouse added a comment - 03/Mar/08 07:17 PM

Thanks, we definitely need to do this.

[ Permlink | « Hide ]

Dan Diephouse added a comment - 16/May/08 04:27 PM

I think this is probably going to be dependent on the DB being used.

[ Permlink | « Hide ]

Ken Yagen added a comment - 31/Oct/08 01:25 PM

1. backup/restore for the embedded derby db
2. High level instructions for backing up/restoring with an external DB with a specific example for MySQL
3. Information on whether or not "hot" backup is allowed for either 1 or 2. (or the degree of hotness allowed - is it fine if people are writing? what if they're just reading? etc)
Thanks,