2GB MySQL InnoDB 500 Large Ubuntu Linux 64 bit Intel Dual Core 6400 4GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat Enterprise Intel Xeon 2xCPU 8GB Fast RAID10 MySQL InnoDB or PostgreSQL the base OpenSUSE configuration. 6.1.1 MySQL configuration changes • Binary log is disabled; • InnoDB is configured to store data for each table in a separate file. 6.1.2 Using a static IP address HISTORY Do not use if MySQL InnoDB, Oracle or PostgreSQL is used! zabbix[history_log] Number of values stored in table HISTORY_LOG Do not use if MySQL InnoDB, Oracle or PostgreSQL is used

cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL Software Version Comments MySQL 5.0 or later Required if MySQL is used as Zabbix backend database. InnoDB engine is required. 45 Software Version Comments Oracle 10g or later Required if Oracle is used additional UPDATEs. For better performance, especially with large databases on MySQL, increasing innodb_buffer_pool_size before upgrading is highly suggested. Also, disable binlog, if it is not needed

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended Software Version Comments MySQL 5.0.3 - 5.7.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. Note that MySQL 8.0 is not supported in Zabbix

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much (see database size Software Version Comments MySQL 5.0.3 - 5.7.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. Note that MySQL 8.0 is not supported in Zabbix

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended Software Version Comments MySQL 5.0.3 or later Required if MySQL is used as Zabbix backend database. InnoDB engine is required. Oracle 10g or later Required if Oracle is used as Zabbix backend database

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended Software Version Comments MySQL 5.0.3 or later Required if MySQL is used as Zabbix backend database. InnoDB engine is required. Oracle 10g or later Required if Oracle is used as Zabbix backend database

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much (see database size Software Version Comments MySQL 5.0.3 - 8.0.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. For MySQL we recommend using the C API (libmysqlclient)

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended Software Version Comments MySQL 5.0.3 - 5.7.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. Note that MySQL 8.0 is not supported in Zabbix

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much (see database size Software Version Comments MySQL 5.0.3 - 8.0.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. Oracle 10g or later Required if Oracle is

Small CentOS Virtual Appliance MySQL InnoDB 100 Medium CentOS 2 CPU cores/2GB MySQL InnoDB 500 Large RedHat Enterprise Linux 4 CPU cores/8GB RAID10 MySQL InnoDB or PostgreSQL >1000 Very large RedHat RedHat Enterprise Linux 8 CPU cores/16GB Fast RAID10 MySQL InnoDB or PostgreSQL >10000 Note: Actual configuration depends on the number of active items and refresh rates very much. It is highly recommended Software Version Comments MySQL 5.0.3 - 8.0.x Required if MySQL is used as Zabbix backend database. InnoDB engine is required. MariaDB also works with Zabbix. Oracle 10g or later Required if Oracle is