...
Make sure that connections are allowed to port 3306 from the peer server only (see firewall instructions below). For instructions on setting up the MySQL master/slave replication, see https://wikis-mit-edu.ezproxyberklee.flo.org/confluence/display/ISDA/MySQL+Replication+Configuration+Instructions
Maintaining the CAMS database
The backup-db script should be installed in /usr/local/cams/sbin on both the master and slave servers, and run periodically from cron. It will dump all databases to a compressed timestamped file in /usr/local/cams/backup/local, and also copy this file over to the peer server's /usr/local/cams/backup/remote directory. To set up the procedure, do the following:
- Create the /usr/local/cams/backup, /usr/local/cams/backup/local, and /usr/local/cams/backup/remote directories.
- Create the /usr/local/cams/sbin directory, if necessary.
- Install the backup-db script in /usr/local/cams/sbin on the MySQL master server.
- Create the backup user in the database on the master, as above.
- Create /usr/local/cams/conf/backup.cnf, with the username and password for the backup account:
No Format [client] user=backup password=<password>
On the slave server, the check-slave-status script should also be installed in /usr/local/cams/sbin; it should be run once per hour from cron. This should use a special replicatechecker account in MySQL, created as follows (this should be created on the master, after replication has been set up):
No Format |
---|
# mysql
mysql> GRANT REPLICATION CLIENT ON *.* TO 'replicatechecker'@'localhost' IDENTIFIED BY '<password>';
Query OK, 0 rows affected (0.00 sec)
mysql> quit
|
where <password> is replaced by the password for the replicatechecker
account. Next, create /usr/local/cams/conf/replicatechecker.cnf, with the username and password for the replicatechecker account:
No Format |
---|
[client]
user=replicatechecker
password=<password>
|
Any problems encountered by either of these procedures will be reported via email to touchstone-support.
cams-ldap
The Cams-to-LDAP integration is done via a trigger library added to the MySQL instance, and a separate Perl daemon which propagates account changes to Moira and LDAP. Set it up as follows:
...