• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Maintenance & Cleanup

C

cmturner2

Guest
I was wondering if there is a set of best practices or details on cleanup post upgrade? In my case I'm at 8.6.0 but I started back at 8.2.

Specifically:

Which old paths can be purged (if any)?
e.g. .../psa/PSA_8.4.0/... ??
e.g. .../swsoft/PSA_8.2.0/... ??

And additional areas that should be cleaned up?

Is this documented somewhere I missed?

This isn't critical, not a space shortage or anything, I just like to keep things tidy.
 
You can remove those PSA_* directories. They contain the rpms downloaded by Plesk Updater/autoinstaller. You can even remove them for your current version as they're already installed. The rpms are not automatically removed after installation. It's sometimes handy to have them around when you want to reinstall some Plesk packages, but Plesk Updater/autoinstaller can always download them again.
 
Back
Top