Implementation Plan October 16, 2009
Personnel
- QC is Sandra
- DBA is Prabhu
- Sysadmin Joncarlo
Preparation for Swith Over
- (Prabhu) Copy all the cron jobs from Hammer to Steele.
- (Prabhu) Copy all the scripts from Hammer to Steele and edit the necessary parameters.
- (Prabhu) Verify with sysadmin about firewall rules, processes limits, Kernel parameters, and oracle limits are the same on hammer and steele.
During maintenance window
S = maintenance window + 2 Hrs
- (S - m ProjManmgt/Prabhu) Make sure database marker is set prior to start of the patching.
- (S - m Prabhu) Verify with sysadmin that patching of hammer is completed
- (S - m Prabhu) Make sure all application servers are offline.
- (S + m Prabhu) Backup the full database on hammer.
- (S + m Prabhu) Make sure backup of full database on hammer is complete.
- (S + m Prabhu) Shutdown the standby database on Steele and Primary database on Hammer
- (S + m Prabhu) Inform Backupadmin/Sysadmin to start filesystem backup/snapshot on Hammer and Steele.
- (S + m Prabhu) Make sure filesystem snapshot is complete and Start the standby database on Steele and then Primary database on Hammer.
- (S + m Prabhu) Execute switchover procedure
- (S + m Sysadmin) Restart sakai on head node
- (S + m Prabhu/Sysadmin) Verify the application login
- (S + m Sysadmin) Restart sakai on remaining nodes
- (S + m Sysadmin) Take application servers out of maintenance mode
Fall-back Procedure (If needed) Time D is the decision time made to fallback
- (D + m Sysadmin) Shutdown Sakai on smartsite-prod
- (D + m Prabhu ) Execute Switch back procedure
- (D + m Sysadmin) Restart sakai on head node
- (D + m Prabhu / Sysadmin) Verify the application login
- (D + m Sysadmin) Restart sakai on remaining nodes
- (D + m Sysadmin) Take application servers out of maintenance mode