Differences

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

--- xythos:upgrade_times_log [2011/08/01 15:27] – hmeij
+++ xythos:upgrade_times_log [2011/08/01 15:46] (current) – [Qs] hmeij
@@ Line 1: / Line 1: @@
 ====== 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:
@@ Line 14: / Line 14: @@
 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?