Due to the fact that these steps require direct manipulation of the SQL tables, Veritas requires the EnterpriseVaultDirectory database to be backed up, before proceeding.

NOTE: These steps are not to be shared with the customer without express consent from Backline. The case must include a comment that indicates who on Backline approved the use of these steps

1. Stop the Enterprise Vault Services
2. Take a backup of the Vault Store database
3. Run the following Query against the Vault Store database:
   
   UPDATE ArchiveUsageSummary
   SET OriginalSize = GV.OriginalSize, ArchivedItemSize = GV.ArchivedItemsSize, TotalArchivedItems = GV.ArchivedItems, TotalItemsWithoutOriginalSize = '0'
   FROM ArchiveUsageSummary AUS INNER JOIN
   (SELECT vlv.ArchivePointIdentity, ArchivedItems, ArchivedItemsSize,
               OriginalSize = CASE WHEN SUM(OriginalSize) is null THEN 0 ELSE SUM(OriginalSize) END
   FROM view_ListVaults vlv LEFT OUTER JOIN
         view_SaveSet ss ON vlv.ArchivePointIdentity = ss.ArchivePointIdentity LEFT OUTER JOIN
         view_SaveSet_Properties ssp ON ss.SavesetIdentity = ssp.SavesetIdentity
   GROUP BY ArchivedItems, ArchivedItemsSize, vlv.ArchivePointIdentity) AS GV ON GV.ArchivePointIdentity = AUS.ArchivePointIdentity
    
4. Once the above Query completes, run this second query against the same Vault Store database:
   
   UPDATE ArchiveUsageSummary
   SET TotalItemsWithoutOriginalSize = WO.TotalItemsWithoutOriginalSize
   FROM ArchiveUsageSummary AUS INNER JOIN
   (SELECT ssp.ArchivePointIdentity, COUNT(IdTransaction) AS TotalItemsWithoutOriginalSize
   FROM view_Saveset_Properties ssp
   WHERE ssp.OriginalSize = 0 OR ssp.OriginalSize IS NULL
   GROUP BY ssp.ArchivePointIdentity) AS WO ON WO.ArchivePointIdentity = AUS.ArchivePointIdentity
    
5. Once this second Query completes, Start the Enterprise Vault Services
6. Test the Enterprise Vault Reporting

In some rare circumstances the values contained in the ​ArchiveUsageSummary table of the Vault Store database could be incorrect due to how the table was updated when items were deleted prior to being properly archived.  The table ​ArchiveUsageSummary is an aggregate table that is used in the two Enterprise Vault Reports.  To confirm that this is the issue being experienced, run the following SQL query against the Vault Store database:

SELECT *
FROM ArchiveUsageSummary
WHERE TotalArchivedItems < 0

The root cause of this issue has been fixed in Enterprise Vault 11.0.0 and above.  After upgrading the values in the table ​ArchiveUsageSummary will no longer be decremented improperly.  However the current values will need to be updated to ensure they properly reflect accurate values, if this issue is found to be occurring please open a case contacting Enterprise Vault Support.

In some rare circumstances the values contained in the ​ArchiveUsageSummary table of the Vault Store database could be incorrect due to how the table was updated when items were deleted prior to being properly archived. The table ​ArchiveUsageSummary is an aggregate table that is used in the two Enterprise Vault Reports. To confirm that this is the issue being experienced, run the following SQL query against the Vault Store database: SELECT *
FROM ArchiveUsageSummary
WHERE TotalArchivedItems < 0