Validating Database Archives
Typically, each Storage Manager (SM) independently performs garbage collection on its archive to purge unneeded artifacts. As a result, it is normal for archive sizes to vary between SMs. The amount of variance depends on the type of workload. Workloads that frequently create and drop tables and indexes can result in large temporary variances between the sizes of SM archives.
In rare scenarios when the SM is restarted, the normal garbage collection process cannot purge all unneeded artifacts in the archive. As a result, if one or more SM archives remain significantly larger than the others, it may be necessary to manually purge artifacts from the archive in order to reclaim disk space in the archive.