If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to REGISTER before you can post. To start viewing messages, select the forum that you want to visit from the selection below.
Download it... install it... migrate data from 1.4.x
I spent around 60 mins... but... all works fine.
Thanks guys for you good work
AndreA
Hi
I read that you migrated setting from 1.4 to 1.6. We're about to install 1.6 version on different box in different location. Can you please advice what the migration involves? Is it possible to Mysqldumb the database and copy conf files?
I read that you migrated setting from 1.4 to 1.6. We're about to install 1.6 version on different box in different location. Can you please advice what the migration involves? Is it possible to Mysqldumb the database and copy conf files?
Thanks
Yep.
After you restore the DB which will involve the creation of the Zabbix DB user to match the original you'll then need to perform the DB upgrade. After you get 1.6 up and running you'll need to point your clients at the new server unless the new server is taking over the original IP address. You will also want to double check the zabbix_*.conf files on the server just in case you forgot something. As for the frontend you won't need to copy over your origional the "install" screens will take care of it for you if you want. You also won't need to upgrade your agents to work with 1.6. At a recent site we did an upgrade and were using a 1.6 server with 1.1.6 agents.
After you restore the DB which will involve the creation of the Zabbix DB user to match the original you'll then need to perform the DB upgrade. After you get 1.6 up and running you'll need to point your clients at the new server unless the new server is taking over the original IP address. You will also want to double check the zabbix_*.conf files on the server just in case you forgot something. As for the frontend you won't need to copy over your origional the "install" screens will take care of it for you if you want. You also won't need to upgrade your agents to work with 1.6. At a recent site we did an upgrade and were using a 1.6 server with 1.1.6 agents.
Thanks for prompt reply!
This sounds good enough. I've done some more research and came across a post which says the v1.6 DB structure is also different from v1.4 but there is the upgrade script as you're saying.
The zabbix_agentd versions compatibility is also quite handy stuff. However I experienced a problem yesterday when I coudn't restart zabbix_agentd on one of our machines. This was due not deleted agent's semaphore record. This was apparently sorted in new version. I think upgrading agents might safe a headache in future by avoiding this kind of problem However will worry about the agents later.
Ok I'll carry on setting up zabbix on our dev box and cross fingers I'll be able to migrate settings.
In my case... i have backed up database for security. After backup i run a update script. Upgrade require in my case some minutes (not more than 10 mins).
Update frontend consist into delete old version and copy new php files
This sounds good enough. I've done some more research and came across a post which says the v1.6 DB structure is also different from v1.4 but there is the upgrade script as you're saying.
The zabbix_agentd versions compatibility is also quite handy stuff. However I experienced a problem yesterday when I coudn't restart zabbix_agentd on one of our machines. This was due not deleted agent's semaphore record. This was apparently sorted in new version. I think upgrading agents might safe a headache in future by avoiding this kind of problem However will worry about the agents later.
Ok I'll carry on setting up zabbix on our dev box and cross fingers I'll be able to migrate settings.
Thanks
There is no upgrade script per se... There is a sql upgrade file which will run a bunch of sql statements which will update the db. I think it's called update.sql or something similar and is found in the updates or create directories for sql.
The command you run will be similar to this:
cat update.sql | mysql -h <host (if needed) -u <user> -p (prompt for pw if needed) <database>
Comment