Migrate path from 4.5.6-33 to 4.5.7-43

Discussion in 'Installation and "How-To" Questions' started by Roy Boverhof, May 8, 2017.

  1. Roy Boverhof

    Roy Boverhof Kilo Poster

    Messages:
    40
    I am running 4.5.6-33 on Centos 5, 32 bit. According to the documentation I must update my current server and then migrate it, but this only works for 86_64.

    I have 4.5.7-43 running on a new virtual machine, I just have no idea how to migrate to this machine as "hspc-mn-backup" fails. (which kinda makes sense)

    So I think I need to install 4.5.6-33 on Centos 6, migrate the database and then upgrade. But I can't find any download links anywhere.
     
    Last edited: May 8, 2017
  2. Roy Boverhof

    Roy Boverhof Kilo Poster

    Messages:
    40
    After some guessing I found I could download the old version here: download.automation.odin.com/obas/4.5/update6/obas-4.5.6-33.x86_64.tar

    Now migrate still fails, so I just made sure all packages were in sync and then disabled the rpm checks with --no-rpm-check when running hspc-mn-backup. Also make sure to use the -d flag as this does a database dump instead of a copy.

    Once I verified the old version was running, I upgraded it to 4.5.7-43. Works perfectly! I just needed to remove the perl-Parse-CPAN-Meta package (https://kb.odin.com/en/119999) and disable the following services: cpuspeed & mdmanager (https://kb.odin.com/en/113455)
     
  3. dkolvakh

    dkolvakh Odin Team

    Messages:
    348
    Hello.

    Especially for such cases, we made improvements in the "hspc-mn-backup" utility. Please check this article https://kb.odin.com/en/2126 for "--check-migrate" option description. The new version of this utility has been attached to that KB.
     
  4. Roy Boverhof

    Roy Boverhof Kilo Poster

    Messages:
    40
    I noticed, but when reading that article it isn't quite clear what the --check-migrate flag does. When looking at the source I see: "Perform product components validation on source and target systems only. Services will not be stopped and no actual data transferred."

    In my case the names of the packages didn't match because of the differences between the 32 and 64 bit versions. Perhaps it's also an idea to keep a list of versions / download url's somewhere... only by doing some URL guessing I was able to download the old version and install that on the new host.
     
  5. dkolvakh

    dkolvakh Odin Team

    Messages:
    348
    There should be no difference, script takes into account only pakage name itself, without architecture.
    Unfortunately, due to company restrictions and obligations, we cannot keep direct download links public. But in any case, contacting your sales representative or support will help to get them.
     

Share This Page