Veritas NetBackup™ Release Notes
- About NetBackup 8.1
- New features, enhancements, and changes
- NetBackup 8.1 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 Accelerator operational notes
- NetBackup Bare Metal Restore operational notes
- NetBackup Cloud operational notes
- NetBackup cluster operational notes
- NetBackup database and application agent operational notes
- NetBackup for Exchange operational notes
- NetBackup for SharePoint operational notes
- NetBackup for Oracle operational notes
- NetBackup deduplication operational notes
- NetBackup internationalization and localization operational notes
- NetBackup for NDMP operational notes
- NetBackup virtualization operational notes
- NetBackup for VMware operational notes
- NetBackup for VMware 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
Changes to policy and other configuration for SQL Server clusters and SQL Server AGs
For legacy SQL Server backups (using batch files), NetBackup no longer requires a second policy that contains the cluster or AG node names. To perform restores, you no longer need to configure permissions for redirected restores (altnames). The mappings in the Distributed Application Restore Mapping host properties replace these configuration steps.
If you are upgrading from an earlier version of NetBackup, you can still use both the second "node name" policy and the altnames permissions for successful backups and restores of SQL Server. However, Veritas recommends that you allow restores only to specific hosts. In NetBackup 8.1, the No.Restrictions
file only allows a requesting client to perform a redirected restore if that client is known by the master server.