Upgrading from 2.2.12 to next version

[zabbixfk]

Upgrading from 2.2.12 to next version

I was able to upgrade using below steps.

- Compile 3.0.10 version on my machine with mysql - before install all the dependencies.
- Source mysql db dump from 2.2.12 version.
- Start zabbix_server - this did the upgrade.

Below are the commands used
Install PHP 5.5, mysql, used webstatic repo

rpm -ivh http://mirror.webtatic.com/yum/el6/latest.rpm
yum install php55w php56w-gd php56w-bcmath php56w-xml php56w-mbstring php56w-mcrypt php56w-mysql php56w-pear php56w-pear php56w-pecl* php56w-process php56w-snmp php56w-soap php56w-odbc php55w-common
yum -y install mysql55w-server mysql55w

Now OpenIPMI, SSH2, SNMP

yum -y install OpenIPMI ipmitool ipmiutil
yum -y install libssh2 libssh2-devel
yum -y install fping
yum -y install net-snmp*
yum -y install partprobe lsof mod_ssl logrotate traceroute iftop

Setup mysql and source 2.2.12 database

mysql_secure_installation
mysql -uUSER -pPASSWD -e 'CREATE DATABASE zabbix character set utf8 collate utf8_bin';
nohup mysql -uUSER -pPASSWD zabbix < zabbix_db_dump_from_2.2.12.sql &

Compile ZBX

tar xvf zabbix-3.0.10.tar.gz
cd zabbix-3.0.10
./configure --enable-server --enable-agent  --with-mysql --with-libxml2 --with-ssh2 --with-net-snmp --with-openipmi  --with-openssl --with-libcurl

I had used nohup and & as my db size were 150G+.

So far all seems good. I still need to test proxy part, not sure how that works though. Any inputs/improvements/suggestions are greatly helpful.

Thanks.

[jgalego]

Upgraded successful from 2.2.20 to 3.0.11 LTS.

We use AWS, and try to use AWS Linux for everything we can. For our Zabbix, we have one EC2 instances with a RDS MySQL database, and 4 Proxies, 3 at AWS 1 OnPremises.

The steps:

- create a new EC2 instance (prepared everything as we use PagerDuty, Slack and AWS SES for the alerts) using the el6 repo for Zabbix 3.0 LTS with AWS Linux/CentOS 6 using:

rpm -ivh http://repo.zabbix.com/zabbix/3.0/rhel/6/x86_64/zabbix-release-3.0-1.el6.noarch.rpm

- snapshot the RDS instance;

- create a new RDS to check if the upgrade would go faultless (it was perfect!);

- changed the zabbix.conf at the 3.0.11 server to point to the original RDS;

- stopped the zabbix 3.0.11 server;

- stopped the zabbix 2.2.20 server;

- changed the Elastic IP to the new server;

- started the zabbix 3.0.11 server (it automatically started a new migration which took 3 minutes);

- Everything was right at the new server and surprisingly the 2.2 proxies are communicating with the 3.0.11 server (which was nice, besides we had already 3.0 proxies ready, but gave us time to upgrade each of the 4) ;

- decommissioned the temp RDS and the 2.2.20 server (just stopped them for the next 7 days);

Nice to have the Zabbix 3.0.x LTS and the AWS Linux 2017.09 working perfectly.

[zabbixfk]

[CLOSED] Upgrading from 2.2.12 to next version

Thanks all for the valuable reply.

Was able to upgrade from 2.2.12 to 3.0.13 ( that was LTS version available last Dec).

Steps:
1). Backup of everything - Mysql DB dumps. Source file copying.
2). Bringing up exact replica - was able to get VM's of existing configs - this really helped
3). Sourcing the backup of master on the new machine - this in my case took lot of time. I was expecting for 150G mysql db, with 32G ram , 4-5 hours enough , but took ~ 8Hrs.
4). During the source, monitoroing data is lost - replication didnt happen so its ok.
----STOP All including proxies.
5). Bring down master, bring up new master - after installing new zbx 3.0.13, start zabbix_server - this upgrades db. ( MySql version check required, older had 5.0.x, new required 5.5.x, for CentOS, used webstatic repos.)
6). Once the DB is up, start server, meanwhile bring up proxy one by one. Proxy db's were in MB's sou bring up took 5-10 mins. Similar to server, running zabbix_proxy upgrades db in proxies.
7). Once the new machine is up, swap the IP address from older to new.
8). Clients starts reporting to new machines.

All well

Thanks.