NetBackup 11.x is Cohesity’s enterprise backup and recovery platform.
One primary server runs the catalog, the scheduler, the web UI and a certificate authority. Media servers move data to deduplicated storageand clients, hypervisors and databases are protected from a single domain
In the next few blogs, we will try to understand the operation of Cohesity Netbackup 11X and do a full deployment and do a real deep dive.
Here are the terminologies
- OpsCenter was the dashboard for NetBackup masters ealrier and looks It’s on its way out.
- IT Analytics is the reporting and capacity tool , used for chargeback, a storage growth forecast, or a single report across NetBackup plus other backup products. This was known as Aptare before.
- Insights Console / Smart Meter – the licensing portal.
- Alta View is the Veritas cloud management modern control plane for NetBackup, manage many domains from one place, plus the cyber-recovery features which is the replacement for OpsCenter
- Helios is the Cohesity-side control plane used for managing Cohesity products and now being merged with Alta View.
- Flex Appliances – These are the NetBackup appliances we had earlier such as the 5200/5300 ones
- Cohesity Data Cloud for NetBackup: NetBackup’s media server role runs on the Cohesity platform instead of on separate media servers and appliances. Your primary server, policies and catalog stay the same.
Types of Netbackup Deployments
NetBackup can be deployed as one domain across sites with optimised duplication, or as separate domains linked by A.I.R.
Single NetBackup Domain
This is the traditional 3-tier (primary, media, client) architecture where backups are stored locally into a de-dupe pool and there could be a SLP moving copies offsite to a location into another de-dupe pool. Here the catalogs are stored on one site however data it backups up can be replicated elsewhere so the backup master at primary controls it. The issue with this is if the primary backup server is attacked that could also take down the catalog with it.

A.I.R Auto Image Replication
Here NetBackup is built into two separate NBU domains. The separate-domain design, plus an isolated vault, is becoming the standard because of ransomware. The catlogs from one site are propogated to other so

Types of Backups
- Full backup – Backups everything on system
- Differential incremental- backs up files changed since the last backup of any type, full or incremental. It’s daily only if the schedule runs daily.
- Cumulative Incremental Backup – Backups up everything changed from last full so it’s a snowball effect and backups grow but restore is quicker as just the last backup to restore…
- Synthentic Backups – A full backup bult on the storage by combining all incremental.
NetBackup Policy Selection
A rough idea of what’s inside a NetBackup policy configuration.
| Workload | NetBackup policy type |
|---|---|
| Unix / Linux files | Standard |
| Windows files | MS-Windows |
| VMware VMs | VMware |
| Hyper-V VMs | Hyper-V |
| NAS through the filer (NetApp, Isilon) | NDMP |
| NAS through file shares, the newer and faster method | NAS-Data-Protection (dynamic NAS) |
| Oracle | Oracle |
| SQL Server | MS-SQL-Server |
| DB2 | DB2 |
| Hadoop / HBase | BigData |
| PostgreSQL, MySQL and other script-driven databases | DataStore, though check your version (see below) |
| SAP | SAP |
| Exchange | MS-Exchange-Server |
| SharePoint | MS-SharePoint |
| The NetBackup catalog itself | NBU-Catalog |
| Block-level backup of very large file systems | FlashBackup / FlashBackup-Windows |
Storage Units in Netbackup
Storage Units as far as I can haven’t changed much since v7X but the Pure disk element has now been folded into MSDP (Media Server Deduplication Pool)
Here are the storage units
- Basic Disk – A plain folder or volume on a media server, with no deduplication
- Advanced Disk – Unlocks grouping of multiple disks into disk pool and Storage lifecycle policies
- MSDP – This is the original pure disk engine now folded into a de-dupe pool
- OST – for connecting Data domains, Hpe devices etc
- Tape library – for backup tapes
Storage life cycle policy SLP
SLP’s have exited as far as v6 and this needs Advanced disk / TB licenses to be activated before we can use it.
Netbackup/ Flex Applinces
Rather than using block array as backup target, Cohesity now sells Veritas media servers such as these once’s that are a plug and play media server
- Classic appliances (52xx/53xx): standalone boxes. To grow, you either add disk shelves to the box (scale up) or buy another appliance and manage it separately.
- Flex (5150, 5260/5360, 5270/5372): also, standalone boxes, one appliance running several containers. Some Flex models can be paired for high availability, but that’s failover, not a scale-out cluster. These are scale-out cluster and capacity and performance grow by adding nodes, and it’s managed as a single unit.

NetBackup Ports
These are the ports that needs to be opened on the firewall and OS . Source for 1556, 13724, 10102 and 10082: NetBackup 11.0 client ports.

