-
Notifications
You must be signed in to change notification settings - Fork 4
Database Administration
ferayd edited this page Jul 22, 2018
·
7 revisions
DB Server: mercury.bioinformatics.danforthcenter.org
DB Server Product: MariaDB (MySQL-compatible)
DB Name: rsa_gia
DB Storage Engine: InnoDB
Backup Information:
Type: logical, full, online backup
Task: cron job of rsa-data user on pluto.bioinformatics.danforthcenter.org
Frequency: Every day at 2 am
DB credentials: ~rsa-data/.my.cnf
Directory: /shared/backups/db_backups/
Retention: 90 days
Error Reporting: bioinfo-alerts@danforthcenter.org
The admin should make sure that the DB server and the backup task are always running, that they have enough disk space, etc.
- Follow these instructions to install MariaDB on the new server.
- Take a full backup of the old rsa_gia DB and restore it on the new server.
- Recreate the old MariaDB users and permissions on the new server. Or, take a full backup of the old mysql DB and restore it on the new server.
- Update the server name in the cron job code of the backup task.
- Update the server name in the default.properties file next to rsa-gia.jar.
- Follow these instructions to install MariaDB-client on the new server.
- Move the cron job code from the old server to the new server.
- Create the backup directory with the correct permissions on the new server, and update it in the cron job code if needed.
- Copy ~/.my.cnf from the old server to the new server.
- Change the username and password on the DB server.
- Update ~/.my.cnf on the backup server.
- Update the rsa-gia source code (in file src/org/danforthcenter/genome/rootarch/rsagia/app2/App.java), rebuild rsa-gia.jar, and copy it to its usual location.