Veritas NetBackup™ for Enterprise Vault™ Agent Administrator's Guide

Last Published:
Product(s): NetBackup (8.1.1)
  1. Introduction to NetBackup Enterprise Vault
    1.  
      About Enterprise Vault
    2.  
      About the NetBackup Enterprise Vault Agent
    3.  
      About the Enterprise Vault Agent and the backup components
    4.  
      Enterprise Vault agent features
    5.  
      Enterprise Vault agent requirements
  2. About NetBackup Enterprise Vault agent installation requirements
    1.  
      Installation requirements for NetBackup Enterprise Vault agent
    2.  
      Verifying Enterprise Vault agent operating system compatibility
    3.  
      NetBackup server and client software requirements
    4.  
      About Enterprise Vault agent installation requirements in a cluster
    5.  
      Configuring Enterprise Vault Agent to protect Enterprise Vault databases
    6.  
      Adding the Enterprise Vault agent license key
    7. Configuration requirements for upgrading the Enterprise Vault agent
      1.  
        Configuring the policy directives after upgrading NetBackup and Enterprise Vault
  3. Configuration
    1.  
      About the Windows and Java user interfaces
    2.  
      Specifying a logon account for the Enterprise Vault server
    3.  
      About VSS-based snapshot configuration
    4.  
      Configuring the local media server for Enterprise Vault backup
    5.  
      Configuration requirements for an Enterprise Vault backup policy
    6.  
      Adding a new Enterprise Vault policy
    7.  
      Enterprise Vault backup policy attributes
    8.  
      Adding schedules to an Enterprise Vault policy
    9.  
      About the types of Enterprise Vault backups
    10.  
      Creating a backup selections list
    11.  
      Adding a client to a policy
  4. About features provided by Enterprise Vault for a backup provider
    1.  
      About Enterprise Vault quiescence before a backup
    2.  
      About quiescing and unquiescing Enterprise Vault services
    3.  
      About granular quiescence
    4.  
      About managing safety copies and backups
    5.  
      About the partition secure notification file
    6.  
      About the archive bit
  5. Performing backups of Enterprise Vault
    1.  
      About Enterprise Vault directives and what data they back up
    2.  
      Manually backing up Enterprise Vault resources
    3.  
      Canceling an Enterprise Vault backup job from the Activity Monitor
  6. Performing restores of Enterprise Vault
    1.  
      Important notes about Enterprise Vault data restore
    2.  
      Stopping the administrative services on Enterprise Vault servers
    3.  
      About the Backup, Archive, and Restore interface
    4.  
      Viewing backup data using the Microsoft SQL Server Management Studio
    5.  
      Restoring Enterprise Vault data
    6.  
      About the Enterprise Vault restore options on the General tab
    7.  
      About the Enterprise Vault Database Settings tab
    8.  
      Specifying the server, clients, and policy type for restores
    9.  
      About restoring Enterprise Vault file system data
    10.  
      Restoring an Enterprise Vault file system component
    11. About restoring Enterprise Vault SQL databases
      1.  
        About backup image restore sets
    12.  
      Restoring Enterprise Vault SQL database components
  7. Disaster recovery
    1.  
      Disaster recovery requirements for Enterprise Vault server
    2.  
      About disaster recovery of an Enterprise Vault site
    3.  
      Recovering a directory database
    4.  
      Recovering an auditing database
    5.  
      Recovering an FSA Reporting database
    6.  
      Recovering a Monitoring database
    7.  
      Recovering index locations
    8.  
      Recovering an Enterprise Vault vault store group
    9.  
      Recovering a fingerprint database
    10.  
      Recovering a vault store database
    11.  
      Recovering vault store partition
    12.  
      Recovering Enterprise Vault partitions
    13.  
      Recovering an Enterprise Vault server
    14.  
      Recovering an Enterprise Vault server on a different system
  8. Enterprise Vault Agent support for Enterprise Vault
    1. Policy configuration for Enterprise Vault
      1.  
        Open partition, vault store database, and fingerprint database consistencies
      2.  
        Closed and ready partition consistencies
      3.  
        Index location consistencies
      4.  
        Directory database consistencies
    2. Notes about Enterprise Vault 10.0 backups
      1.  
        Exclude file list for index locations
      2.  
        Exclude file list for vault partitions
    3.  
      Excluding files from the exclude list
    4.  
      About planning backup schedules
    5.  
      About hosts for Enterprise Vault policies
    6.  
      About Enterprise Vault tools
    7. About Enterprise Vault agent backups
      1.  
        Privileges for Enterprise Vault backup
    8. About Enterprise Vault agent restores
      1.  
        Changing the socket buffer size for large restores
    9.  
      Useful tips about Enterprise Vault agent
    10. Enterprise Vault agent functionality and support for Enterprise Vault
      1.  
        Differential incremental backup taken after a restore fails for Enterprise Vault
  9. Troubleshooting
    1.  
      About troubleshooting
    2.  
      About debug logging
    3.  
      How to enable debug logging
    4.  
      Setting the debug level
    5.  
      About status reports
    6.  
      About operational reports
    7.  
      About progress reports
    8. About NetBackup status-related troubleshooting information
      1.  
        NetBackup status code 2
      2.  
        NetBackup status code 13
      3.  
        NetBackup status code 39
      4.  
        NetBackup status code 59
      5.  
        NetBackup status code 69
      6. NetBackup status code 156
        1.  
          About the VSS_E_BAD_STATE snapshot error
        2.  
          About the VSS_E_INSUFFICIENT_STORAGE snapshot error
      7.  
        NetBackup status code 1800
  10. Appendix A. NetBackup Enterprise Vault Migrator
    1.  
      About the Enterprise Vault Migrator
    2.  
      About configuring a backup policy for migration
    3.  
      About configuring Enterprise Vault for collection and migration
    4.  
      Testing the Enterprise Vault migrator configuration
    5.  
      Setting the recommended DCOM settings
    6. Restoring Enterprise Vault migrated data from NetBackup
      1.  
        Restoring migrated data using the command line interface
      2.  
        Restoring migrated data using a Backup, Archive, and Restore user interface
    7. Troubleshooting the Enterprise Vault migrator
      1.  
        Enterprise Vault migrator version information
      2. About troubleshooting issues with the migrator
        1.  
          Is the data being archived?
        2.  
          Is the data being collected?
        3.  
          Is the migration being configured appropriately?
        4.  
          Is the data being migrated?
      3. About Log Collection
        1.  
          About Enterprise Vault logs
        2.  
          About Enterprise Vault events
        3.  
          About NetBackup logs

