EVSVR repair procedures

Article:HOWTO57347  |  Created: 2011-08-01  |  Updated: 2013-07-12  |  Article URL http://www.symantec.com/docs/HOWTO57347
Article Type
How To


Subject


EVSVR repair procedures

Caution:

If you perform any of the following procedures, do not take your Enterprise Vault system out of backup mode until you have verified that the procedure has resolved the issue. Otherwise, you may damage your system.

Procedure 1

  1. Using the information in the Verify log file to guide you, try to recover each missing file and corrupt file.

  2. Rerun the Verify operation that you previously ran until you have resolved all the errors.

  3. If you cannot recover all the SIS parts, run the BlacklistBadSISParts Repair operation to blacklist the fingerprint database records for the missing files.

    Note:

    This is unnecessary if you have previously run an ArchiveObjects Verify operation with a verification level of SavesetValid. This operation has already blacklisted the database records for the missing SIS parts.

Procedure 2

  1. Place the vault store groups that you want to repair in backup mode.

    If none of the Enterprise Vault services is running then, to place a vault store group in backup mode, you must start the Admin and Directory services only. Do not start the Storage service.

  2. On each Enterprise Vault server, stop all Enterprise Vault services and related processes. Take care to ensure that storage-related processes such as StorageServer.exe and StorageFileWatch.exe have stopped.

  3. Restart the following Enterprise Vault services only:

    • Enterprise Vault Admin service.

    • Enterprise Vault Directory service.

    • Enterprise Vault Indexing service (and all Indexing services that are associated with the vault store groups that you want to repair).

    • Storage service (only if needed). If you need to start this service, the "initial database and partition checks" section of the EVSVR log file reports the fact.

  4. Run a DatabaseReferences Repair operation.

    Caution:

    SIS parts can be shared between different partitions in a single vault store and between partitions in different vault stores. Depending on how you have configured sharing, it is possible that the recreation of savesets in one vault store partition is dependent on SIS parts that belong to a partition of another vault store. These SIS part records must be available before you can recreate the savesets. So, the situation can arise where EVSVR cannot recreate some saveset records in a vault store database because they are dependent on SIS part records that you have yet to recreate in the fingerprint database.

    To avoid this issue, use the sharing level that you have set for the vault store groups as a guide to what to repair. When the sharing level is "Share within group", you must repair the entire vault store group instead of repairing the vault stores and partitions one at a time. When the sharing level is "Share within vault store", you must repair the entire vault store instead of repairing the partitions one at a time. When the sharing level is "No sharing", or the partitions contain pre-8.0 savesets only, you can repair the partitions individually.

    An additional consideration is the database that you need to repair. When this database is the vault store database, all the partitions belonging to that vault store are affected and require repair. However, if you need to repair a fingerprint database then, regardless of the sharing level that you have chosen, the entire vault store group is affected and requires repair

    If any of the following conditions applies, you may want to uncheck the EVSVR operation setting Require Index Entries:

    • You use deferred indexing (FSA).

    • You have a backlog of index operations outstanding on any archives.

    • An index rebuild is running.

    The Require Index Entries operation setting controls whether EVSVR repairs database records based on the existence of index entries for the items.

  5. If the DatabaseReferences Repair operation reports that it cannot recreate saveset records because of missing information in the Directory database, and the archive type is Exchange Mailbox or File System, perform an Archives Repair operation. This operation may be able to recreate the missing saveset records by obtaining the required information from the target Exchange system or file system volume.

  6. Run a Complete Verify operation with EVSVR and investigate any errors.

    Depending on the nature of the errors, you may want to contact Enterprise Vault Support before you proceed.

  7. Consider removing some or all records from the WatchFile and WatchSISPartFile tables of the relevant vault store database.

    Whether you remove the records depends on how old the restored copy of the vault store database is and whether you have enabled collections or migrations. If some records in the restored WatchFile table have subsequently been collected, we recommend that you remove the WatchFile and WatchSISPartFile records. For more information, contact Enterprise Vault Support.

  8. Cancel all archive pending items in mailboxes and revert them to their normal state.

  9. When the databases are in an acceptable state, start the remaining Enterprise Vault services and take the system out of backup mode.

Procedure 3

  1. Place the vault store groups that you want to repair in backup mode.

    If none of the Enterprise Vault services is running then, to place a vault store group in backup mode, you must start the Admin and Directory services only. Do not start the Storage service.

  2. On each Enterprise Vault server, stop all Enterprise Vault services and related processes. Take care to ensure that storage-related processes such as StorageServer.exe and StorageFileWatch.exe have stopped.

  3. Restart the following Enterprise Vault services only:

    • Enterprise Vault Admin service

    • Enterprise Vault Directory service

    • Enterprise Vault Indexing service (and all Indexing services that are associated with the vault store groups that you want to repair).

    • Storage service (only if needed). If you need to start this service, the "initial database and partition checks" section of the EVSVR log file reports the fact.

  4. Run a DatabaseLinkages Repair operation.

  5. Run a Complete Verify operation, and investigate any errors.

    Depending on the nature of the errors, you may want to contact Enterprise Vault Support before you proceed.

  6. If the vault store and fingerprint databases are still not consistent with each other or with the storage data in the affected partitions, run a DatabaseReferences Repair operation.

  7. Cancel all archive pending items in mailboxes and revert them to their normal state.

  8. When the databases are in an acceptable state, start the remaining Enterprise Vault services and take the system out of backup mode.

See About EVSVR

See About Enterprise Vault utilities

See Repair operations in EVSVR

See Risk of data loss when you run certain EVSVR Repair operations

See Viewing the EVSVR output log file


Legacy ID



v26071245_v41328148


Article URL http://www.symantec.com/docs/HOWTO57347


Terms of use for this information are found in Legal Notices