Veritas NetBackup™ Release Notes

Last Published:
Product(s): NetBackup (9.1.0.1)
  1. About NetBackup 9.1.0.1
    1.  
      About the NetBackup 9.1.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 9.1.0.1 new features, changes, and enhancements
      1.  
        EOL for NetBackup on Solaris on primary and media servers
      2.  
        EOL of NetBackup SCVMM plugin for Hyper-V
      3.  
        Changes in Veritas terminology
  3. Operational notes
    1.  
      About NetBackup 9.1.0.1 operational notes
    2. NetBackup installation and upgrade operational notes
      1.  
        After initiating CA migration, connection errors may occur
      2.  
        If NetBackup 9.1.0.1 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.  
        NetBackup anomaly detection management service may not start after a full catalog restore
      2.  
        Authorization check fails if you change the user after installation or upgrade in an NBAC-enabled setup
      3.  
        Restore of the Root ("/") folder for NAS-Data-Protection policy fails
      4.  
        Errors are shown in the jobs detail when NetBackup attempts to expire images from non-WORM capable storage
      5.  
        Microsoft Azure backup fails if the resource group name contains a period (.)
      6.  
        Stale devices shown on the device tree
      7.  
        Temporary devices listed as file system assets
    4. NetBackup administration interface operational notes
      1.  
        Access control methods supported in NetBackup 9.1.0.1
      2.  
        Job actions not available for workload administrators with limited RBAC permissions on assets
      3.  
        Using X forwarding to launch the NetBackup Administration Console can fail on certain Linux platforms
      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.  
        Error in calculating the snapshot size in smart metering for Cloud workloads
      2.  
        Pre-recovery check for VM restore fails on Windows-based NetBackup primary or media servers if the VM's display name contains multi-byte characters
      3.  
        Configuring a cloud recovery host on RHEL 8
    6. NetBackup with Veritas CloudPoint operational notes
      1.  
        Wrong error message shown for a supported Podman version
      2.  
        Snapshots fail when CloudPoint is upgraded to NetBackup 9.1.0.1 while the snapshot jobs are running
      3.  
        Connection attempt fails for the VM that is in the unreachable or stopped state, and has the credentials associated with it
      4.  
        Editing a query with special characters in tag names is not supported for the intelligent Cloud groups
      5.  
        Starting or restarting the CloudPoint services may fail if a stale IP address entry is retained in the Podamn layer on RHEL 8.3 environment
      6.  
        CloudPoint discovery status shows as failed in the NetBackup web UI
      7.  
        New CloudPoint asset information may affect recovery
      8.  
        After upgrade, assets are unsubscribed from protection plans with GRT option enabled
      9.  
        Backup now option may fail with the error
      10.  
        Adding new regions requires a new cloud plug-in configuration
      11.  
        In backup and restore jobs, the number of files transferred is shown as 0
      12.  
        VM disks not displayed due to discovery level
      13.  
        Snapshot jobs fail due to exceptions
      14.  
        Deleted snapshots still visible in the NetBackup web UI
      15.  
        Granular restore fails if target path is deleted and recreated
      16.  
        Public cloud not supported with gov cloud or China region
      17.  
        Indexing not supported on instances created from AWS Marketplaces AMIs
      18.  
        Consistent host snapshot might fail
      19.  
        Configuring AWS plug-in with IAM role showed that the Authentication Method field is blank
      20.  
        Permission denied error occurs if both user and password are updated
      21.  
        Different source and target zones for Google Cloud Platform are not supported
      22.  
        Broken files system detected
    7. NetBackup deduplication operational notes
      1.  
        Backup jobs fail with "Storage server is down ..." for WORM storage servers in multi-domain environments
    8. NetBackup for NDMP operational notes
      1.  
        Parent directories in the path of a file may not be present in an NDMP incremental image
    9. NetBackup for OpenStack operational notes
      1.  
        Instance volumes in the incremental backups cannot be mounted
      2.  
        NetBackup master server does not re-issue the token if NetBackup for OpenStack VM is a 3-node cluster
      3.  
        NetBackup version is displayed as 'Netbackup_9001_beta1' instead of 'NetBackup-CentOS3.10.0 9.0' on the Web UI
      4.  
        Success message appears along with the error message when you delete the policy that has snapshots
      5.  
        Unable to connect to NetBackup master server using NBCA
      6.  
        Excluded Ceph Volume after restore is not mountable or formattable
      7.  
        Restored VMs have blank metadata config_drive attached
      8.  
        NBOSVM reconfig fails when you add new NetBackup for OpenStack VM to the cluster
      9.  
        Database does not sync after NetBackup for OpenStack cluster gets new nodes
      10.  
        Data on boot disk gets backed up despite exclusion
      11.  
        After reinitialization and import, OpenStack certificates are missing
      12.  
        CLI import changes scheduler trust value to disabled
      13.  
        Unable to get node details after you reinitialize the NetBackup for OpenStack Appliance
      14.  
        Snapshots fails with "object is not subscriptable" for many policy jobs at the exact same time
      15.  
        No operation is permitted in insecure way for SSL-enabled Keystone URL
    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.  
        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
    12. NetBackup virtualization operational notes
      1.  
        RHV VM backups and restores require a role with minimum permissions
  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

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.

  • An asset ID is not set for a cloud convert job. Users that have roles with more granular permissions for VMware assets can't view these jobs.

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

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.