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
- 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
- Index
About Enterprise Vault agent backups
Review the following information about the Enterprise Vault agent backups before planning the SQL database backup:
When you attempt to back up an SQL database, Veritas recommends that you run a full backup before any incremental backup. If you perform scheduled incremental backups when no full backup exists the following occurs:
The first scheduled Cumulative incremental backup is a streamed-base backup and is treated as a full backup. However, the Backup, Archive, and Restore user interface displays the backup as a Cumulative backup. As a result, any following scheduled Cumulative incremental backups are "cumulative" in nature.
The first scheduled Differential incremental backup is a streamed-base backup and is treated as a full backup. However, the Backup, Archive, and Restore user interface displays the backup as a Differential backup. As a result, any following scheduled Differential incremental backups are "differential" in nature.
If a full backup for an Enterprise Vault SQL database fails, manually initiate a second full backup and ensure that it finishes successfully before a Cumulative Incremental schedule backup starts. If the full backup for an Enterprise Vault SQL database fails, the following occurs:
Any Cumulative incremental backups that were run after the failure and before the next, successful full backup cannot be restored. This issue only affects Cumulative backups after a failed full backup. Differential incremental backups are not affected, even after a failed full backup.
An attempt to restore these Cumulative Incremental backup images fails with a status 5 error, and this failure can result in a data loss. The tar log file contains the following message: SQL Error Description: This differential backup cannot be restored because the database has not been restored to the correct earlier state.
You can however, restore the data from the Differential backup images. You must restore all of the Differential backup images after the restore of the last full-backup image.
To avoid this issue, Veritas recommends that you make sure the full backup is successful before you begin a Cumulative incremental backup. Ensuring a successful full backup before you attempt Cumulative backup guards against a data loss scenario.
Finally, check whether you have the required privileges to create backups using the Enterprise Vault agent.