my.cnf for optimization

[TwistedFister]

Vicibox 7.0.3 from .iso | Vicidial 2.14-579a Build 161128-1746 | Asterisk 11.22.0-vici | CLuster setup: 1 web 1 DB 1 Slave DB 8 telephony | No Digium/Sangoma Hardware | No Extra Software After Installation

we added a new slave db (ssd's 64GB ram) and looking to optimize it. Do we need to change anything within my.cnf? Or what would be recommended for optimization?

[RockAllMoment]

Yes you have to change my.conf file in slave db to add server_id=2 and in master server_id=1 and log_bin then only the main server will act as master and the second one will act as a slave server.

Note: Once you started slave concept on secondary server avoid manual changes on slave server. Which disconnects slave server from master server.

[Noah]

Did you use the standard my.cnf on the installation for the slave DB?

Slave acts very similarly to production. It inserts, updates and deletes as the production db does based on the same queries from the bin log.
If the servers are the same the same settings would apply, other than the server ID as the post before mentions.

[williamconley]

Vicibox 7.0.3 from .iso | Vicidial 2.14-579a Build 161128-1746 | Asterisk 11.22.0-vici | CLuster setup: 1 web 1 DB 1 Slave DB 8 telephony | No Digium/Sangoma Hardware | No Extra Software After Installation

we added a new slave db (ssd's 64GB ram) and looking to optimize it. Do we need to change anything within my.cnf? Or what would be recommended for optimization?

Vicibox has an installer option for replication. I suspect you'll find it ... useful.