Overview of the Active Upgrade Process
Active Upgrade State Model
The state model in Figure
Figure 1-6. Active Upgrade State Model
|
|
| Check |
Finish |
| Idle | Readiness |
Finish |
|
| |
|
|
| |
Commit |
|
| Idle |
|
|
| |
| Finish |
| Prepare |
Commit |
|
| Split |
|
|
| |
Abort | Abort | Abort |
|
| Prepare | ||
|
| ||
Merge |
|
| |
|
| Split |
Abort Abort
Execute
Merge
Execute
Split
Prepare | Split |
Merge | |
Split Mode | Prepare |
Merge |
duet005a
The state model helps to demonstrate the sequence of events in the Active Upgrade process, as follows:
1.All upgrade sessions start in the Idle state, where you can run the readiness check as many times as necessary to verify that your system meets the prerequisites of the upgrade process. The system continues to run normally, and both sides of the system continue to be synchronized.
2.When you start an upgrade session, the Active Upgrade console switches to the PrepareSplit state, during which it runs a final readiness check and additional background tasks. If the system is ready, the console immediately switches to the Split state and proceeds to divide the system into two independently running systems.