NetBackup™ Release Notes
- About NetBackup 10.1
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 10.1 new features, changes, and enhancements
- Changes in Veritas terminology
- Malware detection enhancements
- RESTful APIs included in NetBackup 10.1
- Additional policy types supported in the NetBackup web UI
- Activity monitor improvements in the NetBackup web UI
- Enhancements in FIPS support
- NetBackup 10.1 support additions and changes
- About the TLS session resumption feature in Global security
- Support updates for universal share
- Support updates for instant access for cloud backups
- Several shutdown commands to be deprecated in a future release
- NetBackup Snapshot Manager must run the same version as NetBackup primary and media servers
- Update cloud configuration file on the primary server immediately after install or upgrade to NetBackup 10.1
- Migrating Google Cloud Platform (GCP) configurations from zones to regions
- Support for new PaaS databases
- Support for cloud immutable (WORM) storage in a cluster environment
- Support for S3 interface for MSDP
- Malware scanner available in the Microsoft Azure Marketplace and the AWS Marketplace
- Setting the cloud cache size in the MSDP disk pool cloud LSU
- Cloud object store workload support
- VMware NAS storage snapshots and replication using NetBackup Snapshot Manager
- Reinstall Kubernetes-based extension for Azure
- MySQL enhancements
- PostgreSQL enhancements
- Workloads that require a custom RBAC role for specific job permissions in the NetBackup web UI
- Web UI support for Microsoft SQL Server recovery using existing credentials and gMSA credentials
- Accurate licensing support
- XBSA workloads available with the NetBackup client
- No release of NetBackup OpsCenter and OpsCenter Analytics
- Transition from Replication Director to NetBackup Snapshot Manager Replication
- NetBackup Bare Metal Restore (BMR) operations in the NetBackup web UI
- IRE limitations
- Limitations for running NetBackup services with non-privileged user (service user) account in NetBackup 10.1
- Operational notes
- About NetBackup 10.1 operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration interface operational notes
- 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
- Child job details for a NetBackup catalog backup display the policy type "Sybase"
- Cloud snapshot replication jobs are not visible to the Default Cloud Administrator in the NetBackup web UI
- Policy name link does not work for some failed jobs in the web UI Activity Monitor
- 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 Bare Metal Restore operational notes
- NetBackup Snapshot Manager (formerly NetBackup CloudPoint)
- 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
- 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
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.
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.
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.