NetBackup™ Release Notes

Last Published:
Product(s): NetBackup (10.0.0.1)
  1. About NetBackup 10.0.0.1
    1.  
      About the NetBackup 10.0.0.1 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 10.0.0.1 new features, changes, and enhancements
      1.  
        Changes in Veritas terminology
      2.  
        Veritas announces EOL of NetBackup clients on HP-UX
      3.  
        Several shutdown commands to be deprecated in a future release
      4.  
        Update cloud configuration file on the primary server immediately after install or upgrade to NetBackup 10.0.0.1
      5.  
        NetBackup for OpenStack enhancements
  3. Operational notes
    1.  
      About NetBackup 10.0.0.1 operational notes
    2. NetBackup installation and upgrade operational notes
      1.  
        If NetBackup 10.0.0.1 upgrade fails on Windows, revert to previous log folder structure
      2.  
        Native installation requirements
      3.  
        NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
      4.  
        About support for HP-UX Itanium vPars SRP containers
    3. NetBackup administration and general operational notes
      1.  
        Restore of the Root ("/") folder for NAS-Data-Protection policy fails
      2.  
        Stale devices shown on the device tree
      3.  
        Temporary devices listed as file system assets
    4. NetBackup administration interface operational notes
      1.  
        Certain NetBackup web UI nodes do not work when NBAC is configured in the 'Required' or 'Automatic' mode
      2.  
        Delay in NetBackup web UI when adding or removing columns in Catalog area
      3.  
        Job actions not available for workload administrators with limited RBAC permissions on assets
      4.  
        Intermittent issues with X forwarding of NetBackup Administration Console
      5.  
        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 Cloud operational notes
      1.  
        Restore of cloud VM backup images replicated with AIR fails Pre-recovery check
      2.  
        Configuring a cloud recovery host on RHEL 8
    6. NetBackup with Veritas CloudPoint operational notes
      1.  
        CloudPoint on-host agent renewal may fail after RHEL migration with NetBackup 10.0.0.1 upgrade
      2.  
        Offline VM backup fails with status code 156
      3.  
        Restoring a VM (with a Read-only disk) from an app-consistent snapshot fails
      4.  
        VM disks not displayed due to discovery level
      5.  
        Granular restore fails if target path is deleted and recreated
      6.  
        Public cloud not supported with gov cloud or China region
      7.  
        Indexing not supported on instances created from AWS Marketplaces AMIs
      8.  
        Consistent host snapshot might fail
      9.  
        Configuring AWS plug-in with IAM role showed that the Authentication Method field is blank
      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
    7. NetBackup for NDMP operational notes
      1.  
        Parent directories in the path of a file may not be present in an NDMP incremental image
    8. NetBackup for OpenStack operational notes
      1.  
        CentOS repository mirror URL is updated
      2.  
        NetBackup for OpenStack Datamover API (NBOSDMAPI) service times out in the haproxy connection
      3.  
        Policy schedule start time on the Horizon UI is different than configured in the policy
      4.  
        Instance volumes in the incremental backups cannot be mounted
      5.  
        NetBackup primary server does not re-issue the token if NetBackup VM is a 3-node cluster
      6.  
        Success message appears along with the error message when you delete the policy that has snapshots
      7.  
        Unable to connect to NetBackup primary server using NBCA
      8.  
        Excluded Ceph Volume after restore is not mountable or formattable
      9.  
        Restored VMs have blank metadata config_drive attached
      10.  
        NBOSVM reconfig fails when you add new NetBackup VM to the cluster
      11.  
        Database does not sync after NetBackup cluster gets new nodes
      12.  
        Data on boot disk gets backed up despite exclusion
      13.  
        After reinitialization and import, OpenStack certificates are missing
      14.  
        CLI import changes scheduler trust value to disabled
      15.  
        Unable to get node details after you reinitialize the NetBackup Appliance
      16.  
        Snapshots fails with "object is not subscriptable" for many policy jobs at the exact same time
      17.  
        No operation is permitted in insecure way for SSL-enabled Keystone URL
    9. 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
    10. NetBackup Snapshot Client operational notes
      1.  
        Snapshot job fails with status code 927
      2.  
        HPE 3PAR array snapshot import fails with status code 4213
      3.  
        Snapshots are deleted after point-in-time rollbacks
      4.  
        Index from Snapshot operation does not populate contents of the snapshot accurately in the catalog
  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
    3.  
      NetBackup 10.0.0.1 binary sizes
  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

Job actions not available for workload administrators with limited RBAC permissions on assets

Note following issues for view and managing jobs with the NetBackup web UI:

  • A job does not receive an asset ID until it runs, which means a queued job does not have an asset ID. Users that have roles with more granular asset permissions for a workload are not able to view or cancel queued jobs.

    This behavior does not affect users with an RBAC role that has full job permissions or a role that can manage all assets for a particular workload.

  • A job does not receive an asset ID if the asset is not yet discovered. Users that have roles with more granular asset permissions for a workload are not able to cancel or restart a job for the asset.

    This behavior does not affect users with an RBAC role that has full job permissions or a role that can manage all assets for a particular workload.

Example 1 - VMware administrator with limited asset permissions cannot cancel any queued jobs

Consider a user that has RBAC permissions only for a VMware vCenter or one or more VMs.

  • The user cannot see queued jobs for the vCenter or for the VMs.

  • Similarly, the user is not able to cancel any queued jobs for the vCenter or for the VMs.

Example 2 - VMware or RHV administrator with limited asset permissions cannot cancel or restart jobs for undiscovered assets

Consider a user that has RBAC permissions only for a VMware vCenter or an RHV server. This user also has one or more job permissions for these assets, but does not have job permissions for all workload assets.

  • A new asset is added to the environment, but the discovery process hasn't run yet.

  • An existing intelligent group is configured so it includes the new asset.

  • When the backup runs, it includes the new asset in the backup.

  • The user is not able to cancel or restart a job for the new asset.