Migrating Eprints from Sigprod to synapse

Details on what I did to transfer eprints, and to upgrade from 3.3 on sigprod to 3.4 on synapse

*Installed mariadb: yum install mariadb (open source version of mysql)

*Installed eprints 3.4 on synapse in /opt/eprints3. See https://wiki.eprints.org/w/Installing_EPrints_on_RHEL/Fedora/CentOS Included creating a database sigpubs on mysql, user sigpubs.

* Created new empty sigpubs archive and tested to be sure it was working https://wiki.eprints.org/w/Getting_Started_with_EPrints_3

* Grabbed a backup of sigpubs running on sigprod: crux: /usr/local/backups/systems/sigprod/ebackups/sigpubs.tar-20190128.gz . scp’d to synapse:/root/eprintsinstall, unpacked.

*Loaded mysql database dump from backup into existing sigpubs mysql database. Followed instructions in https://wiki.eprints.org/w/Upgrading_3.3.12%2B_to_3.4 to upgrade from 3.3 on sigprod to 3.4 on synapse. Regenerated static views. Seems to work.

* Bill changed CNAME sigpubs.si.washington.edu from pointing at sigprod to pointing at synapse.

*Setup automatic daily backup scp’d backup script found on sigprod:/ /usr/local/projects/sigpubs/sigpubs_backup.sh to synapse:/root/bin

Modifed backup script for synapse locations

Copied sigpubs logrotate file from sigprod:/etc/logrotate.d/sigpubs_logrotate.sh to synapse:/etc/logrotate.d, modified for synapse.

Removed dateext directive so logfiles will only have numbers. If they have dates then older versions will keep piling up on the backup server.

Tested this out, but date is still being added. Restarted crond, will see if that makes a difference. Didn't make any difference. Probably because global /etc/logrotate.conf has datext and this is never overwritten by nodateext in any of the logrotate.d files.

TODO: Discuss with Todd whether we want to remove dateext.