Veritas NetBackup™ Release Notes

Last Published:
Product(s): NetBackup (8.3.0.2)
  1. About NetBackup 8.3.0.2
    1.  
      About the NetBackup 8.3.0.2 release
    2.  
      About NetBackup Late Breaking News
    3.  
      About NetBackup third-party legal notices
  2. New features, enhancements, and changes
    1.  
      About new enhancements and changes in NetBackup
    2.  
      NetBackup 8.3.0.2 new features, changes, and enhancements
  3. Operational notes
    1.  
      About NetBackup 8.3.0.2 operational notes
    2. NetBackup installation and upgrade operational notes
      1.  
        After initiating CA migration, connection errors may occur
      2.  
        If NetBackup 8.3.0.2 upgrade fails on Windows, revert to previous log folder structure
      3.  
        Native installation requirements
      4.  
        NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
      5.  
        Do not install from the menu that appears when the installation DVD is inserted
      6.  
        About support for HP-UX Itanium vPars SRP containers
    3. NetBackup administration and general operational notes
      1.  
        The nbdeployutil utility may fail to generate usage reports for traditional licensing
      2.  
        Child backup jobs may enter a queued state for workloads that use BigData policy
      3.  
        Errors are shown in the jobs detail when NetBackup attempts to expire images from non-WORM capable storage
      4.  
        NetBackup web server certificate renewal failure during initiation of NetBackup CA migration or upgrade
      5.  
        Microsoft Azure backup fails if the resource group name contains a period (.)
      6.  
        SLP does not retry multistreaming backup if child job fails or is canceled
      7.  
        Granular restores require adequate available space on target
      8.  
        Stale devices shown on the device tree
    4. NetBackup administration interface operational notes
      1.  
        Search limitations for security events lists in the NetBackup web UI
      2.  
        Using X forwarding to launch the NetBackup Administration Console can fail on certain Linux platforms
      3.  
        Intermittent issues with X forwarding of NetBackup Administration Console
      4.  
        NetBackup Administration Console fails in Simplified Chinese UTF-8 locale on Solaris SPARC 64-bit systems with Solaris 10 Update 2 or later
    5. NetBackup Bare Metal Restore operational notes
      1.  
        BMR boot server not supported on a NetBackup appliance or a Flex appliance
      2.  
        BMR restore may take significant amount of time for formatting and volume creation step
    6. NetBackup Cloud operational notes
      1.  
        Configuring a cloud recovery host on RHEL 8
      2.  
        Indexing error may occur for Micorosft Azure cloud assets
    7. NetBackup with Veritas CloudPoint operational notes
      1.  
        On-host agent may be unavailable after restore with a snapshot taken with NetBackup CloudPoint 8.3
      2.  
        Application status of original instances may report errors for host-consistent restores to alternate locations
      3.  
        Public cloud not supported with gov cloud or China region
      4.  
        Indexing not supported on instances created from AWS Marketplaces AMIs
      5.  
        Consistent host snapshot might fail
      6.  
        Image clean-up may fail for Microsoft Azure workloads
      7.  
        Configuring AWS plug-in with IAM role showed that the Authentication Method field is blank
      8.  
        MongoDB create snapshot job may freeze
      9.  
        Updating a cloud plug-in while a job runs causes job failure
      10.  
        Permission denied error occurs if both user and password are updated
      11.  
        Different source and target zones for Google Cloud Platform are not supported
      12.  
        Broken files system detected
    8. NetBackup deduplication operational notes
      1.  
        Backup jobs fail with "Storage server is down ..." for WORM storage servers in multi-domain environments
    9. NetBackup for NDMP operational notes
      1.  
        Parent directories in the path of a file may not be present in an NDMP incremental image
    10. NetBackup internationalization and localization operational notes
      1.  
        Support for localized environments in database and application agents
      2.  
        Certain NetBackup user-defined strings must not contain non-US ASCII characters
    11. NetBackup Snapshot Client operational notes
      1.  
        HPE 3PAR array snapshot import fails with status code 4213
      2.  
        Snapshots are deleted after point-in-time rollbacks
      3.  
        Index from Snapshot operation does not populate contents of the snapshot accurately in the catalog
    12. NetBackup virtualization operational notes
      1. NetBackup for VMware operational notes
        1.  
          VMware protection plan creation can fail when automatic scheduling and WORM storage are used
        2.  
          Media servers cannot access the virtualization server, fails with status code 200
  4. Appendix A. About SORT for NetBackup Users
    1.  
      About Veritas Services and Operations Readiness Tools
  5. Appendix B. NetBackup installation requirements
    1.  
      About NetBackup installation requirements
    2.  
      Required operating system patches and updates for NetBackup
  6. Appendix C. NetBackup compatibility requirements
    1.  
      About compatibility between NetBackup versions
    2.  
      About NetBackup compatibility lists and information
    3.  
      About NetBackup end-of-life notifications
  7. Appendix D. Other NetBackup documentation and related documents
    1.  
      About related NetBackup documents

Index from Snapshot operation does not populate contents of the snapshot accurately in the catalog

Note:

This issue is specific to on-premises workloads and UNIX platforms.

In the case of the Index from Snapshot operation, if the /usr/openv directory on the snapshot mount host is linked to a different path, the contents of the snapshot is not indexed accurately in the catalog.

Workaround: Reconfigure the storage lifecycle policy to have only the snapshot operation and remove the index from snapshot operation.