Ad Widget

Collapse

New install howto?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Abzstrak
    Junior Member
    • Dec 2022
    • 9

    #1

    New install howto?

    I'm migrating from our single large machine to multiple backend servers, timescale HA db servers and deploying proxies.... is there any articles anyone has written up on setting things up from scratch? especially with timescale, since Im not very familiar with it
  • Jason
    Senior Member
    • Nov 2007
    • 430

    #2
    Ok. First of all if you've a working system don't touch it till the actual migration point. What is your database on that? mysql or postgres?

    If your original one is postgres then migrating to timescale isn't too hard and I've done the process here a couple of times. There is documentation on how to enable timescale on an existing database. https://blog.zabbix.com/upgrading-za...for-timescaled

    The method I followed is roughly outlined below. Ours is a virtual environment so I made liberal uses of snapshots to go back to virgin states on the servers, if you're physical then there is a little more work.
    If database is large consider dropping the amount of history you are keeping till migration complete as it massively impacts on migration time.
    used pg_dump to clone the existing database to a new server. (make note of time to do it)
    Add in extension timescale. If you want to use compression make sure you use the timescale repo not the postgres repo.
    Migrate database to timescale. (takes a long time depending on database size). Make note of all the SQL you've used
    Test connecting new zabbix server to this database and check that upgrade is successful and no errors.

    Once you've worked through all that should have a migration time and a sql document can just run on the data once copied over.

    I've investigated methods for very little downtime, but always found niggles with how they work with active triggers etc and the one above worked fine for us. The only thing is run through the whole migration more than once to make sure ironed out any bugs so when actually migrate the data for real all is smooth and stress free. I'd suggest stopping zabbix server before do the actual migration to make sure that no triggers etc are lost. If you've lots of proxies then should be able to buffer most of your data so almost nothing will be lost.

    Comment

    • Abzstrak
      Junior Member
      • Dec 2022
      • 9

      #3

      thanks for the link, it is useful. I dont plan on converting anything, i plan to just run the two installations in parallel for a time to not have to deal with migrating data plus uptime isnt an issue

      I'm moving from a single server running a single server with postgresql on it to a HA setup with HA timescale DB's and multiple proxy's. I figured a GSLB for loadbalancing the front end via F5's would make sense as well.

      Comment

      Working...