05-03-2009 09:17 AM
Solved! Go to Solution.
05-03-2009 04:55 PM
05-03-2009 09:46 AM
05-03-2009 11:11 AM
05-03-2009 11:16 AM
05-03-2009 11:37 AM
05-03-2009 12:09 PM
05-03-2009 01:56 PM
05-03-2009 04:47 PM
05-03-2009 04:55 PM
05-03-2009 05:08 PM
05-03-2009 05:26 PM
The trigger file has been mentioned here a few times but the actual storage technology has not been confirmed. The trigger file is used generally if your storage where the DVS files are housed is a netapp device.
If it is not then we need to forget about the trigger file. What you can do is run the command:-
select * from journalarchive
against each of your vault store databases.
Looking at the result set you will see columns called backupcomplete and indexcommited. If we are just waiting for confirmation of backup then backupcomplete will be at 0 and indexcommited at 1.
If you also run the command select * from watchfile then there should be the same number of items in this table as there are in the journalarchive table with a backupcomplete value of 0.
Here you can see the actual location of the DVS file so you can investigate whether the archive bit has actually been reset. If it has then the next process depends on whether your storage is local or not. If local then the item should be post processed immediately. If not local then it will be done either when the storage service is restarted or every 12 hours by default (This can be changed via a registry key)
05-03-2009 05:45 PM
05-03-2009 05:50 PM
05-03-2009 09:12 PM