Vault items "Awaiting Backup" not cleairing
HI, in the passed I open the https://www.veritas.com/community/forums/vault-items-awaiting-backup-not-cleairing-down-below-3414, 1 year later the value is up to 4497.
AndrewB said that "the key is the "unsecured SIS parts in other partitions" so you'll have to look at your other partitions to find which one is the true culprit." I check other post and found out that I should be using EVSVR.EXE command to find the error, after reading the manual I understand how does the tools work but I don't know what options I should use to figure out my issue?
can someone help me?
I'm going to recieve more volume to add to EV server but has I don't have more driveletter I'm going to convert to mountpoint, in the aritcle http://www.veritas.com/docs/000028294 one point is to "Confirm all archived items have been backed up (SQL Server)", I really need to correct this error, We still use Microsoft DPM to backup all drivers.
Following the notes we did get from Veritas in an older case:
1) Run the query
use <VaultStoreDB>
select * from watchfile where itemsecured = 1
2) Copy the IDTransaction value for the first entry into the clipboard (should be ArchiveTransactionID now)
3) Run the query
use <VaultStoreDB>
select savesetidentity from saveset where idtransaction = '[idtransaction from step 2]'
4) Copy the SavesetIdentity value into the clipboard
5) Run the query
use <VaultStoreDB>
select * from view_savesetsisparts
where savesetidentity = '[savesetidentity from step 3]'
6) Make a note of the FPDistinctionByte value and copy the ParentTransactionID value into the clipboard. The FPDistinctionByte value will correspond with the member table number in the query below.
7) Run the query
use <FingerprintDB>
select * from MemberTable_[FPDistinctionByte] where ParentTransactionID = '[ParentTransactionID from Step 5]'
8) Confirm that the record returned has a Secured value of 0
9) Run the query
Select * from saveset where idtransaction = '[parenttransactionid from step 5]'
You will have to run this query against all Vault Stores until you find the item as it could be in any of the Vault Stores under that particular vault store group. Once you have found it make a note of the archived date of the item.
10) Open the partition for the Vault Store in which this item exists and confirm that files for this item exist. The folder structure is:
Year\Month-Day\First Character of the Transaction ID\Following 3 characters of the transaction ID
11) If the item exists and that partition has definitely been backed up, run the query below to set the associated SISpart to secured
use <FingerprintDB>
update MemberTable_[FPDistinctionByte]
set Secured = 1
where parenttransactionID = '[parenttransactionid from step 5]'
12) Rename the ignorearchivebittrigger.old file to ignorearchivetriggerbit.txt on the partition location for the VaultStoreMBX2 Vault Store.
13) Put the specific vaultstore into backup mode and then take it out again. This will trigger EV into checking if the items are secure or not.
14) Re-run the query from Step 1. The number of items should have reduced. Pick the top record again and run through the steps again. Repeat until the query from step 1 returns no records.Used this successfully for EV 10.0.4 CHF3.
Please note that changing the secured flag for 1 item may cause a massiv decrease of your count as many items may be referenced to just a few unsecured ones. This was the case in my situation.
