Old update files exist on LiveUpdate Administrator (LUA) distribution centers despite successful purge events. No errors or warnings are listed in the logs for the purge.
If the distribution center is not able to purge the files at the time of the scheduled purge for any reason, the files will remain. On versions previous to 2.3.4, the LUA server marks all files as successfully purged if any files are successfully purged.
Common reasons for content files to be left behind after a purge are:
The files are part of more than one Product Version Language (PVL) and are still considered the latest content for one of their associated PVLs.
The files are part of the most recent set of hub deltas for a product using Microdefinitions technology.
The files were being accessed by clients at the time of the purge.
The files were locked by another application at the time of the purge (commonly, this is by a copy tool, backup software, or search indexing).
Recreate the distribution schedule using the settings noted above.
In many cases, "old" files are present by design. Different product have different dependencies which mean that old contents still might be in use, based on how updates are published for those PVLs (Product Version Language ID's). Additional information is available in the Connect Forum article Managing LiveUpdate Administrator 2.x Space Usage.
It is not recommended to manually delete "old" files from a LiveUpdate Administrator 2.x Distribution Center. This may put the product's database out of synchronization. Only after careful examination that files have not been requested for one month by any of the appropriate clients (SEP for Mac clients, when judging SEP for Mac files) would it be safe to delete them. Instructions for how to verify this can be found in the Connect Forum article Using IIS Logs to Check LiveUpdate Administrator 2.x Health.
Imported Document ID: TECH178155
Subscribing will provide email updates when this Article is updated. Login is required.