User Tools

Site Tools


xythos:upgrade_times_log

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
xythos:upgrade_times_log [2011/08/01 15:26]
hmeij [Qs]
xythos:upgrade_times_log [2011/08/01 15:46] (current)
hmeij [Qs]
Line 1: Line 1:
 ====== Qs ====== ====== Qs ======
  
-Upgrade path:  Each time we took a copy of production, changed database name and user/password properties (xml properties file and inside database). Also staged content area (except in FIRST).+Upgrade path:  Each time we took a copy of production, changed database name and user/password properties (xml properties file and inside database). Also staged content area (except in FIRST).  We have 5 questions:
  
-  * Can we get rid of the prompting when upgrading? (username/passwd, tables for datastores ... just accept defaults provided)+  * #1 Can we get rid of the prompting when upgrading? (username/passwd, tables for datastores ... just accept defaults provided)
  
  Summary of THIRD attempt:  Summary of THIRD attempt:
Line 14: Line 14:
 upgrade 7.2.91 (1:10)\\ upgrade 7.2.91 (1:10)\\
  
-  * When executing fixServerPrincipleIDs script dev server can remain up (we tested). Is this true/advisable for production upgrade? +  * #2 When executing fixServerPrincipleIDs script dev server can remain up (we tested). Is this true/advisable for production upgrade? 
-  * If yes above, should we while production is up, consider running in batches (directory trees) or all at once? +  * #3 If yes above, should we while production is up, consider running in batches (directory trees) or all at once? 
-  * Can we skip the hotfix upgrades after running the script and go directly to 7.2.88, then to 7.2.91?+  * #4 If answer is no, server must be down: when we apply the 7.2.88 upgrade (without fixServerPrincipleIDs script manually, this upgrade seems to automatically invoke it) script **and** upgrade take 19 hours (second attempt) versus script by itself only takes 20 hours (third attempt).  Why? 
 +  * #5 Can we skip the hotfix upgrades after running the script and go directly to 7.2.88, then to 7.2.91?
  
  
Line 26: Line 27:
    
  
-FIRST: **copy of prod db on filer1, no content\\+**FIRST:** \\ 
 +**copy of prod db on filer1, no content\\
 exactly what hong did, achieved about similar times, roughly 6 hours + pre/post work**\\ exactly what hong did, achieved about similar times, roughly 6 hours + pre/post work**\\
 ...upgrade to 7.2.88...\\ ...upgrade to 7.2.88...\\
Line 45: Line 47:
 Jul 27, 2011 3:20:47 PM -- Exited successfully - 0:50 \\ Jul 27, 2011 3:20:47 PM -- Exited successfully - 0:50 \\
  
-SECOND: **copy of prod db on filer4, with content, roughly 20 hours + pre/post work**\\+**SECOND:**\\ 
 +**copy of prod db on filer4, with content, roughly 20 hours + pre/post work**\\
 ...upgrade to 7.2.88...\\ ...upgrade to 7.2.88...\\
 Jul 27, 2011 6:35:55 PM -- Xythos Database Schema Installer Version 7.2.88.1020 - (cumulative time)\\ Jul 27, 2011 6:35:55 PM -- Xythos Database Schema Installer Version 7.2.88.1020 - (cumulative time)\\
Line 64: Line 67:
  
  
-THIRD: **copy of prod db on filer4, with content **\\+**THIRD:**\\ 
 +**copy of prod db on filer4, with content **\\
 ...hotfix 7.1.37_24 (contains the fixInternalPrincipalIDs script ) on current version...\\ ...hotfix 7.1.37_24 (contains the fixInternalPrincipalIDs script ) on current version...\\
 download and unpack\\ download and unpack\\
xythos/upgrade_times_log.1312212397.txt.gz · Last modified: 2011/08/01 15:26 by hmeij