How to free some disk space on the master and/or relays. |
A- Clean old versions of the packages you have published: This would apply to the master. When a package is published from the packager, this will create a new folder containing this package in the ../master/data/Vision64database/packages/ folder. The package will be stored in a sub folder named by the checksum corresponding to this version of the package. Every time a new version of an existing package is published, this will create a new package in a sub folder named by its corresponding new checksum. Depending on how often a packages is fixed or updated (regularly or not, several times or not) it can quickly take a lot of space over time because the older versions of the package are not deleted automatically. This is because some devices might still be assigned to the older version of the package. These older package versions can be deleted by simply going the "Tools" menu in the upper left corner of the console, then select "Clean-up Old Packages". Warning: devices which were already assigned to the package or an operational rule (OR) containing the package before the package was published again, will still request the older version of the package. Therefore it is needed to reassign all these devices which have not yet executed the package to this package or the Operational Rule which contains it.
B- Clean published packages: This would apply to the master. If Client Management has been in use for quite a long time, there's a high probability for existing published packages are not required anymore. It is recommended to go to the "Packages" node in the console, review the packages there and delete the ones which are not needed anymore. Do not forget to unassign them properly prior to deleting them, as described in the KA 000124835.
C- Clean packages from your package factory: It is possible to send back any published package to any package creator, so there's no need to keep the package in the package factory where it was built it as explained in the KA 000142935. Do not forget to, at least, delete the package from there as well when its published version is deleted from the "Packages" node.
D- Clean packages that have not ben requested for a while: To be applied on relays: The filestore module (which handles file transfers between the master, the relay(s) and the clients) can be set to delete both packages and patches when they haven't been requested by its children for a while. If a child to this relay requests a package after it has been cleaned-up from filestore, the relay will simply request it again from the master, then the client will be able to downloaded from the relay once it will have completed the download from the master. To enable or check that it's already been set to self-clean regularly then go to the relay ..\config\filestore.ini, edit it and check the parameter "PackageTTL=". If it's set to "0" then the packages are never deleted from the ../data/filestore/downstream of the relay. Note that this is also applicable to client devices Set the "PackageTTL=" value higher than "0" (in days) for a package to be deleted from the filestore, then restart the service of the agent right way for the setting to be taken into account. Warning: if there is a poor bandwidth between the master and the relay or between a level 2 relay and its level 1 relay etc, the value to be set should be a high one, in order to avoid situations where the relay(s) will frequently download packages again.
E- Clean patches: To be applied on the master: The size used by the downloaded patches for older versions of the Windows Operating System can be very big over time. As all devices have now been upgraded to newer versions of Windows Operating Systems, the disk space used on the drive by older unneeded patches can be very large. Starting from BCM version 12.6, it is now possible to do this cleanup automatically at start of the service of the BCM agent. Before version 12.6 no built-in method was implemented. See KA 000114912 for details.
F- Clean the old update manager update files: This would apply to the master. When the update manager has downloaded a new update for the security products management and/or for the software catalog, the zip files from the previous downloads will never be deleted. This can take a lot of space after a while. See KA 000120555 for details on how to clean these. G- Clean the OSD projects and the drivers which are not in use anymore: Review your OSD projects, images and driver files. Even the drivers can take a lot of space, when drivers are massively imported without filtering. Images can take a lot of space as well as they can be stored on the OSD Manager itself.
Workarounds: If all of the above has not freed enough disk space : |