Redundant database: Difference between revisions

From VoIPmonitor.org
Jump to navigation Jump to search
(Created page with "Since sniffer 10 the voipmonitor has feature which mirrors data from some remote sniffer database to another database. It replicates all partitions from certain date increasin...")
 
No edit summary
Line 1: Line 1:
Since sniffer 10 the voipmonitor has feature which mirrors data from some remote sniffer database to another database. It replicates all partitions from certain date increasingly syncing data to secondary database. You can have unlimited number of slave databases just for offloading or for backup purpose. Here is example of the configuration which will initiate full backup from 2014-06-10 from mysql server on 192.168.0.1 to localhost database creating the whole schema.  
Since sniffer 10 the voipmonitor has feature which mirrors data from some remote sniffer database to another database. It replicates all partitions from certain date increasingly syncing data to secondary database. You can have unlimited number of slave databases just for offloading or for backup purpose. Here is example of the configuration which will initiate full backup from 2014-06-10 from mysql server on 192.168.0.1 to localhost database creating the whole schema.  
This is /etc/voipmonitor.conf file on slave mysql database server:


  [general]
  [general]
Line 20: Line 22:
  cdr_sipport = yes
  cdr_sipport = yes
  cdr_rtpport = yes
  cdr_rtpport = yes
run the voipmonitor
/etc/init.d/voipmonitor start
or test manually with:
voipmonitor --config-file /etc/voipmonitor.conf -k -v 1

Revision as of 12:42, 17 June 2015

Since sniffer 10 the voipmonitor has feature which mirrors data from some remote sniffer database to another database. It replicates all partitions from certain date increasingly syncing data to secondary database. You can have unlimited number of slave databases just for offloading or for backup purpose. Here is example of the configuration which will initiate full backup from 2014-06-10 from mysql server on 192.168.0.1 to localhost database creating the whole schema.

This is /etc/voipmonitor.conf file on slave mysql database server:

[general]
sqldriver = mysql
mysqlcompress = yes
mysqlhost = 127.0.0.1
mysqldb = voipmonitor
cdr_partition = yes
mysqltable = cdr
mysqlusername = root
mysqlpassword = neupk,2
database_backup_from_date = 2014-06-10
database_backup_from_mysqlhost = 192.168.0.1
database_backup_from_mysqldb = voipmonitor
database_backup_from_mysqlusername = root
database_backup_from_mysqlpassword = pass
database_backup_pause = 3
database_backup_insert_threads = 3
cleandatabase = 70
cdr_sipport = yes
cdr_rtpport = yes

run the voipmonitor

/etc/init.d/voipmonitor start 


or test manually with:


voipmonitor --config-file /etc/voipmonitor.conf -k -v 1