Database administration [Документация VAS Experts]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:dpi:dpi_components:platform:dpi_admin:admin_db:start [2019/10/25 12:47] lexx26en:dpi:dpi_components:platform:dpi_admin:admin_db:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
Line 1: Line 1:
-====== 2 Database administration ====== 
-{{indexmenu_n>2}} 
-The built-in database is fault-tolerant and does not require administration. 
-However, it has occurred in some rare cases that database has been corrupted. 
-In this case, the following options are possible: 
-  - database deletion and subsequent loading of data from scratch<code> 
-Stop dpi 
-service fastdpi stop 
-Delete database 
-/bin/rm /var/db/dpi/* 
-Launch dpi 
-service fastdpi start 
-Load all settings in the database from scratch  
-</code> 
-  - database recovery with data transfer <code> 
-Stop dpi 
-service fastdpi stop 
-Run script 
-mdb_dump -a -f dump.txt /var/db/dpi 
-/bin/rm /var/db/dpi/* 
-mdb_load -f dump.txt /var/db/dpi 
-Launch dpi 
-service fastdpi start 
-</code> 
  
-==== Activating the built-in database ==== 
- 
-User data repository or UDR is a built-in database. It permanently stores data on services and policing configuration for operator's subscribers. UDR activation is required to support dynamic IPs and subscribers with several IPs. 
- 
-UDR is activated by configuration parameter in file /etc/dpi/fastdpi.conf: 
-<code> 
-udr=1 
-</code> 
- 
-The database is placed to /var/db/dpi.