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 Next revision Both sides next revision | ||
|
xythos:upgrade_times_log [2011/08/01 09:45] hmeij |
xythos:upgrade_times_log [2011/08/01 11:26] hmeij [Qs] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Qs ====== | ====== Qs ====== | ||
| - | | + | |
| - | * what causes the internal id fix to take so long when content | + | Upgrade path: Each time we took a copy of production, changed database name and user/ |
| - | * | + | |
| + | | ||
| + | |||
| + | | ||
| + | |||
| + | stage version 7.1.37.13\\ | ||
| + | ./ | ||
| + | hotfix 7.1.37_sp2 (skipped)\\ | ||
| + | upgrade to 7.2.88 (1:50)\\ | ||
| + | hotfix 7.2.88.sp2 (skipped)\\ | ||
| + | upgrade 7.2.91 (1:10)\\ | ||
| + | |||
| + | * When executing fixServerPrincipleIDs script dev server can remain up (we tested). Is this true/ | ||
| + | * If yes above, should we while production | ||
| + | * Can we skip the hotfix upgrades after running the script and go directly to 7.2.88, then to 7.2.91? | ||
| + | |||
| + | |||
| + | |||
| + | |||
| ====== UPGRADE TIMES BY MATT/HENK ====== | ====== UPGRADE TIMES BY MATT/HENK ====== | ||
| Line 46: | Line 65: | ||
| THIRD: **copy of prod db on filer4, with content **\\ | THIRD: **copy of prod db on filer4, with content **\\ | ||
| - | ...hotfix 7.1.37_24 on current version...\\ | + | ...hotfix 7.1.37_24 |
| - | download and unpack | + | download and unpack\\ |
| - | fix java path or stage old java | + | fix java path or stage old java\\ |
| - | ./ | + | ./ |
| - | ... 3:45 pm -> 11:45 am basically, 20 hours, NOTE this is longer than fixing it in step 2\\ | + | ...3:45 pm -> 11:45 am basically, 20 hours, NOTE this is longer than upgrade (includes fix) in step 2\\ |
| - | ... but then the server must be down, using the utility it appears it can remain up (verify with xythos)\\ | + | ...but then the server must be down, using the utility it appears it can remain up (verify with xythos)\\ |
| ...internal fix utility results: broken in home 210, broken in data 1,296 \\ | ...internal fix utility results: broken in home 210, broken in data 1,296 \\ | ||
| + | ...upgrade to 7.1.37_sp2 | ||
| ...upgrade to 7.2.88...\\ | ...upgrade to 7.2.88...\\ | ||
| - | Rolled forward to 7.2.88 | + | Jul 29, 2011 4:02:52 PM -- Xythos Database Schema Installer Version |
| - | the installer. | + | Jul 29, 2011 4:35:55 PM -- Successfully upgraded |
| - | ...hotfix 7.2.88.sp2...\\ | + | Jul 29, 2011 5:00:20 PM -- Successfully upgraded the Xythos Document Store: 'Data Document Store - 1:00 \\ |
| - | I upgraded 7.2.88 and then to 7.2.91 (with pauses | + | Jul 29, 2011 5:28:44 PM -- Successfully upgraded the Xythos Document Store: 'Home Document Store - 1:30 \\ |
| - | inbetween), starting at 12:00PM and finishing at 3: | + | Jul 29, 2011 5:46:42 PM -- Workflow data upgrade completed - 1:45 \\ |
| + | Jul 29, 2011 5:48:24 PM -- | ||
| + | Jul 29, 2011 5:51:07 PM -- | ||
| + | Jul 29, 2011 5:51:07 PM -- | ||
| + | Jul 29, 2011 5:51:08 PM -- Exited successfully - 1:50 \\ | ||
| + | ...hotfix 7.2.88.sp2... | ||
| + | ...upgrade 7.2.91 (with pauses)\\ | ||
| + | Jul 29, 2011 6:04:26 PM -- Xythos Database Schema Installer Version 7.2.91.1042 - (cumulative time) \\ | ||
| + | Jul 29, 2011 6:05:11 PM -- Successfully upgraded the Xythos Global Schema - 1:00 \\ | ||
| + | Jul 29, 2011 6:11:51 PM -- Successfully upgraded the Xythos Document Store: 'Data Document Store - 8:00 \\ | ||
| + | Jul 29, 2011 6:51:44 PM -- Successfully upgraded the Xythos Document Store: 'Home Document Store - 45:00 \\ | ||
| + | Jul 29, 2011 7:14:16 PM -- Exited successfully - 1:10 \\ | ||
| + | ...matt states: | ||
| + | ...in between), starting at 12:00PM and finishing at 3: | ||
xythos/upgrade_times_log.txt · Last modified: 2011/08/01 11:46 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
