• Replies 2 replies
  • Subscribers 338 subscribers
  • Views 122 views
  • Users 0 members are here
Related

v12.51 to v15 upgrade question - regarding installing on new servers.

Dean Yager
$organization

I am setting up new servers for my v15 environment.  I have done the server prep for v15.  Do I need to use TIM and install v12.51, then copy my database over, then upgrade to v15?  Or can I copy the database over and use v15 TIM to upgrade the database and  v15 TIM to install all the other servers. 


Does that make sense?

Dean

Parents
  • $organization

    Yup! I just did a similar thing for our v14 upgrade:

    All of the application services on the new farm should be installed as version 15. You can even get the whole thing running on the updated version and test your migration and update before you cut over.

    When you are ready to do the actual upgrade for production, your maintenance window should look something like this:

    1. Stop all services and app pools on the new farm (as well as the old farm)
    2. Migrate the database to the new database server
    3. Run the database upgrade and migration processes with TIM (this is actually detailed in one of the installation docs)
    4. Restart the app pools and services on the new farm

    When I did my upgrade from 12.5.1 to 14.1.7, I had a 22-step migration checklist, had done a number of test runs in advance, and had a bunch of database stuff scripted out. Got back online 50 minutes after the maintenance window began! Our db is still tiny enough to back up to about 1.4GB compressed, but let me know if you beat my time ;-)

Reply
  • $organization

    Yup! I just did a similar thing for our v14 upgrade:

    All of the application services on the new farm should be installed as version 15. You can even get the whole thing running on the updated version and test your migration and update before you cut over.

    When you are ready to do the actual upgrade for production, your maintenance window should look something like this:

    1. Stop all services and app pools on the new farm (as well as the old farm)
    2. Migrate the database to the new database server
    3. Run the database upgrade and migration processes with TIM (this is actually detailed in one of the installation docs)
    4. Restart the app pools and services on the new farm

    When I did my upgrade from 12.5.1 to 14.1.7, I had a 22-step migration checklist, had done a number of test runs in advance, and had a bunch of database stuff scripted out. Got back online 50 minutes after the maintenance window began! Our db is still tiny enough to back up to about 1.4GB compressed, but let me know if you beat my time ;-)

Children