Difference between revisions of "How to backup settings of users in GUI"

From VoIPmonitor.org
Jump to navigation Jump to search
Line 20: Line 20:
  
 
== Restore ==
 
== Restore ==
If you wish to restore dumpfile, with with creation of a new db:
+
If you wish to restore dumpfile, start with a new db:
 
  mysqladmin create voipmonitor
 
  mysqladmin create voipmonitor
  
Let your latest sensor, creates new tables needed for voipmonitor service:
+
Let your latest sensor create tables needed for voipmonitor service:
 
  /etc/init.d/voipmonitor restart
 
  /etc/init.d/voipmonitor restart
  
Let your GUI creates tables needed for GUI, Just login to web GUI with your browser (If you are already logged in, logout first and then 'relogin'. (default login is admin / admin)
+
Let your GUI create tables needed for GUI, Just login to web GUI with your browser (If you are already logged in, logout first and then 're-login'. (default login is admin / admin)
 
  http://voipmonitor_IP
 
  http://voipmonitor_IP
  
Remove data from tables that are customizable by users/admins (because these data was dumped).
+
Remove data from tables that was auto-added in time of creation. (because these data are customizable and was dumped).
 
  mysql voipmonitor -e "SET FOREIGN_KEY_CHECKS = 0; TRUNCATE table tracker_category; TRUNCATE table tracker_priority; TRUNCATE table tracker_status; SET FOREIGN_KEY_CHECKS = 1;"  
 
  mysql voipmonitor -e "SET FOREIGN_KEY_CHECKS = 0; TRUNCATE table tracker_category; TRUNCATE table tracker_priority; TRUNCATE table tracker_status; SET FOREIGN_KEY_CHECKS = 1;"  
  
Line 36: Line 36:
  
  
 
+
Not recommended but can be useful [[other way to backup GUI settings]]
Not recommended but can be usefull [[other way to backup GUI settings]]
 

Revision as of 21:17, 23 November 2015

Backup

Run in bash following commandline to dump only users settings to /tmp/settings.sql


mydb='voipmonitor'; mysql ${mydb} -Ne "show tables from voipmonitor where \
  \`Tables_in_${mydb}\` LIKE 'alerts_%' OR \
  \`Tables_in_${mydb}\` LIKE 'cdr%' AND \
  \`Tables_in_${mydb}\` NOT LIKE 'cdr_custom_headers' OR \
  \`Tables_in_${mydb}\` LIKE '%country%' OR \
  \`Tables_in_${mydb}\` LIKE 'register%' OR \
  \`Tables_in_${mydb}\` LIKE 'cache_number_location' OR \
  \`Tables_in_${mydb}\` LIKE 'contenttype' OR \
  \`Tables_in_${mydb}\` LIKE 'files' OR \
  \`Tables_in_${mydb}\` LIKE 'live_packet' OR \
  \`Tables_in_${mydb}\` LIKE 'message' OR \
  \`Tables_in_${mydb}\` LIKE 'rtp_stat' OR \
  \`Tables_in_${mydb}\` LIKE 'system' \
  "| sed -e "s/^/--ignore-table=${mydb}./" |xargs mysqldump -c --skip-triggers --skip-add-locks --no-create-info ${mydb} > /tmp/settings.sql

Restore

If you wish to restore dumpfile, start with a new db:

mysqladmin create voipmonitor

Let your latest sensor create tables needed for voipmonitor service:

/etc/init.d/voipmonitor restart

Let your GUI create tables needed for GUI, Just login to web GUI with your browser (If you are already logged in, logout first and then 're-login'. (default login is admin / admin)

http://voipmonitor_IP

Remove data from tables that was auto-added in time of creation. (because these data are customizable and was dumped).

mysql voipmonitor -e "SET FOREIGN_KEY_CHECKS = 0; TRUNCATE table tracker_category; TRUNCATE table tracker_priority; TRUNCATE table tracker_status; SET FOREIGN_KEY_CHECKS = 1;" 

Restore settings

mysql voipmonitor < /tmp/settings.sql


Not recommended but can be useful other way to backup GUI settings