Verify operations in EVSVR
|Article:HOWTO57233|||||Created: 2011-08-01|||||Updated: 2013-01-18|||||Article URL http://www.symantec.com/docs/HOWTO57233|
The EVSVR Verify operations let you check the consistency of the information in your vault store partitions, vault store databases, fingerprint databases, and Directory database.
Table: Option settings for Verify operations lists the available Option settings.
Table: Option settings for Verify operations
Verifies that the vault store database records and fingerprint database records point to savesets and SIS parts in a partition:
You must select the required level of verification for this option.
Performs an ArchivesDirectory Verify operation, followed by an ArchivesVaultStore Verify operation.
Verifies that the vault store database records have corresponding records in the Directory database:
Verifies that the Directory database records have corresponding records in the vault store databases:
Performs a DatabaseLinkages Verify operation, followed by an ArchiveObjects Verify operation.
EVSVR performs the ArchiveObjects Verify operation at the most detailed level (SavesetValid).
Verifies the linkages between the vault store databases and fingerprint databases:
Verifies that the savesets and SIS parts in a partition are referenced by database records:
Note the following:
Verifies that the vault store databases contain CAB file collection records whose collection identities match the file names of the associated CAB files. For example, this operation verifies that, when a collection record has a collection identity of 1234, the name of the associated CAB file is
If you find any instances of mismatches between the collection identities and the CAB file names for certain partitions in a vault store database, run the DatabaseReferences Repair operation for those partitions.
Determines the number of collection records in the vault store databases that do not have specified creation dates. In Enterprise Vault 8.0 and later, all new collection records automatically have a specified creation date. However, this is not the case for collection records that an earlier version of Enterprise Vault has created. When the creation date is missing from any collection record, the DatabaseLinkages Verify operation ignores any date range that you specify and processes all of these collection records.
To assign a creation date to any collection record that does not have one, run the UndatedCollections Repair operation.
See About EVSVR
Article URL http://www.symantec.com/docs/HOWTO57233