CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Alternate upgrade process for minimal production downtime
Pages: [1]

Author Topic: Alternate upgrade process for minimal production downtime  (Read 681 times)

dschafer

  • I post occasionally
  • **
  • Posts: 93
  • Karma: 3
    • Backoffice Thinking
  • CiviCRM version: 3.2.3 - 4.4.4
  • CMS version: Drupal 6.x, 7.x, Wordpress
  • MySQL version: 5.1.x - 5.5.x
  • PHP version: 5.2.x - 5.4.x
Alternate upgrade process for minimal production downtime
August 19, 2010, 07:17:49 am
We have several clients where their website is the primary gateway into Civi but also serves a large non-civi related community.

In these cases we want to have the minimum downtown possible.

Would the following alternate approach be acceptable.

Before the step of taking the site off-line, perform the following:

1) Disable Civicrm module
2) Backup civi folders (if not already done as regular backup)
3) Backup civi database
4) Remove current install
5) Deploy upgrade version

Then the down time would consist of:
6) Login to drupal as admin
7) Take site off line
8) Enable civi module
8) Run Civi upgrade script
9) Put site online.

I would like to try this for a 3.2.1 upgrade for a client so any feedback would be very helpful.

Thanks,
   Dave

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Alternate upgrade process for minimal production downtime
August 19, 2010, 03:10:19 pm

in some cases i suspect the enabling of the civicrm module with an older DB and a new code base will cause issues

I would suggest not to disable the module, but create a new version outside htdocs and then do a mv to switch the old and the new and then the upgrade. you can potentially script the whole thing using drush and hence avoid having to type in commands/click links to upgrade site

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: Alternate upgrade process for minimal production downtime
August 20, 2010, 03:03:21 am
Yes, I agree with Lobo--don't enable CiviCRM before upgrading. The truth is that if CiviCRM is disabled I don't see a pressing reason to take the site offline either. In particular if you run this whole process once on a testbed, using of course the same code and DBs as the live site, and the upgrade goes smoothly. It should be quite safe then, I would think, to run the CiviCRM upgrade while Drupal is online.

I can't say 100% if this is recommended, but it should be quite safe IMO.
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Alternate upgrade process for minimal production downtime

This forum was archived on 2017-11-26.