Mysql replication setup for existing voip billing

VoIP provider company is using Portaone product Portabilling version MR24 as a billing system. Portabilling installation schema consists of 5 dedicated servers: Master Slave Replication server Configurator Radius machine Slave server hosted at OVH (dedicated server with 2 disks) had issue with one of the disks, which was replaced. During replacement, the second disk was moved and it got out of the raid, which was not noticed by technician who did the replacement. As a result, after booting the server from HD to get the new disk synched, server failed. Mysql stopped (probably to avoid corruption of master mysql). The mistake was found and corrected weeks later. Technician tried to copy the content of disk2, which had slave info. After copying, turned out that 2 partitions out of 3 are corrupted. Corrupted partitions have been restored from tar archives. Slave server has 2 versions of Portabilling (MR23 and MR24). Server is up now with 2 disks, which are synched. Master and slave servers have real time replication. Mysql replication is not done yet. Each of the servers (master and slave) have 3 interfaces (IP’s). The project is to complete the mysql replication and to put slave up, making sure nothing will break or get corrupted on master DB. Additional notes (points with questions needs to be answered by freelancer): 1. We have list of mysql users for slave (but not the privilege table). It is almost the same with slave (not fully). 2. Except mysql users and Porta-billing database, is there anything which is missing to complete the mysql replication and put the slave server up (DB copied + mysql users inserted)? DB is copied already (a week ago). 3. Master Bin files needs to be copied from master to slave, or when replication setup is done it will synch with the last one and we do not need those on slave server (Bin files do not archive in 24 hours, it is more, than 24 hours, we can check in config files if needed)? 4. Mysql version on master and slave must be the same? 5. Portabilling https interface is showing [login to view URL] now (I guess because slave can not connect via mysql to master to synch). 6. Replication goes from Master to slave, but when we do any change from slave https interface, it gets replicated on master (probably slave interface sends the change to master, and then replication goes to slave, as slave does not have write access on master?). 7. There are internal company documents on master > slave replication and the candidate needs to sign additional non disclose agreement to get access to that documents and to the servers (a copy of passport is needed). As well as, there are some outputs from slave server showing the ports, ip’s of replication, which could be helpful.