This document will explain to you about the following:
The Downloaded Patches view provides the details of the patches that are downloaded, along with their deployment status.
To view the list of the downloaded patches,
You can export the Downloaded Patches details in PDF and CSV file formats..
Administrators can configure a specific limit of space for Patch Repository. When the Patch Repository size exceeds the specified limit, a mail notification will be sent to the administrators if required. This provides them a feasibility to verify that the Patch Repository does not run out of free disk space. If a Patch Repository runs out of free space, then the latest patches cannot be downloaded. However, the space limit specified above is used only for notification purposes. Assume, if you have configured the Repository size as 10 GB, where as the available free space in the same drive is 40 GB, then the patch downloads will not be affected even if the size exceeds the specified limit of 10 GB.
The patch download location on the server can be accessed by clicking on Patch Management tab -> Settings -> Cleanup Settings ->Settings tab. Under Download Settings, the patch repository location path will be given.
In case the existing patch store has limited space available, you can modify the location details using the Change Patch Store Location icon available near the Patch Repository location. You should copy the patches from the previous directory to this new location and restart product server for the changes to take effect. The steps to restart the product server are as follows:
Administrators can configure patch cleanup settings to increase the free disk space on the Patch Repository. There are two significant ways to increase the free disk space, they are explained below:
Using "Cleanup Settings", you can remove superseded Patches. When a new version of a patch has been released, the older version of the patch is no longer required in the network. So these patches can be removed as and when a latest version is supported. You can automate this process of removing the superseded patches by configuring the cleanup policy. This will result in increasing your free disk space, by removing unwanted patches.
Patches once downloaded, are retained in your patch repository. Administrators need to periodically check for the patches which are not missing on any of the computers and which are old enough to be removed. Though it is a time-consuming process, you can remove a lot of unwanted patches and increase your disk space. The process of removing patches which are older than a specific period has been automated now. You can specify a time interval, after which the patches will be removed if it is not missing in any of the managed computers.
You can follow the steps mentioned below to configure Patch Cleanup Policy:
You have successfully configured the patch cleanup policy. Superseded patches and patches that are older than the specified time limit will be removed from the patch repository, which means the available free disk space in the product server will be increased. These changes will also impact the Distribution Server. Distribution server synchronizes the patch details with the product server in such a way, that when a patch is removed from the product server, it will also be removed from the Distribution Server during the subsequent replication interval. So whenever the patch repository is cleaned up, the unwanted patches will also be removed from the Distribution Server.