Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Personnel

  • QC is Sandra
  • DBA is Prabhu

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.
  • (Prabhu)
  •  

During maintenance window

S = maintenance window + 30 mins

  • (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)  
  •  

Fall-back Procedure (If needed) Time D is the decision time made to fallback

  • (D + 0m Sysadmin) Shutdown Sakai on smartsite-prod
  • (
  • (D + 20m Sysadmin) Restart sakai on head node
  • (D + 25m QC) Verify the database marker is in place
  • (D + 40m Sysadmin) Restart sakai on remaining nodes
  • (D + 25m Sysadmin) Take application servers out of maintenance mode
  • No labels