NetBackup™ Release Notes

Last Published:
Product(s): NetBackup (10.3)
  1. About NetBackup 10.3
    1.  
      About the NetBackup 10.3 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.3 new features, changes, and enhancements
      1.  
        Changes in Veritas terminology
      2.  
        RESTful APIs included in NetBackup 10.3
      3.  
        Introducing universal share accelerator
      4.  
        Restore logs in the NetBackup web UI and location of restore logs
      5.  
        Restore types added to NetBackup web UI for MS-Windows, Standard, and VMware policy types
      6.  
        Recovery for additional policy types added to the NetBackup web UI
      7.  
        NetBackup web UI new policy features
      8.  
        Enhancements in system anomaly detection
      9.  
        Entropy computation in NetBackup
      10.  
        About multi-person authorization
      11.  
        About multi-factor authentication
      12.  
        Certificate-based transport layer security (TLS) authentication
      13.  
        NetBackup 10.3 support additions and changes
      14.  
        Support for AWS Snowball Edge
      15.  
        End of life (EOL) for the Enhanced Auditing feature in NetBackup
      16.  
        End of life (EOL) for the NetBackup Access Control (NBAC) authorization model in NetBackup
      17.  
        Protecting assets with Snapshot Manager's agentless restore feature will require Microsoft Windows Server 2019 or later
      18.  
        NetBackup for OpenStack support for CentOS has ended
      19.  
        Several shutdown commands to be deprecated in a future release
      20.  
        License file required for upgrade
      21.  
        Upgrades to NetBackup 10.3 may take a long time
      22.  
        Before upgrade, default credentials category is NONE
      23.  
        Data-in-transit encryption (DTE) mode is set to 'Preferred On' by default
      24.  
        Update cloud configuration file on the primary server immediately after install or upgrade to NetBackup 10.3
      25.  
        Additional permissions added for new features
      26.  
        Integrate MSDP Cloud credentials into NetBackup generic Credential Management System
      27.  
        MSDP Cloud is now supported on SUSE Linux Enterprise Server
      28.  
        Cloud Catalyst to MSDP Cloud migration is not supported on 10.3 MSDP servers
      29.  
        New features for NetBackup for Microsoft SQL Server
      30.  
        New features for NetBackup for Oracle
      31.  
        Upgrading to Snapshot Manager for Data Center 10.3 for Qumulo plug-in users
      32.  
        New D-NAS features
  3. Operational notes
    1.  
      About NetBackup 10.3 operational notes
    2. NetBackup installation and upgrade operational notes
      1.  
        If NetBackup 10.3 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.  
        Changes to database commands
      2.  
        For some workload environments, reduce the size of the job database before upgrade
      3.  
        Policies using Replication Director fail with error code 4224
      4.  
        Failed to get response from NetBackup malware utility
    4. NetBackup administration interface operational notes
      1.  
        Delay in NetBackup web UI when adding or removing columns in Catalog area
      2.  
        Intermittent issues with X forwarding of NetBackup Administration Console
      3.  
        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.  
        After PIT restore, "The host ID does not exist" error appears
      2.  
        AIX BMR Shared Resource Tree (SRT) creation fails in NetBackup 10.3
      3.  
        NetBackup services may not start automatically after BMR restore on a Linux client
    6. NetBackup Cloud Object Store Workload operational notes
      1.  
        Auto Image Replication (AIR) from NetBackup version 10.3 to 10.1 does not work.
      2.  
        For Azure, backups fail when an older policy is updated with a new backup host
      3.  
        Replicated backups cannot be restored to older NetBackup versions
    7. NetBackup Snapshot Manager (formerly NetBackup CloudPoint)
      1.  
        Indexing not supported on instances created from AWS Marketplaces AMIs
    8. NetBackup NAS operational notes
      1.  
        Parent directories in the path of a file may not be present in an NDMP incremental image
      2.  
        RD storage units are not listed as Replication targets
    9. 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.  
        Instance volumes in the incremental backups cannot be mounted
      4.  
        NetBackup primary server does not re-issue the token if NetBackup VM is a 3-node cluster
      5.  
        Success message appears along with the error message when you delete the policy that has snapshots
      6.  
        Unable to connect to NetBackup primary server using NBCA
      7.  
        Excluded Ceph Volume after restore is not mountable or formattable
      8.  
        Restored VMs have blank metadata config_drive attached
      9.  
        NBOSVM reconfig fails when you add new NetBackup VM to the cluster
      10.  
        Database does not sync after NetBackup cluster gets new nodes
      11.  
        Data on boot disk gets backed up despite exclusion
      12.  
        After reinitialization and import, OpenStack certificates are missing
      13.  
        CLI import changes scheduler trust value to disabled
      14.  
        Unable to get node details after you reinitialize the NetBackup Appliance
      15.  
        Snapshots fails with "object is not subscriptable" for many policy jobs at the exact same time
      16.  
        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
  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.3 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

After PIT restore, "The host ID does not exist" error appears

After a point in time (PIT) restore operation (which may include either a Full File System restore or a BMR restore), the error message The host ID does not exist appears.

In this scenario, a full backup is taken when a SERVICE_USER as root/administrator account is configured. This account takes the backup of the NetBackup installed binaries with root/administrator ownership. Before a restore, SERVICE_USER is configured with an account other than root/administrator, and then an incremental backup is taken where the service user is backed up as part of bp.conf. In a PIT restore operation with the incremental backup, the SERVICE_USER entry gets restored. However, the binaries are restored in the root account ownership.

Workaround:

After changing the service user, you must take a full backup, whether it is a MS-Windows\Standard Policy for File System or BMR policy configuration.