HRMS Disaster Recovery Procedure

PeopleTools Application Administration

The following disaster recovery procedure is intended to be performed by a knowledgeable PeopleTools Applications Administrator. For more information involving these steps, refer to the AppAdmin Tips&Techniques document index located at \\corpproj\data$\PsAdmin\HTML\tipsindx.html.

Recovery Procedure

  1. Shutdown all development databases and their related services on the development database server
  2. Ensure the current production software silo is distributed from psadm@boss to the development database server
  3. Update the configuration.properties file for all production channels of the production webserver domain on nalia so that the psserver parameter points to the development database server
  4. Re-distribute the production software silo from nalia to the production webserver host in Physics
  5. Update the SLB router so that only the production webserver host in Physics is OPERATIONAL
  6. Establish the required psconfig definition files for the database under /apps/psadm/version/{SID} on the development database server
  7. Generate the production application server and process scheduler domains on the development database server
  8. Ensure the /apps/psadm/data/reports directory on the production webserver host in Physics has group ownership of pswls and group permissions of rws
  9. Ensure that user psadm on the development database server is able to ssh to all production ssh targets for interface purposes; this may require having psadm's public key copied to the appropriate servers. See the HRMS project for the list of internal and external targets
  10. Ensure the development database server is able to print to all production printers
  11. Ensure the firewall for the development database server will allow all appropriate remote production database hosts to connect via database link

Once the restored production database is available

  1. Restart the production webserver domain on the production webserver host in Physics so that the configuration change takes effect
  2. Start the production application server domains on the development database server
  3. Sign-in to PIA, add a new process scheduler Report Node for the restored production database and production webserver host in Physics
  4. In PIA, update the process scheduler Server Definition to associate the new report node
  5. Start the production process scheduler domain on the development database server
  6. Run a test process to ensure the process scheduler is functioning appropriately and report distribution is successful

Current Environment

At the time of this writing, the following values are in use:

Parameter Value
development database server dawn
production webserver host in Physics wally2
production software silo hcm11
production webserver domain hcm-prod


-- KevinOberle - 4 Dec 2008

Edit | Attach | Print version | History: r7 | r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r3 - 04 Dec 2008 - 18:56:57 - KevinOberle
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback