Please enter search query.
Search <book_title>...
Veritas NetBackup™ for Enterprise Vault™ Agent Administrator's Guide
Last Published:
2018-09-19
Product(s):
NetBackup (8.2, 8.1.2, 8.1.1)
- Introduction to NetBackup Enterprise Vault
- About NetBackup Enterprise Vault agent installation requirements
- Installation requirements for NetBackup Enterprise Vault agent
- Verifying Enterprise Vault agent operating system compatibility
- NetBackup server and client software requirements
- About Enterprise Vault agent installation requirements in a cluster
- Configuring Enterprise Vault Agent to protect Enterprise Vault databases
- Adding the Enterprise Vault agent license key
- Configuration requirements for upgrading the Enterprise Vault agent
- Configuration
- About the Windows and Java user interfaces
- Specifying a logon account for the Enterprise Vault server
- About VSS-based snapshot configuration
- Configuring the local media server for Enterprise Vault backup
- Configuration requirements for an Enterprise Vault backup policy
- Adding a new Enterprise Vault policy
- Enterprise Vault backup policy attributes
- Adding schedules to an Enterprise Vault policy
- About the types of Enterprise Vault backups
- Creating a backup selections list
- Adding a client to a policy
- About features provided by Enterprise Vault for a backup provider
- Performing backups of Enterprise Vault
- Performing restores of Enterprise Vault
- Important notes about Enterprise Vault data restore
- Stopping the administrative services on Enterprise Vault servers
- About the Backup, Archive, and Restore interface
- Viewing backup data using the Microsoft SQL Server Management Studio
- Restoring Enterprise Vault data
- About the Enterprise Vault restore options on the General tab
- About the Enterprise Vault Database Settings tab
- Specifying the server, clients, and policy type for restores
- About restoring Enterprise Vault file system data
- Restoring an Enterprise Vault file system component
- About restoring Enterprise Vault SQL databases
- Restoring Enterprise Vault SQL database components
- Disaster recovery
- Disaster recovery requirements for Enterprise Vault server
- About disaster recovery of an Enterprise Vault site
- Recovering a directory database
- Recovering an auditing database
- Recovering an FSA Reporting database
- Recovering a Monitoring database
- Recovering index locations
- Recovering an Enterprise Vault vault store group
- Recovering a fingerprint database
- Recovering a vault store database
- Recovering vault store partition
- Recovering Enterprise Vault partitions
- Recovering an Enterprise Vault server
- Recovering an Enterprise Vault server on a different system
- Enterprise Vault Agent support for Enterprise Vault
- Policy configuration for Enterprise Vault
- Notes about Enterprise Vault 10.0 backups
- Excluding files from the exclude list
- About planning backup schedules
- About hosts for Enterprise Vault policies
- About Enterprise Vault tools
- About Enterprise Vault agent backups
- About Enterprise Vault agent restores
- Useful tips about Enterprise Vault agent
- Enterprise Vault agent functionality and support for Enterprise Vault
- Troubleshooting
- Appendix A. NetBackup Enterprise Vault Migrator
- About the Enterprise Vault Migrator
- About configuring a backup policy for migration
- About configuring Enterprise Vault for collection and migration
- Testing the Enterprise Vault migrator configuration
- Setting the recommended DCOM settings
- Restoring Enterprise Vault migrated data from NetBackup
- Troubleshooting the Enterprise Vault migrator
Open partition, vault store database, and fingerprint database consistencies
To ensure consistency when backing up a fingerprint database, you should add all open partitions of the vault store group and the fingerprint database in the same policy. By grouping these components into a single policy, you can ensure that the specified Vault Stores remain in backup mode until all snapshots are taken or the backup finishes. Configuring a policy in this way also means that the vault stores spend less time in backup mode.
The following is an example of how you would configure a new policy that includes a fingerprint database:
EV_OPEN_PARTITION=vs1
EV_OPEN_PARTITION=vs2
EV_OPEN_PARTITION=vs3
EV_FINGERPRINT_DB=vsg1
Where vsg1 is a vault store group and vs1, vs2, and vs3 are all the vault stores under vsg1.