Overview of the Active Upgrade Process
Figure 1-4. Committing the Upgrade
|
|
| Internal Storage |
|
|
| Data |
Console | Duplexed System | (Old System) (Current Data) | |
|
|
| Remirror |
|
|
| with RDR |
|
|
| System |
| Network | External | (Upgraded) (Old Data) |
|
| Storage |
duet004
When the RDR disk resychronization is finished, all critical system resources are running in duplex mode, and the Active Upgrade process is complete. You do not need to restart the system, and, because your application is already running on the upgraded software, there is no additional downtime.
Related Topics
•“Aborting the Active Upgrade Process”
•“Active Upgrade State Model” on page
•“Software Upgrade Support” on page
•“System Prerequisites” on page
Aborting the Active Upgrade Process
Aborting the Active Upgrade process stops the current upgrade session and returns your system to its original state. If necessary, you can abort an upgrade session at any point up until you commit the upgrade.
If you abort the upgrade session while the system is in split mode, no downtime is incurred. Your applications continue to run on the Production Side while the Active Upgrade console restores the system to duplex mode.