NetBackup™ Release Notes
- About NetBackup 10.5
- New features, enhancements, and changes
- NetBackup 10.5 new features, changes, and enhancements
- Operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- NetBackup Cloud Object Store Workload operational notes
- NetBackup Snapshot Manager (formerly NetBackup CloudPoint)
- NetBackup database and application agent operational notes
- NetBackup NAS operational notes
- NetBackup for OpenStack operational notes
- 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
Cloud Scale and decoupling of Cloud Scale
With this release, the following describes the features, enhancements, and changes for Cloud Scale and decoupling of Cloud Scale.
Cloud Scale deployment on a single node Kubernetes environment
Cloud Scale Technology can be deployed on the single node of a Kubernetes cluster. This deployment provides a cost-effective solution as it requires only one node in a Kubernetes cluster where all the Cloud Scale components are easily deployed.
Cost optimization for Media server load balancers
Along with CPU and memory usage, the media server scale-out is also seen if the jobs are found in queued state due to the maximum job per media server settings.
Decoupling of Cloud Scale
Decoupling of NetBackup web services from primary server The NetBackup web services are decoupled (dissociated) from the primary server in the Cloud Scale Technology. This change has been made to containerize the web services and run it as a standalone service pod in a Kubernetes cluster.
Consolidated log location in Cloud Scale using fluentbit
This feature lets you consolidate the log files that have been distributed during the process of running NetBackup in a scale-out environment.
Decoupling of NetBackup Policy and Job Management (NBPEM/NBJM) from primary server
The NetBackup policy and job management capabilities are decoupled from the primary server and run as a separate service in a Kubernetes cluster.
NetBackup Authentication Broker (nbatd) service
Enabling the FIPS mode for nbatd: For Cloud Scale deployment, the nbatd containerized service runs in a separate Kubernetes pod cluster server rather than the NetBackup primary server pod. Hence enable the FIPS mode for the NetBackup Authentication Broker service.
AD/LDAP domain: For Cloud Scale deployment, the nbatd containerized service runs in a separate Kubernetes pod cluster server rather than the NetBackup primary server pod. Therefore, the existing AD/LDAP domain configuration on the primary server Kubernetes pod does not work. Reconfigure the AD/LDAP domain.
Request routing and load balancing for scale-out server
For NetBackup Cloud Scale deployment, with NetBackup deployed in a scale-out form factor, a single endpoint called request router is created for external requests to come into the system. The requests are distributed to the appropriate services or individual instances of a service for processing.
For more information, see the NetBackup Deployment Guide for Kubernetes Cluster.