Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2023-04-24
Product(s):
NetBackup (10.2)
- 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
View the list of product resources
To view the list of product resources run the following command:
$ kubectl get --namespace <namespace> all,environments,primaryservers,mediaservers,msdpscaleouts
The output should look like the following:
NAME READY STATUS RESTARTS AGE pod/dedupe1-uss-controller -79d554f8cc-598pr 1/1 Running 0 68m pod/dedupe1-uss-mds-1 1/1 Running 0 75m pod/dedupe1-uss-mds-2 1/1 Running 0 74m pod/dedupe1-uss-mds-3 1/1 Running 0 71m pod/media1-media-0 1/1 Running 0 53m pod/environment-sample -primary-0 1/1 Running 0 86m pod/x10-240-0-12.veritas .internal 1/1 Running 0 68m pod/x10-240-0-13.veritas .internal 2/2 Running 0 64m pod/x10-240-0-14.veritas .internal 2/2 Running 0 61m pod/x10-240-0-15.veritas .internal 2/2 Running 0 59m NAME TYPE CLUSTER-IP PORT(S) AGE service/dedupe1- uss-controller ClusterIP 10.1.109.118 10100/TCP 68m service/dedupe1- uss-mds ClusterIP None 2379/TCP,2380/TCP 75m service/dedupe1- uss-mds-client ClusterIP 10.1.5.208 2379/TCP 75m service/media1- media-0 LoadBalancer 10.1.121.115 13782:30648/TCP,
1556:30248/TCP 54m service/ environment- sample-primary LoadBalancer 10.1.206.39 13781:30246/TCP,
13782:30498/TCP,
1556:31872/TCP,
443:30049/TCP,
8443:32032/TCP,
22:31511/TCP 87m service/ x10-240-0-12 -veritas-internal LoadBalancer 10.1.44.188 10082:31199/TCP 68m service/ x10-240-0-13 -veritas-internal LoadBalancer 10.1.21.176 10082:32439/TCP, 68m service/ x10-240-0-14 10102:30284/TCP -veritas-internal LoadBalancer 10.1.25.99 10082:31810/TCP, 68m service/ x10-240-0-15 10102:31755/TCP -veritas-internal LoadBalancer 10.1.185.135 10082:31664/TCP, 68m 10102:31811/TCP NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/dedupe1 -uss-controller 1/1 1 1 68m NAME DESIRED CURRENT READY AGE replicaset.apps/dedupe1-uss -controller-79d554f8cc 1 1 1 68m NAME READY AGE statefulset.apps/media1-media 1/1 53m statefulset.apps/environment -sample-primary 1/1 86m NAME TAG AGE STATUS primaryserver.netbackup .veritas.com/environment -sample 10.1 88m Success NAME TAG AGE PRIMARY SERVER STATUS mediaserver.netbackup. x10-240-0-10 veritas.com/media1 10.1 54m .veritas.internal Success NAME AGE TAG SIZE READY msdpscaleout.msdp. veritas.com/dedupe1 75m 17.0 4 4 NAME READY AGE STATUS environment.netbackup. veritas.com/ environment-sample 3/3 88m Success
An environment is deployed successfully if all pods and environment CR display status as "Success".