As our vault size grows, and our backups take longer and longer, we have decided to give purge a try. So far it’s not going that well. The problem can be replicated by creating a purge collection rule, as follows
- Single product (all the data is isolated in the product)
- All folders
- All object types
- No restriction on versions to keep
When we run a purge job using this rule, some items are purged. Yes, we use baselines and promotions so I’m not expecting just the latest to remain, but I’m really surprised by how much stuff remains. In many cases no version of objects are purged at all. I find it strange for such a purge to results in <10% data removal. So strange that we ran another purge job using the same collection rule (i.e. on the same product data that had already been purged). Additional items were purged, which were not removed on the previous job. We can repeat this process many times, and on each subsequent job more items are purged, albeit a reducing number each time.
Surely all the items that are available to purge (not part of baselines) should get purged on the first attempt. I would not expect any subsequent purge jobs using the same collection to find any additional items to delete? I know you cannot delete a part or CAD doc with build rules in isolation, but if you hit the affected part and CAD Doc at the same time then it’s OK.
Can anybody comment on this?