The Lab Topology
I’ve constructed this lab on Proxmox so here are the hardware requirements
| Host | Role | vCPU / RAM | OS disk | Data disk |
|---|---|---|---|---|
| nbu-primary | Primary server, NetBackup CA, web UI | 12 / 60 GB | 100 GB | 100 GB catalog |
| nbu-media01 | Media server, MSDP | 8 / 16 GB | 80 GB | 500 GB MSDP01 |
| nbu-client01 | Windows client | 2 / 4 GB | 60 GB | 20 GB test data |
| nbu-media02 | Media server, MSDP | 8 / 16 GB | 80 GB | 500 GB MSDP02 |
NetBackup Deployment Checklist
I hit a lot of issues with this deployment so here is the short summary of it
Probably the most that are important are here
- Ensure the Primary server is scoped correctly, the webserver on it runs hot when it has analytics enabled on it
- All hosts must be joined to the AD domain before NetBackup is installed.
- Create admin accounts and groups before installing roles, then sign out or reboot so the logon token picks them up.
- The web service account and group must exist on the primary server before installation, with Log on as a service granted.
- Ensure NetBackup ports are opened
- NetBackup’s own services talk to each other through localhost:1556 (PBX). If you untick IPv6 on the NIC before installing, NetBackup sets itself up IPv4-only (IP_ADDRESS_FAMILY = AF_INET) and listens on 0.0.0.0:1556. Windows, meanwhile, still sends localhost to ::1, where nothing is listening. Some calls fall back to IPv4 and work, and others don’t. In my lab the web service couldn’t reach nbsl, so the MSDP storage server wizard spun forever
- Install the Netbackup software as an admin user
Create a new Organisational Unit for NetBackup
Import-Module ActiveDirectory
$base = (Get-ADDomain).DistinguishedName
New-ADOrganizationalUnit -Name NetBackup -Path $base
$ou = "OU=NetBackup,$base"
# Groups: who administers and who operates NetBackup
'GG-NBU-Admins','GG-NBU-Operators' | % { New-ADGroup $_ -GroupScope Global -GroupCategory Security -Path $ou }
# Named admin account for the backup team (installs and manages NetBackup)
New-ADUser adm-ash -Path $ou -Enabled $true -AccountPassword (Read-Host 'adm-ash password' -AsSecureString)
Add-ADGroupMember GG-NBU-Admins -Members adm-ash

Grant Rights on the NetBackup Servers and Clients
Add-LocalGroupMember -Group Administrators -Member 'NBU\GG-NBU-Admins' 
Create a local web service account (before install)
This is quite an important one, you could actually create this is as domain account, but I still prefer this running as local and the admin guide says it too to use AD based accounts. This account should be set to password no expire.
$p = Read-Host 'nbwebsvc password' -AsSecureString
New-LocalUser -Name nbwebsvc -Password $p -PasswordNeverExpires -Description 'NetBackup web service'
New-LocalGroup -Name nbwebgrp
Add-LocalGroupMember -Group nbwebgrp -Member nbwebsvcGive the account nbu-primary only, grant nbu\svc-nbu-web Log on as a service:
secpol.msc → Local Policies → User Rights Assignment. Then sign out and sign back in as LAB\adm-ash.

