Merging the SystemPerforming the Upgrade 4-17Related Topics• “Verifying the Upgrade Side Before Committing the Upgrade”• “Committing the Upgrade” on page 4-18• “Viewing Active Upgrade Process Status” on page 4-21• “Aborting the Upgrade” on page 4-19• TroubleshootingVerifying the Upgrade Side Before Committing the UpgradeAfter you have merged the system, your critical applications (including the ActiveUpgrade console) are running from the software on the Upgrade Side system disks. Atthis point, you can test the software you installed and verify the general health of thesystem with full access to the system’s resources, including:• Network resources• External storage• Application data disksFor example, you might want to perform the following tasks before you commit theupgrade:• Verify that all of your critical applications have restarted on the Upgrade Side (see“Verifying the Status of Application Services” on page 5-2).• Verify that you have access to your network and application data disks.• Verify that client systems can reach all of the services that your system provides.• Verify the presence and version number of each software package (see “Verifyingthe Status of Installed Software” on page 5-3).• Verify that you can start and run any applications that you have installed orupgraded (if they are not already running).• Check the configuration settings for your applications and the operating system,which could have been altered by software installation.If you are satisfied that everything is working correctly, you can commit the upgrade tomake the changes permanent.If there are any problems, you can abort the upgrade to return the system to its originalstate. However, aborting the upgrade while the system is in merge mode incursdowntime, because the Active Upgrade console must stop your critical applications onthe Upgrade Side before it can restart them on the Production Side.Related Topics• “Committing the Upgrade”
