Hi Steve,
Thanks for the post.
This is very much available in our road-map and in future you will be able to apply the patches without having to stop the services. We are also planning to support direct upgrade of the secondary server as well. But at present this is not possible and as a workaround you can use the below steps to reduce the downtime to few minutes.
- If you are using a VM, you can clone the VM and perform the upgrade in the Clone server. Then replace the PMP directory in the production server. In this case, you will only have to stop the service for renaming the working PMP directory and to paste the upgraded directory from the clone server.
- If you are not using a VM, you can still stop the PMP service, take a copy of entire PMP directory and move it to another server. Then you can start the PMP service while you perform the upgrade in the other server.
But our recommendation for using the RestAPI feature is to embed both Primary and Secondary URL's in the target systems. This way, all the automatic password retrieval would continue to work using the secondary server while you upgrade the primary.
Hope this helps you. Do contact us if you have any other questions.
Thanks & Regards,
Ganesh
[Technical Consultant | Password Manager Pro]
