Reset Search
 

 

Article

KB44638 - AWS upgrades of PCS/PPS takes a very long time compared to Azure/KVM/VMWare/Hyper-V platforms

« Go Back

Information

 
Last Modified Date2/3/2022 9:14 PM
Synopsis

AWS upgrades of PCS/PPS takes a very long time compared to Azure/KVM/VMWare/Hyper-V platforms

This article describes the delay observed in AWS Upgrades of PCS/PPS appliances.
Problem or Goal
AWS Upgrades of PCS/PPS Virtual Appliances take a considerable amount of time to upgrade when compared to other platforms such as Azure/KVM/VMWare/Hyper-V.
Cause
This is seen due to the Disk I/O operations.
Solution
Upgrades from base Deployments that use GP3 EBS Volumes take considerably less amount of time.

Therefore, please deploy base images using GP3 EBS Volumes via AMI templates or deploy Base PCS 9.1R13 or later images from marketplace as we have incorporated GP3 EBS volumes.


Workaround:
  1. Freshly Deploy an AWS Image of the target version.
  2. Export Binary System/User configurations from the current appliance.
  3. Import the exported Binary System/User Configurations on to the Freshly Deployed AWS instance.
  4. Perform some basic/functionality testing.
  5. Shutdown the existing/old PSA-V instance and make a note of the Auth code previously used.
  6. Use the Auth code to generate new licenses and apply them.
  7. Assign the Elastic (Public IP Address) to the new instance.
  8. Decommission the old instance once the new appliance is fully functional.
Note:
  • If the target PCS image is not available, you would need to perform an upgrade the usual way.
  • AWS Marketplace is not qualified for the China Region.
Related Links
Attachment 1 
Created ByRaghu Kumar

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255