NetBackup™ Release Notes
- About NetBackup 10.0.0.1
- New features, enhancements, and changes
- Operational notes
- About NetBackup 10.0.0.1 operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- Certain NetBackup web UI nodes do not work when NBAC is configured in the 'Required' or 'Automatic' mode
- Delay in NetBackup web UI when adding or removing columns in Catalog area
- Job actions not available for workload administrators with limited RBAC permissions on assets
- 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 Cloud operational notes
- NetBackup with Veritas CloudPoint operational notes
- CloudPoint on-host agent renewal may fail after RHEL migration with NetBackup 10.0.0.1 upgrade
- Offline VM backup fails with status code 156
- Restoring a VM (with a Read-only disk) from an app-consistent snapshot fails
- VM disks not displayed due to discovery level
- Granular restore fails if target path is deleted and recreated
- 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
- Configuring AWS plug-in with IAM role showed that the Authentication Method field is blank
- 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 for NDMP operational notes
- NetBackup for OpenStack operational notes
- CentOS repository mirror URL is updated
- NetBackup for OpenStack Datamover API (NBOSDMAPI) service times out in the haproxy connection
- Policy schedule start time on the Horizon UI is different than configured in the policy
- Instance volumes in the incremental backups cannot be mounted
- NetBackup primary server does not re-issue the token if NetBackup VM is a 3-node cluster
- Success message appears along with the error message when you delete the policy that has snapshots
- Unable to connect to NetBackup primary server using NBCA
- Excluded Ceph Volume after restore is not mountable or formattable
- Restored VMs have blank metadata config_drive attached
- NBOSVM reconfig fails when you add new NetBackup VM to the cluster
- Database does not sync after NetBackup cluster gets new nodes
- Data on boot disk gets backed up despite exclusion
- After reinitialization and import, OpenStack certificates are missing
- CLI import changes scheduler trust value to disabled
- Unable to get node details after you reinitialize the NetBackup Appliance
- Snapshots fails with "object is not subscriptable" for many policy jobs at the exact same time
- No operation is permitted in insecure way for SSL-enabled Keystone URL
- NetBackup internationalization and localization operational notes
- NetBackup Snapshot Client 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
About NetBackup installation requirements
This release of NetBackup may contain changes to the minimum system requirements and procedures that are required for installation. These changes affect the minimum system requirements for both Windows and UNIX platforms. Much of the installation instructional information in the NetBackup Release Notes is provided for convenience. Detailed installation instructions are found in the NetBackup Installation Guide and the NetBackup Upgrade Guide.
See NetBackup installation and upgrade operational notes.
Before you upgrade the NetBackup server software, you must back up your NetBackup catalogs and verify that the catalog backup was successful.
Database rebuilds are likely to occur in each major, minor (single-dot), and release update (double-dot) version of NetBackup. Therefore, before upgrading to NetBackup 10.0.0.1, you must ensure that you have an amount of free disk space available that is equal to or greater than the size of the NetBackup database. That means for default installations, you are required to have that amount of free space on the file system containing the
/usr/openv/db/data(UNIX) or<install_path>\Veritas\NetBackupDB\data(Windows) directories. If you have changed the location of some of the files in either of these directories, free space is required in those locations equal to or greater than the size of the files in those locations. Refer to the NetBackup Administrator's Guide, Volume I for more information about storing NBDB database files in alternate locations.Note:
This free disk space requirement assumes that you have already performed the best practice of completing a successful catalog backup before you begin the upgrade.
Primary and media servers must have a minimum soft limit of 8000 file descriptors per process for NetBackup to run correctly.
For more information about the effects of an insufficient number of file descriptors, refer to the following articles on the Veritas Support website:
NetBackup primary and media servers exchange server version information at startup, and every 24 hours. This exchange occurs automatically. During startup after an upgrade, the upgraded media server uses the vmd service to push its version information to all of the servers that are listed in its server list.
Veritas recommends that you have the primary server services up and available during a media server upgrade.
All compressed files are compressed using gzip. The installation of these files requires gunzip and gzip, so make sure that they are installed on the computer before you attempt to install NetBackup. For all UNIX platforms except HP-UX, the binaries are expected to be in /bin or /usr/bin and that directory is a part of the root user's PATH variable. On HP-UX systems, the gzip and gunzip commands are expected to be in /usr/contrib/bin. Installation scripts add that directory to the PATH variable. These commands must be present to have successful UNIX installations.