Veritas NetBackup™ for Enterprise Vault™ Agent Administrator's Guide
- 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
NetBackup status code 2
Message: none of the requested files were backed up
The following list can help determine the cause of the issue:
Verify if the Enterprise Vault services are running on the related Enterprise Vault servers.
Enterprise Vault services could be stopped automatically if any disk volume in the system is full. In addition, the Enterprise Vault services could stop if the client is also a media server and if a disk storage unit is full. In this situation, you would start the Enterprise Vault services and re-run the backup.
Verify whether the Enterprise Vault user name credentials that are given in the client host properties are correct or not.
Ensure that MSXML is installed.
If MSXML 6 is not installed, the client's bpresolver log contains the following error message:
registry key for MSXML6 not found. Seems that MSXML6 is not installed...Exiting
You should install MSXML 6 and run the backup again.
Look at the Event Viewer of the policy client and related Enterprise Vault servers.
Quiescence can fail if the Enterprise Vault component (Vault store or Index location) or its parent component (such as, vault store group or site) is already quiesced. The backups fail with a status 2. You should clear the backup mode and attempt to run the backup again.
A backup can fail with a status 2 if the backup runs within a few minutes from when an Enterprise Vault directory database was restored. You should browse the Enterprise Vault configuration from Vault Administration Console and attempt to run the backup again.