JournalArchive table doing a count on where backupcomplete = 0
When the item is set to after backup, it is watched in two locations in the Vault Store Database.
One in the JournalArchive table with a BackupComplete flag set to 1, and one in a table called Watchfile, which contains a full path to the Archived item.
Every item listed in the watchfile table will be scanned upon Storage Service start or every 12 hours.
The StorageFileWatch process will go through each item listed in the WatchFile table and determine whether the item has been backed up or not. It determines this by looking at whether the archive bit exists on the file or not. If the archive bit has been removed, then Enterprise Vault removes that particular entry from the watchfile table, and then in the journalArchive table, it changes the “BackupComplete” column from a 0 to a 1
Every morning (Depending on your monitoring settings) you will get an event notifying you how many items are still awaiting backup, and that is driven from the JournalArchive table doing a count on where backupcomplete = 0
However I have a senario where JournalArchive table doing a count on where backupcomplete = 0 has about 1000 entries amd the watchFile table is empty .... We use EVNearSync for our backup solution to replicate from primary to secondary storage and all folders seems to be in sync ??
We have an EV 10.04 environment
Not sure wht to do here ? or how this happned ?