https://wiki.netyce.com/ 2026-05-01T10:08:31+00:00 https://wiki.netyce.com/ https://wiki.netyce.com/lib/exe/fetch.php?media=wiki:logo.png text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:database:database&rev=1720009873&do=diff 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 'Full' architecture licence key), it is recommended to configure the two servers running a database in a Master-Master replication setup. More than two database servers are not supported. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:database:database_replication&rev=1720009873&do=diff Database Replication On deployments using two YCE servers or more, two YCE databases can be setup using master-master replication. This setup offers redundancy with instant fail over capabilities. Although the installation always creates a master-master configuration, the administrator can assign a primary and a secondary database server to each of the front-ends, allowing any combination of master-slave or master-master relationships. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:database:database_sync_repair&rev=1720009873&do=diff NetYCE Database Re-synchronization procedure Refer to the two NetYCE database servers as PRI and SEC although this assignment has nothing to do with the actual organization and hierarchy. Think of it as the local and remote NetYCE database server respectively. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:database:datamodel&rev=1720009873&do=diff YCE datamodel ERD The main database, 'YCE', forms the heart of the application and is accessible but not alterable by the customer. A second database, 'NMS', is used to contain custom tables or tables used by integrations with NMS applications. This database is open to the customer. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:database:dbusers_and_grants&rev=1720009873&do=diff DB users and grants NetYCE database permissions are dependent on the database user. The NetYCE application primarily uses the “touchup” user. This user is permitted to access all databases and modify their contents, but cannot modify or create tables. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:database:encryption&rev=1720009873&do=diff Encryption NetYCE uses encryption in several places of the application: * User authentication passwords * Application Login forms * Distribution files * Customer database backups (archives) * Selected columns in the database User passwords text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:database:manual_database_restore&rev=1720009873&do=diff Manual database restore procedure " We are currently working on a new method of importing and exporting the database. Starting from version 8.2.2, this procedure will be deprecated." NetYCE database archive sets are normally restored using the front-end tool