guides:reference:database:database
LDAP: couldn't connect to LDAP server
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
guides:reference:database:database [2020/01/06 13:25] – [CMDB database] yspeerte | guides:reference:database:database [2020/01/06 13:53] (current) – [NCCM database] yspeerte | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{indexmenu_n> | ||
+ | |||
+ | ====== NetYCE database ====== | ||
+ | |||
+ | NetYCE uses the public domain database version of the MySQL, MariaDB. Supported version of MariaDB are 10.0, 10.1 and 10.2 and all its subversions. When using multiple NetYCE servers (requiring a ' | ||
+ | |||
+ | The NetYCE server configuration is defined using the setup script ''/ | ||
+ | |||
+ | Although NetYCE uses one database engine per server, the database setup uses five distinct databases, each with their specific functions: | ||
+ | * YCE | ||
+ | * LOGS | ||
+ | * CMDB | ||
+ | * NMS | ||
+ | * NCCM | ||
+ | |||
+ | ===== YCE database ===== | ||
+ | |||
+ | The **YCE** database has all the core NetYCE tables that make up the base application. It manages the data for the modelling (// | ||
+ | |||
+ | The YCE database also contains the User and User group administration, | ||
+ | |||
+ | For users wishing to familiarize themselves with the principal YCE tables and their relations, the NetYCE entity-relationshp-diagram or [[guides: | ||
+ | |||
+ | The YCE database is backed-up automatically every day and maintains a 15 day archive-history by default. Maintenance is performed daily to detect and repair table corruptions. | ||
+ | |||
+ | |||
+ | ===== LOGS database ===== | ||
+ | |||
+ | The NetYCE **LOGS** database maintains some logs in the database for sharing between the various servers. These logs include the Job logs (executing jobs on network devices), the Task logs (api requests and responses), and the Action log (user actions). | ||
+ | |||
+ | Since these logs can be quite extensive on busy systems and offer a detailed view of all NetYCE activity, a database design was adopted to allow very long retention times and an un-alterable history. Each logging table actually consists of many concatenated write-once, read-only tables, each table covering exactly one week of created records. The weekly rollover deletes the oldest week and re-creates the " | ||
+ | |||
+ | The LOGS database is backed-up automatically every day and maintains a 15 day archive-history by default. Maintenance is performed daily to detect and repair table corruptions and execute the weekly ageing rollover. | ||
+ | |||
+ | |||
+ | ===== CMDB database ===== | ||
+ | |||
+ | Where the YCE database hosts the NetYCE modelled and managed node definitions, | ||
+ | |||
+ | The CMDB tables can be manipulated using the NetYCE front-end (" | ||
+ | |||
+ | The CMDB database is backed-up automatically every day and maintains a 15 day archive-history by default. Maintenance is performed daily to detect and repair table corruptions. | ||
+ | |||
+ | |||
+ | ===== NMS database ===== | ||
+ | |||
+ | Adding custom tables can be done in the **NMS** database. These tables can be defined and created using any SQL management tool. Access privileges for the "Admin - Custom data" tool are automatically added when a new table is detected (or use '' | ||
+ | |||
+ | Direct SQL (write) access to these tables is granted using the MariaDB "// | ||
+ | |||
+ | The NMS database is backed-up automatically every day and maintains a 15 day archive-history by default. Maintenance is performed daily to detect and repair table corruptions. | ||
+ | |||
+ | |||
+ | ===== NCCM database ===== | ||
+ | |||
+ | The **NCCM** database is the base for **NCCM** (' | ||
+ | |||
+ | As with the LOGS database, the NCCM tables maintaining the configuration history are broken up in week-data tables which are rotated and merged weekly. This setup allows for the default 800 days of configuration history. | ||
+ | |||
+ | Additional tables are present to manage the NCCM and Compliance processes. Data in the tables in the NCCM database should be __not__ modified unless indicated by NetYCE since all are managed by these processes. | ||
+ | |||
+ | The NCCM database is backed-up automatically every day and maintains a 15 day archive-history by default. The NCCM database archive is created separate from the archive containing the YCE, LOGS, NCCM and CMDB databases. The NCCM archives can therefore be restored independently from the YCE archives. | ||
+ | |||
+ | Maintenance is performed daily to detect and repair table corruptions and execute the weekly ageing rollover. | ||
+ | |||
+ | |||