Installation and deployment
Version 7.x > Installation and deployment > Upgrade from 6 to 7 View modes: 
User avatar
Member
Member
shelley.ford-celero - 2/11/2013 12:04:30 PM
   
Upgrade from 6 to 7
Hi,

We have two environments: dev and prod. We have KIM installed on our dev server but not our production server. When sites are created we run KIM in our dev environment, develop the site and then when it is time to implement into production we back up and restore db from dev to prod and copy the site files up from dev to prod.
With sites running 6 in production the only way we can upgrade to 7 is if we install KIM in production and run the upgrade through KIM on the applicable sites. Either that we will have to put a freeze on content updates while we bring a copy of prod down to dev, upgrade and test the site in dev and then move it back up. It seems export and import functions don't work on upgrades. Can you confirm that installing KIM on the production box is the best option to upgrade existing sites? Or am I missing something. The Blog doesn't really say anything.

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 2/11/2013 2:56:03 PM
   
RE:Upgrade from 6 to 7
You can run the KIM tool on your dev server for a remote site. In fact, you can run the KIM tool on your local machine and update a remote site.

Yes you are correct the export/import process will not work because you would be exporting from 7.x and importing the site into a code base of 6.x and database version of 6.x. So you will need to run the KIM tool on the live server to perform the update to your code and database and then if you needed/wanted import your site from dev (but technically you wouldn't need this if you just ran the KIM tool).

User avatar
Member
Member
shelley.ford-celero - 2/11/2013 3:40:20 PM
   
RE:Upgrade from 6 to 7
Thanks for the info! I'm now wondering how would you run the KIM tool on our dev server for a remote site. When I run KIM and click Register I'm asked for the name, URL and a path to where the files are located. We don't have a share to the production server. The only way to access the server is through remote desktop or FTP. Or am I looking at the wrong thing in KIM?

User avatar
Kentico Customer Success
Kentico Customer Success
kentico_martind2 - 2/12/2013 2:31:35 AM
   
RE:Upgrade from 6 to 7
Hello,

You should have a local instance of the KIM also on the dev server, right?

Best regards,
Martin Danko

User avatar
Member
Member
shelley.ford-celero - 2/12/2013 8:35:11 AM
   
RE:Upgrade from 6 to 7
That is correct. It is only on our dev server. It is not on the production server and it is not on my local machine.

User avatar
Kentico Customer Success
Kentico Customer Success
kentico_martind2 - 2/12/2013 8:50:30 AM
   
RE:Upgrade from 6 to 7
Hi Shelley,

So I would recommend you to copy your instance from dev server and then just change the configuration, e.g. settings in the Site Manager and web.config according to the previous version (of course, don't forget to make a back-up first).

Best regards,
Martin Danko

User avatar
Member
Member
esolutions - 7/11/2013 11:09:56 AM
   
RE:Upgrade from 6 to 7
Hi,
Sorry, I had to walk away from this project for a bit. When you say copy my instance from the dev server I just want to confirm that you are referring to the website. If that is what you mean I'm not sure I understand. Doesn't the upgrade also apply changes to the database? If so, then I can't move the db from dev to prod as it would overwrite the client's content would it not?

User avatar
Member
Member
esolutions - 7/11/2013 11:32:17 AM
   
RE:Upgrade from 6 to 7
I also want to add we don't have the sites set up under the default web site. We have them set up as separate sites. Each has their own URL like sitename.dev in dev and in production www.sitename.ca or whatever.

User avatar
Kentico Customer Success
Kentico Customer Success
kentico_martind2 - 7/11/2013 5:43:03 PM
   
RE:Upgrade from 6 to 7
Hello,

By copying I mean to copy a whole application folder, e.g. C:\inetput\wwwroot\kentico
Upgrade apply changes to the DB but doesn't change any content, it will just update or create necessary tables used by the application but any content of the website won't be affected. So I don't see any problem with that. Also as I mentioned, don't upgrade anything without making a backup of the application as well as the Database as first.

Best Regards,
Martin Danko