![](/images/new-backgrounds/1103032/103032169x1.webp)
Merging the System
Verifying the Upgrade Side Before Merging the System
After you have upgraded or installed software on the Upgrade Side, you can perform limited testing on the Upgrade Side system disks, as long as your activities do not require access to the following resources, which are currently unavailable:
•Network
•Internal data disks
•Application data disks
For example, you might want to perform the following tasks before you merge the system:
•Verify the presence and version number of each software package (see “Verifying the Status of Installed Software” on page
•If possible, verify that you can start the applications you installed or upgraded.
•If possible, configure the settings for any applications you installed or upgraded.
If you are satisfied that everything is working correctly, you can merge the system to stop your applications on the Production Side and restart them on the Upgrade Side for final verification.
If there are any problems, you can abort the upgrade to return the system to its original state. Aborting the upgrade while the system is in split mode does not incur downtime, because your critical applications are still running on the Production Side.
Related Topics
•“Managing Upgrade Tasks on the Upgrade Side” on page
•“Viewing Active Upgrade Process Status” on page
•“Merging the System” on page
•“Aborting the Upgrade” on page
•Troubleshooting
Merging the System
After you are finished performing upgrade tasks on the Upgrade Side of the system, you can merge the system to verify your changes before you permanently commit them.
Performing the Upgrade