From 1.6 to 2.0 recommended procedure

Hi,

I’m upgrading from 1.6 to 2.0 on new infrastructure so I can’t follow the guide Update to version 2.0.0.

Is there a recommended procedure for export/import of hosts with “tag,label”, rules?

Backup config 1.6 and restore on new version 2.0? Or export …/conf.d/wato/folder/hosts.mk, …/conf.d/wato/folder/rules.mk import on 2.0?

Thx.
Dario.

Why this. If you have a new infrastructure you should do on you old system a complete backup of your 1.6 installation. Restore this with the same 1.6 on the new infrastructure and then upgrade to 2.0 as described in the article.

1 Like

Hi @SAMDAR,

I agree with Andreas: The URL you posted, contains multiple scenarios how to update to 2.x, so I believe you can follow this guide. It even contains instructions how to do this “live” from one machine to the other.

As far as I’ve seen in this forum, multiple users have successfully used this method. Here is
one of the more recent examples: https://forum.checkmk.com/t/checkmk-post-centos-8-supported-distro/28466/12.

HTH,
Thomas

Hi @andreas-doehler, @openmindz,

My infrastructure consists of a physical master “centos 8” with two VM slaves “centos 8” connected to each other in distributed monitoring via TLS.

I was struggling to create a fully virtualized infrastructure on new redhat 8 machines recreate distributed monitoring and complete it via export and import.

Otherwise you say that I should first replace the physical master then follow the guide to upgrade to 2.0?

example:

  1. vm master creation

  2. I install checkmk 1.6

  3. restore backup master physical to master virtual

  4. check the connection to the slaves

  5. VM snapshot

  6. Upgrade OS to redhat 8

  7. upgrade Update to version 2.0.0

  8. Start

  9. rollback snapshot

Thx.
Dario.

Hi @SAMDAR

As far as I understood your initial post, your goal was/is to update one instance
from Checkmk 1.6.x to 2.0.x. Your last post is referring to a distributed monitoring setup,
so you need to update multiple instances.

As per the update guide, the recommended procedure to do this, is to stop all instances,
update all of them, and start them all up again: That’s all you need to take care of.

Checkmk, and updates for it, are - more or less - independent of your underlying OS, resp.
your infrastructure combinations. As such, I’m hesitant to give you a recommendation for
your “example” plan, but it does sound feasible… :slight_smile:

HTH,
Thomas

1 Like