manual:installation:upgrade_notes_320

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
manual:installation:upgrade_notes_320 [2017/03/17 12:27]
martins-v numbering fix
manual:installation:upgrade_notes_320 [2018/02/22 08:50]
martins-v fixing typo
Line 1: Line 1:
 ==== 10 Upgrade notes for 3.2.0 ==== ==== 10 Upgrade notes for 3.2.0 ====
  
-These notes are for upgrading from Zabbix 3.0.x to Zabbix 3.2.0.+These notes are for upgrading from Zabbix 3.0.x to Zabbix 3.2.0. ​All notes are grouped into: 
 + 
 +  * ''​Critical''​ - the most critical information related to the upgrade process and the changes in Zabbix functionality 
 +  * ''​Informational''​ - all remaining information describing the changes in Zabbix functionality
  
 It is possible to upgrade to Zabbix 3.2.0 from versions before Zabbix 3.0.0. See the [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions. It is possible to upgrade to Zabbix 3.2.0 from versions before Zabbix 3.0.0. See the [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions.
 +
 +==== Critical ====
 +
 +=== Database upgrade ===
 +
 +The history_text.id and history_log.id fields will be removed from the corresponding history tables during database upgrade. Depending on the history table size this process can be slow.
  
 === Case-sensitive MySQL database === === Case-sensitive MySQL database ===
  
 A case-sensitive MySQL database is required for proper server work. It is [[:​manual/​appendix/​install/​db_scripts#​mysql|recommended]] to create a case-sensitive MySQL database during new installations. If you created a MySQL database with the utf8 character set previously, in order to support case sensitiveness of stored data, you need to convert the charset to utf8_bin. A case-sensitive MySQL database is required for proper server work. It is [[:​manual/​appendix/​install/​db_scripts#​mysql|recommended]] to create a case-sensitive MySQL database during new installations. If you created a MySQL database with the utf8 character set previously, in order to support case sensitiveness of stored data, you need to convert the charset to utf8_bin.
 +
 +==== Informational ====
  
 === Escalation changes === === Escalation changes ===
Line 13: Line 24:
 == Delaying escalations during maintenance == == Delaying escalations during maintenance ==
  
-The logic of delaying problem notifications during host maintenance has been changed. ​+The logic of delaying problem notifications during host maintenance ​[[:​manual/​introduction/​whatsnew320#​delaying_escalations_during_maintenance|has been changed]]
  
-In previous Zabbix versions, problem notifications during a host maintenance period were "​suppressed" ​if you were using the //​Maintenance status = not in "​maintenance"//​ action condition. In the new version, the old mechanism is dropped. Instead there is an new //Pause operations while in maintenance//​ option in action configuration,​ which allows to pause notifications ​in the host maintenance ​phase if you wish so. +In previous Zabbix versions, problem notifications during a host maintenance period were skipped ​if you were using the //​Maintenance status = not in "​maintenance"//​ action condition. In the new version, the old mechanism is dropped. Instead there is new //Pause operations while in maintenance//​ option in action configuration,​ which allows to pause notifications ​during a maintenance if you wish so. 
  
 To ensure that escalations using this functionality work properly after the upgrade you must reconfigure the relevant actions by: To ensure that escalations using this functionality work properly after the upgrade you must reconfigure the relevant actions by:
Line 24: Line 35:
 == Parallel escalation for each of multiple PROBLEM events == == Parallel escalation for each of multiple PROBLEM events ==
  
-Before Zabbix 3.2 every new //PROBLEM// event would abort escalation of earlier //​PROBLEM// ​events, i.e. only one active escalation could run for a trigger with multiple event generation. Now escalation procedures for all these events are processed in parallel. This change and newly introduced [[manual/​config/​event_correlation|event correlation]] and [[manual/​config/​triggers/​event_tags|event tags]] enable more flexible approach to multiple //PROBLEM// event resolution. For example, depending on configuration now //OK// event may either stop escalation for the particular //PROBLEM// event, for numerous events or for all of them. +Before Zabbix 3.2 every new //PROBLEM// event would abort the escalation of an earlier //​PROBLEM// ​event, i.e. only one active escalation could run for a trigger with multiple event generation. Now escalation procedures for all these events are processed in parallel. This change and newly introduced [[manual/​config/​event_correlation|event correlation]] and [[manual/​config/​triggers/​event_tags|event tags]] enable more flexible approach to multiple //PROBLEM// event resolution. For example, depending on configuration now //OK// event may either stop escalation for the particular //PROBLEM// event, for numerous events or for all of them. 
  
  
Line 47: Line 58:
  
 Recovery operations also get a dedicated tab in the action configuration form, while the condition tab has been dropped and conditions now can be set in the general action property tab. Recovery operations also get a dedicated tab in the action configuration form, while the condition tab has been dropped and conditions now can be set in the general action property tab.
- 
-=== Database upgrade === 
- 
-The history_text.id and history_log.id fields will be removed from the corresponding history tables during database upgrade. Depending on history table size this process can be slow. 
  
 === IBM DB2 connection encoding === === IBM DB2 connection encoding ===
Line 94: Line 101:
  
 When item property "Type of information"​ is changed, previous history and trend data will not be displayed in graphs. When item property "Type of information"​ is changed, previous history and trend data will not be displayed in graphs.
- 
---------------------------------------------------