NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Deployment
- Prerequisites for Kubernetes cluster configuration
- Deployment with environment operators
- Deploying NetBackup
- Primary and media server CR
- Deploying NetBackup using Helm charts
- Deploying MSDP Scaleout
- Deploying Snapshot Manager
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Performing catalog backup and recovery
- Section III. Maintenance
- MSDP Scaleout Maintenance
- Upgrading
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Storage server not supporting Instant Access capability on Web UI after upgrading NetBackup
After you upgrade NetBackup 10.0 (10.0.0.1 or 10.1), 10.1.1 to NetBackup 10.2 or MSDP Scaleout to 18.0, if you:
find the storage server not supporting Instant Access capability on Web UI
Or
fail to select MSSQL recovery point to create MSSQL Instant Access on Web UI
Then perform the following steps manually to refresh the Instant Access capability in NetBackup:
Login to NetBackup primary server.
Execute the following commands to refresh the MSDP capabilities on NetBackup primary server:
nbdevconfig -getconfig
nbdevconfig -setconfig
For example,
/usr/openv/netbackup/bin/admincmd/nbdevconfig -getconfig -stype PureDisk -storage_server [storage server] > /tmp/tmp_pd_config_file
/usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server [storage server] -stype PureDisk -configlist /tmp/tmp_pd_config_file
Restart the NetBackup Web Management Console service (nbwmc) on NetBackup primary server.
For example,
/usr/openv/netbackup/bin/nbwmc terminate
/usr/openv/netbackup/bin/nbwmc start