1 / 6

Upgrade & Patching of Kentico CMS

Upgrade & Patching of Kentico CMS. …without any much pain. My Checklist . Have you reviewed the docs? Can the site be taken offline? Do you have access to the database? Do you have access to the web server file system? Do you have the latest patch for your version?

mandel
Download Presentation

Upgrade & Patching of Kentico CMS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Upgrade & Patching of Kentico CMS …without anymuch pain

  2. My Checklist • Have you reviewed the docs? • Can the site be taken offline? • Do you have access to the database? • Do you have access to the web server file system? • Do you have the latest patch for your version? • Have you notified Editors and/or Developers? • Have you locked them out? • No, really… have you? If you answered “yes” to these then proceed Note: The cumulative hotfixes contains all bug fixes from the previous hotfixes of the same version. So patch 5.0.19 contains all the fixes up to that point.

  3. The short way vs. The safe way You can update a live site • Takes less time – possibly more risky • Possibly late at night – not a great option • As long as you have File and Database backups (not site exports). • You locked the users out of the site (at router or using security) Or you can do it the safe way… • Takes more time • Very safe • Site flips to new version with minimal or no downtime The choice is yours to make Note: There are many right ways to complete an update, your situation may vary from server to server. In doubt have backups and time.

  4. The safe way • Lockout “changers” (editors, developers, etc) • Backup the database, then restore into a new database • Copy the website file base into a new folder (note: check permissions) • Set the copied sites web.config to use new database • Set up a new IIS site to use the new site files using a temp domain name • Now you have 2 sites in a mirror, the live site is still up and the copy is upgradable • Using the patch or upgrade procedure, update the temp site • Tip: When upgrading the site files, I use a file compare tool to examine the file changes before I copy them. This allows one to see if your customizations (if any) will be affected. Update your code as needed / if needed. • Tip: If updating the temp site more than 1 patch or version, load the site up between each and test it, this allows for some database scripts to run for that version ensuring a completed update. • Tip: Test the site on the temp domain until your comfortable with it. Seriously. • Site transition • Stop the old iis site, change the host headers (if used) so that the new site is now the main domain used and restart the site. Then, re-enable the “changers”. • If there are any issues, you can possibly swap the IIS host headers back to bring the old site online.

  5. Demo Time • Patching 5.0 to 5.0.19 • Upgrading Kentico 5.0.19 to 5.5

  6. Questions? What about: Webfarms? Staged servers? Multi-sites? Contact info: support@kentico.com neilp@kentico.com

More Related