Please enter search query.
 
              Search <book_title>...
            
 
          Veritas NetBackup™ Release Notes
                Last Published: 
				
                2021-01-15
              
              
                Product(s): 
				
                 NetBackup (8.3.0.1)
              
              
            - About NetBackup 8.3.0.1
 - New features, enhancements, and changes
- About new enhancements and changes in NetBackup
 - NetBackup 8.3.0.1 new features, changes, and enhancements
- NetBackup now supports data immutability and indelibility with the MSDP WORM instance in Flex Appliance
 - Changes to user session default values
 - NetBackup with SAN client 16-gigabit target mode HBA support
 - Updates to the NetBackup for OpenStack plug-in
 - NetBackup supports SSL-enabled (HTTPS) clusters of Hadoop and HBase
 - NetBackup 8.3.0.1 support additions and changes
 - New cloud providers and region support
 
 
 - Operational notes
- About NetBackup 8.3.0.1 operational notes
 - NetBackup installation and upgrade operational notes
- After initiating CA migration, connection errors may occur
 - If NetBackup 8.3.0.1 upgrade fails on Windows, revert to previous log folder structure
 - Native installation requirements
 - NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
 - Do not install from the menu that appears when the installation DVD is inserted
 - About support for HP-UX Itanium vPars SRP containers
 
 - NetBackup administration and general operational notes
- The nbdeployutil utility may fail to generate usage reports for traditional licensing
 - Backups for workloads that use the BigData policy may fail
 - Child backup jobs may enter a queued state for workloads that use BigData policy
 - Errors are shown in the jobs detail when NetBackup attempts to expire images from non-WORM capable storage
 - NetBackup web server certificate renewal failure during initiation of NetBackup CA migration or upgrade
 - Microsoft Azure backup fails if the resource group name contains a period (.)
 - SLP does not retry multistreaming backup if child job fails or is canceled
 - Granular restores require adequate available space on target
 - Stale devices shown on the device tree
 
 - NetBackup administration interface operational notes
- Search limitations for security events lists in the NetBackup web UI
 - Using X forwarding to launch the NetBackup Administration Console can fail on certain Linux platforms
 - Intermittent issues with X forwarding of NetBackup Administration Console
 - NetBackup Administration Console fails in Simplified Chinese UTF-8 locale on Solaris SPARC 64-bit systems with Solaris 10 Update 2 or later
 
 - NetBackup Bare Metal Restore operational notes
 - NetBackup Cloud operational notes
 - NetBackup with Veritas CloudPoint operational notes
- Public cloud not supported with gov cloud or China region
 - Indexing not supported on instances created from AWS Marketplaces AMIs
 - Consistent host snapshot might fail
 - Image clean-up may fail for Microsoft Azure workloads
 - Configuring AWS plug-in with IAM role showed that the Authentication Method field is blank
 - MongoDB create snapshot job may freeze
 - Updating a cloud plug-in while a job runs causes job failure
 - Permission denied error occurs if both user and password are updated
 - Different source and target zones for Google Cloud Platform are not supported
 - Broken files system detected
 
 - NetBackup deduplication 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
 
BMR restore may take significant amount of time for formatting and volume creation step
Due to operating system changes, a Bare Metal Restore (BMR) restore may take significant time during the formatting step when there are logical volumes in the system being restore. Red Hat Enterprise Linux 8 has introduced some changes for LVM2 which causes scanning of the udev database. This scanning takes a significant amount of time for LVM-related operations.
When you perform a BMR restore, you may see the following message in the bmrrst logs:
WARNING: Device * not initialized in udev database even after waiting 10000000 microseconds.
The BMR restore still succeeds, despite the longer restore time.