The general procedure is:
- Open an HPSM change (standard procedure) & notify interested parties, CAB if prod
- Back up system
- Stop app
- Stop DB
- Back up DB
- Back up app
- Perform updates per instructions
- Roll back if q/a fails
- Hand over to app owner for q/a
- Hand over to customer for q/a
- Certify update
Separate environments are logically partitioned and can generally be updated independently. Updates on non-prod which require a reboot imply outage to co-located non-production instances. Since all environments include co-located code & db, outages to one requiring reboots imply outage to the other. DB outages imply outages to respective middle tier in that environment
Labels
(None)