NetBackup™ Release Notes
- About NetBackup 9.1
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 9.1 new features, changes, and enhancements
- Changes in Veritas terminology
- Backup and restore of Kubernetes applications
- Backup anomaly detection in NetBackup
- Non-privileged user or service user account to run NetBackup services
- Support for AD user groups in the auth.conf file
- 2 FA support for the NetBackup Administration Console through SAML-based Identity Provider or CAC/PIV smart cards or user certificates
- NetBackup Client Direct deduplication is now supported with WORM
- Case insensitivity for client names in a NetBackup policy
- RESTful APIs included in NetBackup 9.1
- API keys enhancements
- BMR enhancements
- NetBackup support for vCloud Director 9.0, 9.1, and 9.5 has ended
- nbdeployutil renamed to NetBackup Deployment Insights
- About the NetBackup Smart Diagnosis (nbsmartdiag) utility
- EOL for support on RHEL 7.0 through 7.3
- EOL for CentOS 8 support
- NetBackup 9.1 support additions and changes
- Several shutdown commands to be deprecated in a future release
- Windows compiler and security requirements for NetBackup 9.1 and later installation and upgrade
- New RBAC default roles
- Changes to the RBAC permissions for jobs
- Update cloud configuration file on the primary server immediately after install or upgrade to NetBackup 9.1
- EOL for CloudPoint version 2.x
- Automated asset protection with intelligent cloud groups
- Changes to Cloud protection policies
- CloudPoint extensions for scalable workflows
- New backup options for cloud workloads
- Backup from snapshot
- Parameterized restore
- Windows agentless support
- Support for Microsoft Azure Stack Hub
- Support for CloudPoint on an RHEL 8.3 Podman environment
- Support for CloudPoint on SUSE Linux Enterprise Server (SLES)
- Continuous data protection (CDP) provides backup for VMware without stunning the VMs
- Combined deployment of NetBackup family products
- Cloud enhancements for administrators
- Instant rollback for VMs
- For VMware and RHV environments, reduce the size of the job database before upgrade
- Query options added for VMware intelligent policies
- Nutanix AHV enhancements
- Oracle Instance Management to be removed from NetBackup Administration Console
- NetBackup Oracle Intelligent Policy can be configured with options for Data Guard
- Oracle and DB2 policy templates are deprecated in the NetBackup 9.1 release
- NetBackup for Microsoft SQL Server agent enhancements
- New behavior for Oracle and Microsoft SQL Server intelligent policies
- Operational notes
- About NetBackup 9.1 operational notes
- NetBackup installation and upgrade operational notes
- After initiating CA migration, connection errors may occur
- If NetBackup 9.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
- Permissions necessary for redirected restores with non-root service user accounts
- 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
- 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
- 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
- Updating a cloud plug-in while a job runs causes job failure
- 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 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 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
- 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
Granular restore fails if target path is deleted and recreated
On protected VM assets, if you recreate a filesystem and mount it to the same drive or path, then subsequent discovery updates the CloudPoint asset database for newly created filesystems. Also, the old filesystem assets that are mounted on same drive or mount point are marked for deletion but not removed from asset database. This is because the retention period is of 1 day if there is no snapshot associated to the older filesystem asset. In this case, if you initiate the granular restore with the same drive or mount path as a target, then the operation might fail with an error. This issue doesn't occur if you try granular restore after 1 day on the such drives or mount paths. This problem also exists if you unmount the existing disk from the drive or mount path and mount another file-system to same drive or mount path.
Workaround:
Do not use a filesystem as granular restore target destination that was recreated from an existing filesystem or newly created filesystem on last discovered mount point or drive.