xythos:upgrade_times_log
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
xythos:upgrade_times_log [2011/08/01 15:27] hmeij |
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/ | + | Upgrade path: Each time we took a copy of production, changed database name and user/ |
| - | * Can we get rid of the prompting when upgrading? (username/ | + | * #1 Can we get rid of the prompting when upgrading? (username/ |
| | | ||
| 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/ | + | * #2 When executing fixServerPrincipleIDs script dev server can remain up (we tested). Is this true/ |
| - | * 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). |
| + | * #5 Can we skip the hotfix upgrades after running the script and go directly to 7.2.88, then to 7.2.91? | ||
xythos/upgrade_times_log.1312212466.txt.gz · Last modified: 2011/08/01 15:27 by hmeij
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
