Veritas NetBackup™ Release Notes
- About NetBackup 9.1.0.1
- New features, enhancements, and changes
- Operational notes
- About NetBackup 9.1.0.1 operational notes
- NetBackup installation and upgrade operational notes
- After initiating CA migration, connection errors may occur
- If NetBackup 9.1.0.1 upgrade fails on Windows, revert to previous log folder structure
- Native installation requirements
- NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
- Do not install from the menu that appears when the installation DVD is inserted
- About support for HP-UX Itanium vPars SRP containers
- NetBackup administration and general operational notes
- NetBackup anomaly detection management service may not start after a full catalog restore
- Authorization check fails if you change the user after installation or upgrade in an NBAC-enabled setup
- Restore of the Root ("/") folder for NAS-Data-Protection policy fails
- Errors are shown in the jobs detail when NetBackup attempts to expire images from non-WORM capable storage
- Microsoft Azure backup fails if the resource group name contains a period (.)
- Stale devices shown on the device tree
- Temporary devices listed as file system assets
- NetBackup administration interface operational notes
- Access control methods supported in NetBackup 9.1.0.1
- Job actions not available for workload administrators with limited RBAC permissions on assets
- Using X forwarding to launch the NetBackup Administration Console can fail on certain Linux platforms
- 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
- Wrong error message shown for a supported Podman version
- Snapshots fail when CloudPoint is upgraded to NetBackup 9.1.0.1 while the snapshot jobs are running
- Connection attempt fails for the VM that is in the unreachable or stopped state, and has the credentials associated with it
- Editing a query with special characters in tag names is not supported for the intelligent Cloud groups
- 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
- CloudPoint discovery status shows as failed in the NetBackup web UI
- New CloudPoint asset information may affect recovery
- After upgrade, assets are unsubscribed from protection plans with GRT option enabled
- Backup now option may fail with the error
- Adding new regions requires a new cloud plug-in configuration
- In backup and restore jobs, the number of files transferred is shown as 0
- VM disks not displayed due to discovery level
- Snapshot jobs fail due to exceptions
- Deleted snapshots still visible in the NetBackup web UI
- 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 deduplication operational notes
- NetBackup for NDMP operational notes
- NetBackup for OpenStack operational notes
- Instance volumes in the incremental backups cannot be mounted
- NetBackup master server does not re-issue the token if NetBackup for OpenStack VM is a 3-node cluster
- NetBackup version is displayed as 'Netbackup_9001_beta1' instead of 'NetBackup-CentOS3.10.0 9.0' on the Web UI
- Success message appears along with the error message when you delete the policy that has snapshots
- Unable to connect to NetBackup master 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 for OpenStack VM to the cluster
- Database does not sync after NetBackup for OpenStack 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 for OpenStack 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
- NetBackup virtualization 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 9.1.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.