In the lab, just turn off Windows Updates to save bit of compute
---------------------------------------------------------------------
# 1. ALL SERVERS — before installing NetBackup
# ---------------------------------------------------------------------
# Windows Update off — LAB ONLY (production patches on a schedule)
New-Item 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU' -Force | Out-Null
Set-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU' -Name NoAutoUpdate -Value 1 -Type DWord
Stop-Service wuauserv -ForceEnable Ping and RDP
---------------------------------------------------------------------
# 1. ALL SERVERS and Clients — before installing NetBackup
# ---------------------------------------------------------------------
# Ping and RDP
New-NetFirewallRule -DisplayName 'Allow ICMPv4' -Direction Inbound -Protocol ICMPv4 -IcmpType 8 -Action Allow
Set-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0
Enable-NetFirewallRule -DisplayGroup 'Remote Desktop'
Ensure IPV6 stay enabled
---------------------------------------------------------------------
# 1. ALL SERVERS — before installing NetBackup
# IPv6 stays ON, IPv4 preferred — never untick IPv6 on the NIC
Enable-NetAdapterBinding -Name * -ComponentID ms_tcpip6
New-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters' -Name DisabledComponents -PropertyType DWord -Value 0x20 -Force
Restart-Computer # DisabledComponents only applies after a rebootEnsure AV exclusions are added to all Netbackup Paths
# Defender exclusions (real-time protection stays on)
# F:\ = catalog on the primary, MSDP storage (F:\msdp) on media servers
Add-MpPreference -ExclusionPath 'C:\Program Files\Cohesity NetBackup','C:\Program Files\Veritas','F:\','C:\ProgramData\boost_interprocess'
Add-MpPreference -ExclusionProcess 'bpbkar32.exe','bpcd.exe','vnetd.exe','pbx_exchange.exe','bpbrm.exe','bptm.exe','bpdm.exe','bprd.exe','bpdbm.exe','bpjobd.exe','nbemm.exe','nbpem.exe','nbjm.exe','nbrb.exe','nbatd.exe','nbazd.exe','nbsl.exe','nbstserv.exe','nbwmc.exe','java.exe','postgres.exe','pgbouncer.exe','pg_ctl.exe','spoold.exe','spad.exe','mtstrmd.exe','pdregister.exe','nbaudit.exe','nbevtmgr.exe','nbim.exe','nbkms.exe','nbvault.exe','vmd.exe','ltid.exe'
I’ll turn off Realtime Monitoring as well in Lab
# LAB-ONLY ALTERNATIVE — use INSTEAD of the exclusions, never both:
# Set-MpPreference -DisableRealtimeMonitoring $true
# NetBackup admins into local Administrators (after the domain join)
Add-LocalGroupMember -Group Administrators -Member 'NBU\GG-NBU-Admins'
Restart-ComputerEnsure this reboot is done before you install and log back in.
# NetBackup admins into local Administrators (after the domain join)
Add-LocalGroupMember -Group Administrators -Member 'NBU\GG-NBU-Admins'
Restart-ComputerOnce the reboot is done, will now start all our firewall rules on Master/Media Servers
# . FIREWALL — one rule per role on media /master server
# ---------------------------------------------------------------------
# nbu-primary: 1556 PBX, 13724 vnetd, 443 web UI/web service, 13781 messaging broker, GRT 7394 if nededed
New-NetFirewallRule -DisplayName 'NetBackup' -Direction Inbound -Protocol TCP -LocalPort 1556,13724,443,13781,7394 -Action Allow
# nbu-media01/02/03: 1556 PBX, 13724 vnetd, 10082 MSDP spoold, 10102 MSDP spad
New-NetFirewallRule -DisplayName 'NetBackup' -Direction Inbound -Protocol TCP -LocalPort 1556,13724,10082,10102 -Action Allow
# edia servers: GRT prerequisites (NFS components installed, Windows NFS server service off) + nbfsd log folder
Install-WindowsFeature FS-FileServer, FS-NFS-Service
Set-Service NfsService -StartupType Disabled; Stop-Service NfsService -ErrorAction SilentlyContinue
New-Item -ItemType Directory "C:\Program Files\Cohesity NetBackup\NetBackup\logs\nbfsd" -ForceFor GRT level functionality, we ensure we have NFS Server Installed and Service in Disabled State.
# . FIREWALL — GRT prerequisites (Only Media Server)
# ---------------------------------------------------------------------
# Media servers: GRT prerequisites (NFS components installed, Windows NFS server service off) + nbfsd log folder
Install-WindowsFeature FS-FileServer, FS-NFS-Service
Set-Service NfsService -StartupType Disabled; Stop-Service NfsService -ErrorAction SilentlyContinue
New-Item -ItemType Directory "C:\Program Files\Cohesity NetBackup\NetBackup\logs\nbfsd" -Force
New-NetFirewallRule -DisplayName "NetBackup nbfsd" -Direction Inbound -Protocol TCP -LocalPort 7394 -Action AllowOnce the reboot is done, add the firewall rule to Clients
# FIREWALL — one rule per role on Windows clients
# ---------------------------------------------------------------------
# nbu-client01 (and any Windows client): 1556 PBX, 13724 vnetd + remote push prerequisites
New-NetFirewallRule -DisplayName 'NetBackup' -Direction Inbound -Protocol TCP -LocalPort 1556,13724 -Action Allow
Set-Service RemoteRegistry -StartupType Automatic; Start-Service RemoteRegistry
Enable-NetFirewallRule -DisplayGroup 'File and Printer Sharing'
Enable-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)'
Enable-NetFirewallRule -DisplayGroup 'Remote Service Management'
Before MSDP is configured this should be applied. It’s the setting that decides which IP protocols NetBackup uses for its connections which is covered in next blog
# 5. ALL SERVERS — straight after installing, before MSDP
Set-Content -Path C:\af.txt -Encoding ascii -Value "IP_ADDRESS_FAMILY = AF_UNSPEC"
bpsetconfig C:\af.txt
bpgetconfig | Select-String 'IP_ADDRESS_FAMILY' # must say AF_UNSPEC
bpdown -f -v; bpup -f -vThat’s all the prerequisite for Netbackup install so let’s kick off the deployment.
