Upgrade from 2.8.6 to 4.0.1 and move to another server

  • Resolved waynesmall

    (@waynesmall)


    10 years, 2 months ago

    Ok – please don’t beat me up on this, but my site has been running WP 2.8.6 for some time.
    Over the Christmas holidays, I’m planning to move it from it’s current Windows Server 2008 server over to a 2012R2 server and also upgrade it to the most current version of WordPress at the same time.

    I’m looking for tips/tricks/guidance on how to handle this. I’m an IT guy myself, and can handle the windows side of things without worry – more looking to find out the collective wisdom on the process for moving it and then upgrading it.

    Many thanks!

Viewing 10 replies - 1 through 10 (of 10 total)
  • Moderator James Huff

    (@macmanx)

    It would probably be best to do a manual update, follow the (very) detailed guide at https://codex.www.ads-software.com/Upgrading_WordPress_Extended

    Now, this is very important, do not go directly to WordPress 4.0.1. Instead, follow this and update across two versions at a time: https://codex.www.ads-software.com/Upgrading_WordPress_Extended#Upgrading_Across_Multiple_Versions

    Thread Starter waynesmall

    (@waynesmall)

    Oh wow – thank you James – I really should not have let it get so far behind ??

    I’m thinking that I should move it to the new server as it’s current version first, and then do the upgrades on the new server – that way I can leave the old server online while I do the work on the new server.

    Do you have any links to handle migrations like this?

    Moderator James Huff

    (@macmanx)

    We sure do! ??

    https://codex.www.ads-software.com/Moving_WordPress

    Thread Starter waynesmall

    (@waynesmall)

    Thanks – it’s obvious to me, that I need to read the codex more huh ??
    James – do you have any opinion on my comment about moving it to the new server as a 2.x site, testing it locally with a hosts file, and then doing the upgrades on that site?
    BTW – appreciate your responses – many thanks.

    Moderator James Huff

    (@macmanx)

    If there isn’t preventing you from upgrading now, I’d personally prefer to do the upgrade before the move.

    Thread Starter waynesmall

    (@waynesmall)

    My thought was that if I upgrade on the production system and it goes wrong, then the site is offline till I fix it, however if I move the site first, test it and then upgrade it on the new server, no one will know it’s broken until I cutover DNS to point to the new server.

    Moderator James Huff

    (@macmanx)

    If you comfortable wrangling the DNS and hosts file locally, then you shouldn’t have much of a problem upgrading in development before you switch back the DNS.

    It’s just personally easier for me to move first, upgrade second, and then panic if it crashes, but I know I’m an edge case. ??

    Thread Starter waynesmall

    (@waynesmall)

    Thanks mate – DNS/Hosts file is not an issue for me at all.
    hehe – I suspect I’m an edge case too some days. thanks so much for the prompt responses and great info – will let you know how I go!

    Moderator James Huff

    (@macmanx)

    You’re welcome!

    Thread Starter waynesmall

    (@waynesmall)

    James – I thought I’d come back and let you know how it all went.
    1. I restored my server in my home test environment and despite all warning, attempted to upgrade direct from 2.8.6 to 4.1… and it worked! I figure therefore I must have a pretty simple site, so Today I attempted the upgrade of the live site from 2.8.6 to 4.1 on the existing (old server)… and it worked too.
    Now I’m busy moving it over to the new server… will report back later once it’s done…

    Many thanks – Wayne

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Upgrade from 2.8.6 to 4.0.1 and move to another server’ is closed to new replies.

Tags