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
About restoring Enterprise Vault SQL databases
Note:
Restoring multiple Enterprise Vault images in one restore operation is not supported in this release. Veritas recommends that you restore one backup image at a time. Selecting multiple backup images in a single restore job may give unpredictable results.
Review the following notes before you attempt to restore an Enterprise Vault SQL database:
Restore full and incremental backups one at a time.
When you do a redirected restore, you must select the Redirected restore option and specify the alternate SQL instance name and database name. (This requirement applies to each restore in the restore set.) The SQL instance name always contains the system name. (For default instances, the system name is the instance name.)
The Enterprise Vault agent cannot restore data and log files (.MDF and .LDF files) of an Enterprise Vault SQL database to a physical path that is different from the original physical path. As a result, the Enterprise Vault SQL restore is affected as follows:
The drive (C:/ or D:/) used by these files at backup time is available at the restore time (in the destination client).
In the redirected restore, if a new path (SQL instance or database name) already exists and it is associated with some other physical files. The database becomes associated with the new physical files after the restore completes. The physical files of the old database become dangling files and are no longer associated with a database.
In the redirected restore, if the physical files to be restored are present and associated with some other database, manually take the database offline. If you do not take the database offline, the restore cannot overwrite those files.