Veritas NetBackup™ Release Notes
- About NetBackup 8.1.2
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 8.1.2 new features, changes, and enhancements
- NetBackup 8.1.2 introduces a new web user interface
- Veritas Smart Meter helps you manage deployment more efficiently
- RESTful APIs included in NetBackup 8.1.2
- Veritas offers the NetBackup Parallel Streaming Framework SDK
- About secure communications in MSDP for Auto Image Replication
- NetBackup 8.1.2 support additions and changes
- VxUpdate replaces LiveUpdate
- NetBackup no longer supports HP-UX and AIX platforms for master and media servers
- Newer Red Hat Linux compilers used with NetBackup 8.1.2
- Linux device persistent binding changes
- BMR introduces secure communication support on AIX and HP-UX
- Supported NetBackup BMR configurations based on operating system and patch release
- Several shutdown commands to be deprecated in a future release
- Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1.2
- Support added for Amazon GLACIER_VAULT storage class
- Auditing enhancements
- NetBackup integration with Vnomic
- NetBackup's BigData policy now protects Microsoft Azure Stack and HBase workloads
- Operational notes
- About NetBackup 8.1.2 operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- Access control methods supported in NetBackup 8.1.2
- NetBackup Administration Console does not show a failure message for incorrect CloudPoint plug-in credentials
- "Operation timed out" message appears when policies are accessed from the Remote Administration Console
- Using X forwarding to launch the NetBackup Administration Console can fail on certain Linux platforms
- Intermittent issues with X forwarding of NetBackup Administration Console
- Reduced functionality during the initialization of the NetBackup Administration Console
- NetBackup Administration Console may encounter a core dump issue when the Simplified Chinese UTF-8 locale is used on a Solaris SPARC 64-bit system with Solaris 10 Update 2 or later
- NetBackup API operational notes
- NetBackup Bare Metal Restore 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 SAN Client and Fibre Transport operational notes
- NetBackup Snapshot Client operational notes
- NetBackup virtualization operational notes
- NetBackup for VMware operational notes
- The NetBackup web UI cannot restore a VM from a replicated backup image
- The NetBackup web UI does not validate VMware server entries
- NetBackup cannot use the nbd or nbdssl transport mode to connect directly to VMware IPv6 ESXi servers
- VMware block-level incremental backups expire when the previous full backup expires
- A VM restore to a vCenter fails when NetBackup has credentials for a restore ESX server
- Virtual machine alert notification may be incorrect for the VMware policies with specific Replication Director options
- 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
GRT backup fails for SharePoint if the SharePoint database object path exceeds the Windows maximum path limit
A Granular Recovery Technology (GRT) backup fails for SharePoint if the SharePoint database object path exceeds the Windows maximum path limit.
During GRT backup, SharePoint database objects are temporarily stored as files within a folder hierarchy. This folder name consists of the SQL Server host name, Backup image ID, and Content Database name within the NetBackup temporary directory path. Together this combination should not exceed the Windows path length limitation. For more details, refer to the following Microsoft article:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx
If the Windows path length limitation is exceeded, then the result can be a failure to capture the backup artifacts for GRT for SharePoint.
Workaround: Ensure that the content database name along with the other parameters mentioned above does not exceed the Windows maximum path limit.