Veritas NetBackup™ Release Notes
- About NetBackup 8.3
- New features, enhancements, and changes
- NetBackup 8.3 new features, changes, and enhancements
- Operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- NetBackup Bare Metal Restore operational notes
- NetBackup Cloud operational notes
- NetBackup with Veritas CloudPoint operational notes
- NetBackup database and application agent operational notes
- NetBackup internationalization and localization operational notes
- NetBackup for NDMP operational notes
- NetBackup Snapshot Client operational notes
- NetBackup virtualization operational notes
- Appendix A. About SORT for NetBackup Users
- Appendix B. NetBackup installation requirements
- Appendix C. NetBackup compatibility requirements
- Appendix D. Other NetBackup documentation and related documents
Notes and restrictions for Microsoft SQL Server agent
Note the following for the protection status of an asset:
The NetBackup web UI does not indicate if a classic policy protects an instance or an availability group. Use the NetBackup Administration Console to see how classic policies are used to protect instances or availability groups.
If a backup image does not exist for an asset, the web UI indicates that it is "Not protected".
Databases only appear on the Databases tabs in the NetBackup web UI if they meet one of the following criteria: A backup exists of the database, the database instance has validated credentials, or a manual discovery of databases was performed.
The discovery process displays two messages. First, when a request to start discovery is initiated for the databases or availability groups the web UI displays, "Starting the discovery of…". The discovery doesn't begin until the second message displays, "Successfully started the discovery of ... Click Refresh to update the list."
NetBackup discovers and displays failover cluster instances (FCIs) under the cluster name and the physical node names. For example, instance
FCIis enumerated with both its physical nodes
hostvm11and with its cluster name
sql-fci. Databases are also enumerated with the node names and the cluster name.
You must have the Microsoft SQL Server Native Client version 11.0.7462 ODBC driver or later installed on the availability group replicas to be able to discover and to browse databases on a read-scale availability group. Exit status 114 is received in the NetBackup Administration Console when you browse for databases from a SQL Server intelligent policy. In the web UI, a read-scale availability group is not discovered, but no error message is given.