About the Enterprise Vault Database Settings tab

On Enterprise Vault Database Settings tab you can choose how you want to leave the Enterprise Vault SQL database after a restore job completes. You have the option to leave the database operational, non-operational, or in a read-only state that enables you to still restore additional transaction logs. Also, you can perform an alternate SQL restore, a Point in time (PIT) restore, or a consistency check of the database after the restore completes.

Table: Enterprise Vault Database Setting tab options lists the restore options on the Enterprise Vault Database Setting tab.

Table: Enterprise Vault Database Setting tab options

Restore option

Description

Restore completion state

After a restore completes, you can leave an SQL database in any of the following states:

  • Operational

  • Read-only

  • Non-operational

To bring the Enterprise Vault SQL database to the required Point in time (PIT) or end-of-log (EOL), the SQL database restore consists of a set of restores. An example set of restores consists of the following:

  • A FULL database restore

  • The last CUMULATIVE (database differential) restore

  • One or more DIFFERENTIAL (transaction log) backups that were taken after the last cumulative backup

In other scenarios, the set of restores would require a subset of restores, such as a FULL or a FULL and cumulative restore. If the set contains incremental restores, the initial restores should leave the database in a "Restore pending" state so future restores append to the database. Thus, you should use the Leave database operational option only in the last restore job of the restore set. Once the database is brought online, the user cannot make any further cumulative or differential (database differential or transaction log) restores on that database. If you want to perform any further restores, you must start from a FULL database restore.

Note:

Given a PIT or EOL, the NetBackup SQL Agent has the capacity to find the SQL restore set (FULL, database differential, and transaction logs). However, the Enterprise Vault agent does not have this capability; therefore, the user must find and sequence the SQL restore set manually.

Consistency check after restore

You can check the consistency of the database after restores are complete.

To check the consistency of the database, select one of the following consistency checks when you select the Leave database operational option:

  • Full check, excluding indexes

    Select this option to exclude indexes from the consistency check. If indexes are not checked, the consistency check runs significantly faster but is not as thorough. Only the data pages and clustered index pages for each user table are included in the consistency check. The consistency of the nonclustered index pages is not checked.

  • Full check, including indexes

    Select this option to include indexes in the consistency check. Any errors are logged. This option is selected by default.

  • Physical check only (SQL 2000 only)

    This option only applies to SQL Server 2000.

  • None

    Select this option to ensure that no consistency check occurs after a restore.

    Note:

    Any option other than None is effective only in the restore job that brings the database to an operational state.

Point-in-time recovery

To recover the Enterprise Vault SQL database to a PIT, select a restore set that includes the immediate DIFFERENTIAL (transaction log) backup after the PIT. In addition, while restoring this backup you must select the "PIT" option and specify the PIT.

You must ensure that you use the PIT option only with the last differential backup restore. You must select the Leave database operational option in the user interface to enable you to select the PIT option.

Redirected restore

Select this option and specify the new <SQL INSTANCE\SQL database name > to restore to an alternate client, alternate SQL instance, or alternate SQL database. You must do that for each restore in the restore set. The destination SQL database should not be present. If it is present, a chance of data loss in the destination database is possible.

Note:

You can change the SQL INSTANCE name, however do not change the SQL database name. If you change the SQL database name Enterprise Vault does not automatically recognize the new name. If you chose to change the SQL database name then you must also update your Enterprise Vault configuration.

Note:

A redirected restore of an auditing database must be made to the same SQL instance where the directory database resides.

Take database offline

Select this option to disconnect all the connections to the destination SQL database (including Enterprise Vault connections) before it is restored. You should use this option only with the full restore.