Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  3. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  5. Section III. Monitoring and Management
  7. Managing the Load Balancer service
  9. Steps for upgrading Cloud Scale from multiple media load balancer to none
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Steps for upgrading Cloud Scale from multiple media load balancer to none

For version 10.5 and later, there is no need of load balancers for media servers. this section describes the post upgrade procedure to be performed for converting from multiple load balancers to none.

Steps to convert from multiple load balancers to none

  1. After successfully upgrading the Cloud Scale Technology to 10.5 or later, all the load balancers associated with the media server are upgraded to version 10.5 or later.
  2. Deactivate the policy and the schedules. Wait for the running jobs to complete.
  3. Add the media2 object in the mediaServers without te network load balancers.
  4. Execute the following command:

    helm get values cloudscale -n <namespace>

    Note the details of the mediaserver section.

    Then, add another mediaserver object with a different name, but with identical details as the first one:

    helm upgrade cloudscale VRTSk8s-netbackup-11.2.0.2/helm/cloudscale-11.2.0.2.tgz -n <namespace> --reuse-values \
--set environment.mediaServers[0].name=media1 --set environment.mediaServers[0].nodeSelector.labelKey=<original value> \
--set environment.mediaServers[0].nodeSelector.labelValue=<original value> --set environment.mediaServers[0].replicas=<original value> \
--set environment.mediaServers[0].minimumReplicas=<original value> --set environment.mediaServers[0].storage.data.capacity=<original value> \
--set environment.mediaServers[0].tag=11.2 --set environment.mediaServers[0].storage.log.capacity=<original value> \
--set environment.mediaServers[0].storage.data.storageClassName=<sc-name> \
--set environment.mediaServers[0].storage.log.storageClassName=<sc-name> \
--set environment.mediaServers[1].name=media2 --set environment.mediaServers[1].nodeSelector.labelKey=agentpool \
--set environment.mediaServers[1].nodeSelector.labelValue=mediapool --set environment.mediaServers[1].replicas=2 \
--set environment.mediaServers[1].minimumReplicas=2 --set environment.mediaServers[1].storage.data.capacity=60Gi \
--set environment.mediaServers[1].storage.data.storageClassName=<sc-name> \
--set environment.mediaServers[1].tag=11.2 --set environment.mediaServers[1].storage.log.capacity=10Gi \
--set environment.mediaServers[1].storage.log.storageClassName=<sc-name>
  5. Once the media2 is successfully added, check the status of the media servers, media2 pods and services. Wait for the all the Pods to come up with media server status as success. 
    Get mediaservers
