Upgrade Related

The UDP Console password migration tool failed to execute.
Symptom
If you have updated Arcserve UDP to version 9.2 and are using a console database on a remote machine with different passwords for the console and the remote machine, the console password migration tool fails and logs the following message:
Identified password migration failure for Arcserve UDP Console!
Solution
No action required. For more information, see the log.

In the All Plans view, select the plan, go to Actions, and then click Deploy Now.
If the above step fails, then do the following:

In the All Plans view, select the plan, go to Actions, click Modify, and then click Save.
From the Nodes view, go to Action, click Update, and then click Save.
Note: Applying the above steps helps to automatically deploy the plan correctly once more.

Make sure to perform a timely upgrade of all RPS and Proxy involved in more complex plans.
We recommend that you carefully review any other warning that the UDP Console might display as part of the plan deployment.

Incorrect warning messages appear even when hosts are upgraded to UDP 9.2.
Symptom
Even when the hosts are successfully upgraded to UDP 9.2, the following warning message appears:
Some hosts have not upgraded to UDP 9.2 and are vulnerable. Please upgrade them as soon as possible.
Solution
Please wait for 24 hours as the warning messages usually disappear within the timeframe.

Although the older version of httpd binary located in the following path is carried with UDP 9.2, this binary is not executed from the UDP 9.2 Console. This older version of httpd binary is carried from UDP 9.0 only for the remote deployment purpose.
C:\Program Files\Arcserve\Unified Data Protection\Management\Deployment\D2D\3rdComponents\Apache\x86\bin\

The upgrade is successful with a warning on the Password Migration tool.
Symptom
The software update was installed successfully with the following warning.
Warning: The Password Migration tool did not run successfully for the UDP 9.2 update.
Solution
Notes:

The Registry Editor fails to reflect the correctly updated binary of Apache.
Symptom
In the Registry Editor, the Version folder located in the following path fails to reflect the correctly updated binary of Apache.
HKEY_LOCAL_MACHINE\Software\Arcserve\Unified Data Protection\Common\Apache\Version
Solution
To review the currently installed Apache version, check the CHANGES file located in the following path:
C:\Program Files\Arcserve\Unified Data Protection\Common\Apache

The Registry Editor fails to reflect the correctly updated binary of JRE.
Symptom
In the Registry Editor, the Version folder located in the following path fails to reflect the correctly updated binary of JRE.
HKEY_LOCAL_MACHINE\Software\Arcserve\Unified Data Protection\Common\JRE\Version
Solution
To review the currently installed JRE version, check the version file located in the following path:
C:\Program Files\Arcserve\Unified Data Protection\Common\JRE

The Registry Editor fails to reflect the correctly updated binary of Tomcat.
Symptom
In the Registry Editor, the Version folder located in the following path fails to reflect the correctly updated binary of Tomcat.
HKEY_LOCAL_MACHINE\Software\Arcserve\Unified Data Protection\Common\Tomcat\Version
Solution
To review the currently installed Tomcat version, check the RELEASE-NOTES file located in the following path:
C:\Program Files\Arcserve\Unified Data Protection\Common\Tomcat

During the installation or upgrade of Arcserve UDP components, the .Net 4.7.2 version gets deployed automatically. However, in some cases, the system may require a reboot for the .Net changes to take effect.

The database does not get upgraded to SQL 2014 SP3 without an active Internet connection.
Symptom
When you upgrade from UDP 8.0 to UDP 8.1 without an active Internet connection, the UDP still continues with the default SQL E 2014 SP2 database.
Solution
As a workaround, manually upgrade the database to SQL E 2014 SP3.

Old Hypervisor details are not displayed after upgrading to Arcserve UDP 7.0 Update 2.
Symptom
After upgrading to Arcserve UDP 7.0 Update 2 from Arcserve UDP 6.5 Update 3 or previous supported versions, the Hypervisor information in Arcserve UDP 6.5 Update 3 or previous supported versions is lost.
Note: The issue does not appear when upgrading from Arcserve UDP v6.5 Update 4 to 7.0 Update 2.
Solution

Enter the Hypervisor information again after the upgrade.

Upgrade to Arcserve Appliance version 7.0 with Arcserve UDP 7.0 installation iso pops an error dialog ApplianceInformation.exe has stopped working.
Symptom
When upgrading to Arcserve Appliance version 7.0 with Arcserve UDP 7.0 installation iso, the upgrade application of UDP calls the ApplianceInformation.exe during upgrade process and creates an log file in the saved folder, while the DVD drive is read-only, an error dialog about ApplianceInformation.exe appears.
This issue does not block and effect the upgrade process , the upgrade application of Arcserve UDP 7.0 continues until finished.
Upgrade with downloaded Arcserve UDP 7.0 executable installation file, Arcserve_Unified_Data_Protection.exe is done without any issues.
Solution
Close the error dialog.