I'm wondering if anybody could help me understand what process that actually purges the items in the journalarchive table in SQL?
I am talking about the situation where both the "Index commited", and "backup complete" columns are correctly populated with "1", and thereby also the watchfile table has been purged as part of the postprocessing if you have the vaultstore set to remove save sets after backup.
This is stated in technote 316761:
a. These items are removed from the JournalArchive Table and the WatchFile Table once Indexcommited and BackupComplete are both 1.
Currently, I have quite a few items in the journalarchive table that are both indexed and backed up. Whats the logic here?
I've checked the more recent partitions and the few items that are listed there as unsecured is due to regular archiving/backup cycles. I'm curious though - What could make an item to be something else than "truely secured" if it has been both indexed and backed up?