Kubectl get mediaserver -n <namespace>
media1 11.0.x-xx 79m nbux-xx-xxx-xx-xxx.vxindia.cohesity.com Success
media2 11.0.x-xx 79m nbux-xx-xxx-xx-xxx.vxindia.cohesity.com Success
  6. Ensure that all the user settings that were present for media1 pods are added manually to media2 pods also. For example, LogLevel, FIPS Mode, DNAT and so on.
  7. Pause both the mediaserver objects using the following command:

    helm upgrade cloudscale VRTSk8s-netbackup-11.2/helm/cloudscale-11.2.tgz -n <namespace> --reuse-values \

    --set environment.mediaServers[0].name=media1 --set environment.mediaServers[0].nodeSelector.labelKey=<original value> \

    --set environment.mediaServers[0].nodeSelector.labelValue=<original value>

    --set environment.mediaServers[0].replicas=<original value> \

    --set environment.mediaServers[0].minimumReplicas=<original value>

    --set environment.mediaServers[0].storage.data.capacity=<original value> \

    --set environment.mediaServers[0].storage.data.storageClassName=<sc-name> \

    --set environment.mediaServers[0].paused=true \

    --set environment.mediaServers[0].tag=11.2

    --set environment.mediaServers[0].storage.log.capacity=<original value> \

    --set environment.mediaServers[0].storage.log.storageClassName=<sc-name> \

    --set environment.mediaServers[1].name=media2

    --set environment.mediaServers[1].nodeSelector.labelKey=<original value> \

    --set environment.mediaServers[1].nodeSelector.labelValue=mediapool

    --set environment.mediaServers[1].replicas=<original value> \

    --set environment.mediaServers[1].minimumReplicas=<original value>

    --set environment.mediaServers[1].storage.data.capacity=<original value> \

    --set environment.mediaServers[1].storage.data.storageClassName=<sc-name> \

    --set environment.mediaServers[1].tag=11.2

    --set environment.mediaServers[1].storage.log.capacity=<original value> \

    --set environment.mediaServers[1].storage.log.storageClassName=<sc-name> \

    --set environment.mediaServers[1].paused=true

  8. Navigate to NetBackup web UI and select Storage. On the Disk Storage, select the Storage server. There are multiple entries for media server with and without the load balancers.
  9. Delete the entry for media1. You have to remove all the entries of media servers containing FQDN.
  10. Remove the first mediaserver object from the environment using the following command (change the index first mediaServer to index 0 mediaServer):

    helm upgrade cloudscale VRTSk8s-netbackup-11.2/helm/cloudscale-11.2.tgz -n <namespace> --reuse-values \

    --set environment.mediaServers[0].name=media2

    --set environment.mediaServers[0].nodeSelector.labelKey=agentpool \

    --set environment.mediaServers[0].nodeSelector.labelValue=mediapool

    --set environment.mediaServers[0].replicas=2 \

    --set environment.mediaServers[0].minimumReplicas=2

    --set environment.mediaServers[0].storage.data.capacity=60Gi \

    --set environment.mediaServers[0].storage.data.storageClassName=<sc-name> \

    --set environment.mediaServers[0].tag=11.2

    --set environment.mediaServers[0].storage.log.capacity=10Gi \

    --set environment.mediaServers[0].storage.log.storageClassName=<sc-name> \

    --set environment.mediaServers[0].paused=true

  11. Check the bp.conf file.
  12. Delete the media1 entries (FQDN entries of media1) from the bp.conf file. Exec into the primary pod and open /usr/openv/netbackup/bp.conf and delete the entries and save the file.
  13. Resume the media2 using the following command:

    helm upgrade cloudscale VRTSk8s-netbackup-11.2/helm/cloudscale-11.2.tgz -n <namespace> --reuse-values \

    --set environment.mediaServers[0].name=media2

    --set environment.mediaServers[0].nodeSelector.labelKey=agentpool \ --set environment.mediaServers[0].nodeSelector.labelValue=mediapool

    --set environment.mediaServers[0].replicas=2 \

    --set environment.mediaServers[0].minimumReplicas=2

    --set environment.mediaServers[0].storage.data.capacity=60Gi \

    --set environment.mediaServers[0].storage.data.storageClassName=<sc-name> \

    --set environment.mediaServers[0].tag=11.2

    --set environment.mediaServers[0].storage.log.capacity=10Gi \

    --set environment.mediaServers[0].storage.log.storageClassName=<sc-name> \

    --set environment.mediaServers[0].paused=false

  14. Note the minimum replica value of media2. Change the minimum replica value using the following command:

    kubectl get pvc -n nbu | grep -i data-media1-media | wc -l 2

    Wait for the pod to be in running state and the status of the media server must be displayed as success.

    Note:

    Although minimum replica value of media server = 0 is supported in cloud scale, for PSF workloads (for example, MongoDB) at least one elastic media server must be running (that is, minimum replica of media server >= 1). The name of media server can be obtained from Host mappings

    For elastic media server, this name is same as the media server pods.

  15. Login into the primary server Pod and move the database from previous media server to new media server using the following command:

    bpmedia -movedb -allvolumes -oldserver <old mediaserver name> -newserver <new mediaserver name>

    example: bpmedia -movedb -allvolumes -oldserver nbux-xx-xxx-xx-xxx.vxindia.cohesity.com -newserver media2-media-0

    Repeat this step for other media servers.

  16. Using the command delete the alias or hostname and repeat this for each media server:

    nbemmcmd -deletehost -machinename <old mediaserver name> -machinetype media

    example: nbemmcmd -deletehost -machinename nbux-xx-xxx-xx-xxx.vxindia.cohesity.com -machinetype media

  17. Modify the minimum replica value to the original value noted in step 13.
  18. Add the entry of the previous media server object alias to the new media server in the Host mappings.

    Note:

    When migrating from multiple load balancers to no load balancers in NetBackup version 11.0 or later, delete the stale host mapping entries as follows:

    Navigate to, NetBackup Web UI ==> Security==> Host mappings ==> Select the Actions menu next to the primary host name ==> Manage mappings ==> Delete the old load balancer media name mapping and click on Save.

  19. Restore the backup and check the status in the Activity monitor and to the location where the backup is restored.

Feedback

Was this page helpful?
Previous

Opening the ports from the Load Balancer service

Next

Managing PostrgreSQL DBaaS

Feedback

Was this page helpful?