La Crosse Upgrade Details 2010
This year's upgrade process will be in 6 parts.
1. Setup the read-only mode copy of La Crosse's Voyager (outage early in the morning)
2. Patch Oracle to 10.0.2.4 and apply CPU
3. Upgrade Voyager to 7.2.0
4. Apply Voyager Service Pack to get to 7.2.1
5. Do all split server configuration work
6. La Crosse library tests and customizes as needed, then switch back production (short outage).
Read Only Mode (completed noon - starting at 3am)
- Comment out cron jobs (completed)
- Take down production (completed)
- Configure UPG zones on widener (completed)
- Copy zones from production to UPG zones on widener (in progress)
- Copy backups to UPG zones (completed 4:45am)
- Bring up UPG zones as production (completed)
- Verify all is well (completed)
- Set Voyager read-only mode (completed)
- set Oracle tablespace to read-only (completed)
- Modify production zones to use UPG ip addresses and check firewall rules (completed)
- Oracle listener configuration (completed)
-- /oracle/app/oracle/product/10.2.0/db_1/network/admin/listener.ora backup and change (completed)
- /etc/inet/hosts files in each zone (completed)
- Make a backup copy of production web zone /m1/voyager/xxxdb to be referred to for customizations later (completed)
bw - taking a break at 5am - read-only instance is up and running, will bring up other zones and start upgrading later this morning.
bw - absolutely insane day - it's Wed 10:15pm, I'm getting this going finally.
Patch Oracle to 10.0.2.4 and apply CPU (completed 12:15am)
- Copy oracle patch files to /m1/incoming/oracle (completed)
- Uncompress (completed)
- Pre-installation steps (completed)
- Install 10.2.0.4 update (completed - 11:05-11:15pm)
- Run upgrade script and recompile script (completed 12:15am)
- Install Oracle CPU (not doing at this time)
Install Voyager 7.2.0 upgrade (completed Thursday 8:25am)
- Copy the voyager upgrade files to /m1/incoming/v720 (completed)
- Run 7.2.0 upgrade (completed)
- Prep -
- install new jdk from SHARED tarball in both web and db zones (completed)
- verify /m1/voyager/xxxdb/ini/voyager.env has JAVA_HOME set correctly (completed)
- move /m1/shared/apache2 to /m1/shared/httpd/2.2.6 and make a symlink from /m1/shared/httpd/2.2.6 to /m1/shared/apache2 (completed)
- change /m1/voyager/xxxdb mountpoint so it's not a mountpoint for the upgrade.pl run (completed)
- Files upgrade.pl (completed)
- Verify /m1/voyager/xxxdb/tomcat/vxws/conf/server.xml entries -
-- <Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="128.104.22.*"/> (completed)
-- url="jdbc:oracle:thin:@HOSTNAME:PORT:VGER" (completed)
- RE-verify /m1/voyager/xxxdb/ini/voyager.env has JAVA_HOME set correctly (completed)
- Oracle schema update (completed Thurday 1:27am)
- (Run regen) - not this year
- Post setup steps (pick up here in the morning)
-- UB (completed)
-- Media scheduler (completed)
-- Authorities Keyword stuff (completed 8am)
-- Run through full Authority Headings piece, including ctxsys recreation and running ./create_single_index.ksh $USERPASS (test and will do if needed)
-- recreate readonly user (completed)
- Service re-setup - make sure the /m1/voyager/xxxdb directories are only the valid ones or the voyager service setup will do funny things with the extras (completed)
Install Voyager 7.2.1 service pack (completed 10:35am)
- Install service pack on DB server (completed)
- shut down zones and change /m1/voyager/xxxdb mountpoint so it is a mountpoint again and rsync the new xxxdb directory over to it (completed)
Post Service pack server splits (completed 11:50am)
- Split web server - don't use maketomcatwebserver.ksh method (completed)
-- verify upgraded java jdk to 1.6 version(completed)
-- cleaned up older bin/lib/utility/sbin directories(completed)
-- built tarball with -(completed)
--- sudo tar cvf webserver.tar lacrossdb/etc lacrossdb/webvoyage lacrossdb/ini lacrossdb/tomcat/vwebv lib/2007.2.1 bin/2007.2.1/*exe bin/2007.2.1/*cgi(completed)
-- sudo vi *db/etc/webvoyage/voyager.ini(completed)
-- under xxxdb/tomcat/vwebv find the WEB-INF/web.xml and verify XServiceHost is pointing to the right place(completed)
-- start things up(completed)
-- went slower than it needed to because I thought it was going to be harder(completed)
- Split z3950 server(completed)
-- with prod switch over, will need to modify for prod IPs and stop/start voyager on z3950(completed)
--- Build with their tar command - leave out voyager and oracle libraries - scp them over afterwards(completed)
--- as voyager ; cd /m1/voyager/lib/2007.2.1 (already done with first instance setup - Stout)(completed)
--- scp user@xxxdbupg.wisconsin.edu:/oracle/app/oracle/product/10.2.0/db_1/lib32/libnnz10.so .(completed)
--- scp user@xxxdbupg.wisconsin.edu:/oracle/app/oracle/product/10.2.0/db_1/lib32/libclntsh.so.10.1(completed)
--- scp user@xxxdbupg.wisconsin.edu:/oracle/app/oracle/product/10.2.0/db_1/lib32/libclntsh.so.9.0 .(completed)
--- modify /m1/voyager/stoutdb/etc/ascopac/opac.ini from localhost to xxxdbupg(completed)
--- /m1/voyager/stoutdb/ini/z3950svr.ini from localhost to xxxdbupg(completed)
- Split staff client server (not for La Crosse, at least this year)
-- build zone/create users/groups/home directories, etc.
Customize upgraded Webvoyage and test staff clients
- Use the laclibupg.wisconsin.edu address for customizations
- Copy of pre-upgrade stoutdb directory should be /m1/v710-lacross
- Point upgraded staff client at lacvoydbupg.wisconsin.edu address for testing upgraded
- Fix newbooks
Switch over
- Take down read-only production zones
- Reboot upgraded zones to come back up as production
-- take down read-only production zones (outage starts here)
-- for upgraded zones -
-- zone configuration files back into place
-- /etc/inet/hosts in each zone back to production values
-- /oracle/app/oracle/product/10.2.0/db_1/network/admin/listener.ora backup into place
-- apache configuration changes if anything has an IP address hard coded
-- shut down zones
-- boot zones (should come up as production)
-- uncomment cron jobs for voyager and nightly backups
-- update nightly backup scripts as needed
-- on z3950 update z3950svr.ini and xxxdb/etc/ascopac/opac.ini and stop/start voyager (z3950.wisconsin.edu brief downtime at this point)
- Do any cleanup needed
)
There are no threads for this page.
Be the first to start a new thread.