...
Pre Implementation tasks:
On Friday, August 13, 2010:
â—� Sandra and Fernando will set database markers.
â—� Anand Mehta will:
â—‹ Copy the existing Tomcat to tomcat-264 on all seven app servers
â—‹ Delete all CLE files from tomcat-264
â—‹ Build and deploy the 2.6.4 code to tomcat-264
â—‹ Make a copy of all properties file in the sakai directory and update the copies to 2.6.4 level
â—� Anand Mehta to set the Sakai properties:
UCD Deployment Notes |
1. Commands to remove old CLE files from Tomcat (executed from /home/ucdavis/cle/tomcat)
...
b. set html.tags.welcome=a, abbr, acronym, address, b, big, blockquote, br, center, cite, code, dd, del, dir, div, dl, dt, em, font, hr, h1, h2, h3, h4, h5, h6, I, ins,kbd, li, marquee, menu, nobr, noembed, ol, p, pre, q, rt, ruby, rbc, rb, rtc, rp,s, samp, small, span, strike, strong, sub, sup, tt, u, ul, var, xmp, img, embed,object, table, tr, td, th, tbody, caption, thead, tfoot, colgroup, col|
Saturday, August 14, 2010 during maintenance window: 5:00 am to 10:30am
1. (5:00 am to 5:10 am) Anand Mehta will place smartsite in maintenance mode and stop all Tomcats.
2. (5:11 am to 5:25 am) Anand Mehta will rename tomcat to tomcat-263 and tomcat-264 to tomcat on all app servers
3. (5:26 am to 5:40 am) Anand Mehta will backup the 2.6.3 properties files and put the 2.6.4 properties files in the sakai directory
4. (5:40am to 6:10 am) Mark Pankow will backup the existing DB.
1. No cron jobs will be disabled or altered. ** Mark will link to actual text document.
2. I will let the normally scheduled hot backup run at 4AM. It will not include a datapump (export) which is part of my "normal" daily backup.
3. At 5:40 I will manually export the SAKAI schema. It should not alter the timeline, but I will be running a test at some point this weekend to verify.
4. After the export, I will manually switch the logfile in production and make note of that.
5. I will then defer log transfer to the standby.
5. (6:10 am to 6:20) Mark Pankow will execute the upgrade scripts 2.6.2 to 2.6.3 and 2.6.3 to 2.6.4 CLE upgrade scripts as follows:
ADD: Talk to Anand: No commits; add commits or have DBA issue commits.
...
Post release actions:
1. GRBK-646: Check production DB if we have duplicate (same realm_id) entries in the GB_USER_DEREF_RM_UPDATE_T
a. select realm_id, count() 
as NUM_DUPS from GB_USER_DEREF_RM_UPDATE_T group by REALM_ID having count() > 1;
Rollback:
â—� Anand Mehta rolls back the upgrade by doing the following:
1. (8:00 am to 8:15 am) Anand Mehta stops any running Tomcats.
2. (8:15 am to 8:25 am) Anand Mehta renames tomcat to tomcat-264 and tomcat-263 to tomcat on all app servers.
3. (8:25 am to 8:40 am) Anand Mehta backs up the existing properties files and puts the 2.6.2 properties files in the sakai directory.
4. (8:40 am to 9:40 am) Mark Pankow
1. I would import the SAKAI schema from the export taken manually. That should not take more than the 40 minutes alloted.
2. Additionally, measures above would allow for a restore and recovery to the point right before the upgrade using the 4AM hot backup.
3. Lastly, the standby base is there and ready to be converted to the primary in the event of catastrophic failure.
4. ADD: log transfer; reconnect primary database to hot standby
5. ADD: Any syntax, commands, sql scripts for these steps above
...