A slave monitor computer constantly monitors the health of the replication process. One computer must be designated as the slave monitor, and each server must have the slave monitor specified in the Slave Monitor field.
Example: There are two replications servers (A and B) at two different offices. In server A's office, the replication monitor could be any computer on network A. It would not be a computer on network B, because if the internet went down, the monitor would quit working.
Server Description: The description of the server. This description can be changed but it should match your server name or IP address exactly. We recommend using the IP address to reduce possible DNS issues. Not actually linked to the Clinic table.
server_id: Assign a unique server_id to each server. This ID will be specified in the my.ini file during setup. Each workstation can then use a query to identify which server it is connected to.
A to Z folders: Assign each server an A to Z folder. It can differ by server. This allows use of a folder in the local area network rather than one that's accessed across a VPN. This path will show in the Data Path window (Paths). Keeping the A to Z folders synchronized between locations is up to the customer and requires additional software and expertise (see Folder Replication).
Update Blocked: Set whether an Open Dental software update can occur from this server. We recommend updating Open Dental from only one server and blocking updates from others.
Report Server: Flag the server as a report replication server so it can run dangerous Queries such as those with CREATE TABLE or DROP TABLE syntax. These queries can cause replication failure so should only be run on report servers. More than one computer can be a 'report' server.
Slave Monitor: Specify the computer that will monitor the status of the replication process. If replication fails, this computer will be responsible for disabling access to Open Dental from all computers on this server until replication has been restored. The slave monitor should stay on and logged on to Open Dental at all times.
Syncing databases will update all databases in the chain with new entries.
To detect replication failure, Open Dental must be running on the designated slave monitor computer.
How replication failure is detected.
For example if server ID is 3:UPDATE preference SET ValueString = '3' WHERE PrefName = 'ReplicationFailureAtServer_id';
It is up to the administrators of the replication service to ensure that training is in place to make sure users know what to do when they see this message.
The slave monitor will detect failure if replication stops or fails on any server, for any reason. So do not stop replication unless Open Dental is shut down on the monitor. The slave monitor will not react to loss of internet connection; MySQL will gracefully continue replication where it left off when reconnected. Stopping the MySQL service will cause other error messages in Open Dental, but will not trigger a reaction by the slave monitor.