Decoupling of NetBackup web services from primary server
From Cloud Scale Technology version 10.5 and later, the NetBackup web services are decoupled (dissociated) from the primary server so that it can be containerized and executed independently as a standalone service pod in a Kubernetes cluster. All the other APIs and web UI behavior remains the same within the NetBackup cluster. The NetBackup web applications and the supporting infrastructure is deployed to /usr/openv/wmc/ as part of a new Docker container image called netbackup-ws-app. This image (netbackup-ws-app) is deployed in a new separate Kubernetes pod within the NetBackup cluster.
The deployment of the web services pod is orchestrated using NetBackup operator framework which manages all of the NetBackup Kubernetes deployment artifacts within a Kubernetes cloud deployment.
Components involved in the decoupled NetBackup web services architecture:
: The
nbwsinitcontainer is the first file to execute during the deployment. It performs the environmental setup work described in the deployment section below. When thenbwsinitcontainer stops, the rest of the containers start simultaneously and thenbwsinitcontainer dissociates.: Components of volume mounts supports
vnetproxy sidecar and thenbwsapppod mounts the/mnt/sock-data persistentvolume where the proxy files are used to exchange within sockets.: This volume represents the NetBackup primary catalogue data log.
: Components of
Kubernetes secretsis mounted and used by thenbwsinitcontainer to establish trust with thenbatdpod in order to get the CA certificate as prerequisite to creating the web services certificates and trust stores.: For Cloud Scale Technology deployment, the NetBackup web service is unable to make localhost connections. It needs to connect remotely on the primary pod and the decoupled
nbatdpod. For these remote service connections, it now needs to use the secure communication infrastructure provided by thevnetdinbound and outbound proxies.: The
nbwsappincludes thenbhousekeepingsidecar container in its deployment to perform scheduled housekeeping tasks such as log file clean up, rotation and telemetry collection.: The
nbwsapppod includes thefluentbitsidecar container in its deployment to perform regular log collection from the source container(s) and combine in a separatefluentbit-collectorpod.