We will now start the deployment of NetBackup 11.X, and I’ll skip irrelevant sections in this just to stay focussed.
Install NetBackup Primary Server
Primary server runs the catalog, the scheduler, the web UI and a certificate authority and can also act as a media server if we wanted to.

Choose Custom settings if you wish to move the default installation from C:\

Choose Netbackup Primary Server, this will run on a 60 day eval

On the lab, you could actually turn this off as it may save bit of compute

Untick this option as well

Admin Consoles are actually no longer necessary, but you may choose to install it if needed

Go with local or AD account here and ensure this AD group is added to a member of Administrators

Go with local or AD account here, the admin guides point in the direction of having these set as AD accounts whilst many blogs suggest leaving it as local for web server account

Give the netbackup server name here

Click Install

Install takes around 20 mins

Reboot the machine before you open the web UI

Post reboot, login as the AD user you installed Netbackup

If you installed admin console, you can login via that too, but I think the UI is bit more fluid now

Grant the AD admin group access: in the web UI go to Security → RBAC → Add

give NBU\GG-NBU-Admins the Administrator role

Log out and log back in to the WebUI and add the path variables
ALL SERVERS — after install
# ---------------------------------------------------------------------
# PATH (open a new window afterwards)
$nb = 'C:\Program Files\Cohesity NetBackup\NetBackup\bin'
$path = [Environment]::GetEnvironmentVariable('Path','Machine')
if ($path -notmatch 'admincmd') { [Environment]::SetEnvironmentVariable('Path', "$path;$nb;$nb\admincmd;C:\Program Files\Cohesity NetBackup\Volmgr\bin;C:\Program Files\Cohesity NetBackup\pdde", 'Machine') }
$env:Path = [Environment]::GetEnvironmentVariable('Path','Machine')
A lot of NetBackup’s internal traffic goes to localhost . On Windows, localhost can resolve to the IPv6 address ::1 before 127.0.0.1. With AF_INET, NetBackup only listens on IPv4. So a component connects to ::1, finds nothing listening, and fails and you could get caught in MSDP configuration
| Value | Meaning |
|---|---|
AF_INET | IPv4 only. NetBackup listens on, and connects over, IPv4 only |
AF_UNSPEC | Both IPv4 and IPv6. NetBackup listens on both and uses whichever a name resolves to |
If you haven’t set it
Set-Content -Path C:\af.txt -Encoding ascii -Value "IP_ADDRESS_FAMILY = AF_UNSPEC"
nbsetconfig C:\af.txt
nbgetconfig | Select-String 'IP_ADDRESS_FAMILY'Ensure this is checked as well before we add the media server
# Checks — all must pass BEFORE configuring MSDP
reg query HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents # 0x20
# True
Get-NetAdapterBinding -ComponentID ms_tcpip6 | select Name,Enabled
# AF_UNSPEC
bpgetconfig | Select-String 'IP_ADDRESS_FAMILY'
# replies from 127.0.0.1
ping localhost -n 1 
Click on Install Netbackup Media Server
Media servers move data to deduplicated storage; the install process is same but pick Media Server

Choose the primary server here

For this to pass through, ports 1556,13724,443 must be open on the firewall and on the OS as we did in last blog.

Since NetBackup 8.1, every host talks to the others over TLS, and every host carries a certificate issued by the primary server, which acts as the domain’s own certificate authority. So when you install a client or a media server, it has to ask the primary for a certificate.

The host has exchanged the cert, and trust has to work in both directions:

Click Install and wait for 20 mins

Post Reboot, we can see both our servers are now ready

Auth Tokens
Tokens are short lived passwords that are meant as a security feature for every host talking to NetBackup to see if its validated and trusted. So, when you install a client or a media server, it has to ask the primary for a certificate.
Go to Security → Global security settings → Secure communication
- Very high: a token is always required.
- High (default): a token is required only if the primary doesn’t already know the host, for example because it isn’t yet in a policy or registered as a media server…

In production, keep tokens to one or a few uses and a short expiry, and leave the level at High or above. In a ransomware attack, a rogue host joining your backup domain is exactly what you don’t want so here, the token expires each day

To add a token, Go to Security → Tokens → Give token a name and give details such as its validity

Token is generated

Configure a NetBackup Client
For a client to be added to NetBackup it has to have the client packages on it. The installation process is similar to our primary and media server but pick the Client Software
Ensure that you have completed the prerequisite section else you will get “RPC server unavailable” means the push from the primary can’t reach Windows’ remote management on nbu-client01. That’s blocked by default on Server 2025.

Register all the servers – Primary, Media Servers etc in here. If anything is missed here, it will need to be added later into the host properties else you get socket read errors

It has to ask the primary for a certificate so click Next here

Provide the token value here

Click Install and Reboot the VM

If you missed adding a media server or if a new media server joins later, you can go to the client properties and add it as shown

A NetBackup client can also be installed directly from the primary server. Just run the installer file on the master server

Click Install

After few minutes, the new client will be seen in our host properties section

So that’s the NetBackup primary, master, client done so let’s ramp up to storage.
