The adop cycle, phase by phase

Prepare, apply, finalize, cutover, cleanup. What each does, HOW LONG IT TAKES, and WHICH ONE TAKES THE OUTAGE. PREPARE creates the patch edition — a fresh copy synchronised with the running one. It runs while users work, and it is slower than people expect, particularly the first cycle after a long gap. A prepare that fails usually fails on space, because it is duplicating the estate. APPLY puts the patch into the patch edition, and it is the long phase. Hours for a large patch. Users are unaffected throughout — that is the entire point of the model — and it is where Module 4 Lesson 7's workers live, so a failed worker stalls here. FINALIZE does everything that can be prepared in advance of the swap, so the cutover has less to do. It also runs online. CUTOVER IS THE OUTAGE AND IT IS THE ONLY ONE. Services stop,…

In this module: Module 7 · Patching

1. 1Why you are patching at all
2. 2Kinds of patch, and what each touches
3. 3Reading a readme properly
4. 4Online patching: the model
5. 5The adop cycle, phase by phaseFree preview
6. 6When a phase fails
7. 7Abandoning and cleaning up
8. 8Rollback: what is actually reversible
9. 9Patching the database tier
10. 10Testing a patch before production
11. 11The outage plan
12. 12Patching cadence, and falling behind
13. 13What breaks: five patching failures
14. 14Lab briefing · Apply, fail, abandon, apply again