Part 5 – Cyber Recovery in Practice with Cohesity NetBackup 11.X

The Primary domain controller should be backed up regularly and so should be the Global Catalog as it may hold additional roles that might otherwise not be replicated across other domain controllers.

A system state backup involves all the components of an Active Directory such as SyVol, Group Policies, DNS info etc and with NetBackup GRT it gives us the ability to restore granular objects within an Active Directory tree.

To use GRT, NFS Server should be installed on all NetBackup Media Servers

NetBackup uses Granular Recovery Technology (GRT) and NFS to recover the individual objects that reside within a database backup image such as user accounts, emails, SharePoint databases etc. It uses its own NBFSD (NetBackup File System Daemon on port 7394) on the media server to present a backup image as a read-only file system over the NFS so another host can open it and mount like a drive and users can pick what they want to restore.

NetBackup does not support granular restores of Group Policy Objects.

Media Server Configuration

From the Manage menu > Server Roles -> Select Server for NFS

Click Install

Once NFS is installed on Media server, disable it

To use GRT functionality, NFS Client role should be enabled on the media server.

Disabling the Client for NFS on the media server — NetBackup 11.2 | Cohesity Documentation

Active Directory Server

Create a new user for grt backups and add it as domain admin

The NetBackup Client Service must be configured to log on as an account with domain admin privileges.

Install NFS Client Service. From the Manage menu > Server Roles -> click Client for NFS. Click Next.

Ensure NFS Client service has started

Disable portmapper service on Media Servers

Port 111 is the standard portmapper port. NFS clients first ask a portmapper (port 111) which port the NFS service is listening on. During a GRT backup or restore, NetBackup’s nbfsd brings its own NFS service and port registration. If another portmapper is already running on the media server, it holds port 111, and nbfsd can’t register. That’s the same “cannot start nbfsd” failure

On the media serve check if portmapper service is stopped

Get-Service | Where-Object { $_.DisplayName -match 'Portmap|Server for NFS' } | Select Name, DisplayName, Status, StartType

Let’s also run netstat to verify and here 111 is still listening which needs to be disabled

netstat -ano | Select-String ':111 '

Portmap is a kernel so this needs to be disabled from registry. (4 = disabled, 3 = manual, which is what it is now)

Change from 3 =2, The Start value for a driver means:

  • 0 – Boot
  • 1 – System
  • 2 – Automatic
  • 3 – Manual ( Demand)
  • 4 – Disabled
Get-CimInstance Win32_SystemDriver -Filter "Name='Portmap'"

Create AD Backup Policy

To back up the Active Directory, select GRT

Under Selection List we used to just pick System State. On a domain controller, SYSVOL is already part of the System State. Windows includes it automatically through the DFS Replication (DFSR) VSS writer, so System State:\ captures the registry, boot files, COM+ and the rest but System State:\ is a deprecated directive in modern versions of NetBackup, which no longer resolves it properly and causes backups to fail with Status 71. NetBackup requires Shadow Copy Components:\ to back up Active Directory and Windows system state data.

Durning this GRT backup, the media server starts nbfsd, which listens on TCP 7394. The DC’s Client for NFS connects to the media server on 7394 and mounts the backup image so let’s kick off an AD backup

When the backup is running, we can test via Test-NetConnection … -Port 7394 result from the DC, which only succeeds while a GRT job

AD Backups are taken.

Troubleshooting Backups

A quick backup via Windows Native Backup to check if VSS writers are holding good.

wbadmin start backup -backuptarget:e: -systemstate

If the NetBackup client service fails to restart, the indication could be that its missing domain admin privilages.

 C:\Users\Administrator> Get-WinEvent -LogName System -MaxEvents 30 | Where-Object { $_.Message -match 'NetBackup' } | Select TimeCreated, Id, Message

TimeCreated             Id Message
-----------             -- -------
11/15/2026 2:00:50 PM 7036 The NetBackup Privileged Access Service service entered the stopped state.
11/15/2026 2:00:49 PM 7000 The NetBackup Client Service service failed to start due to the following error: ...
11/15/2026 2:00:49 PM 7009 A timeout was reached (30000 milliseconds) while waiting for the NetBackup Client Service...
11/15/2026 2:00:49 PM 7036 The NetBackup Privileged Access Service service entered the running state.
11/15/2026 1:59:58 PM 7000 The NetBackup Client Service service failed to start due to the following error: ...
11/15/2026 1:59:58 PM 7009 A timeout was reached (30000 milliseconds) while waiting for the NetBackup Client Service...
11/15/2026 1:59:55 PM 7036 The NetBackup Privileged Access Service service entered the stopped state.
11/15/2026 1:59:54 PM 7036 The NetBackup Privileged Access Service service entered the running state.
11/15/2026 1:58:10 PM 7036 The NetBackup Privileged Access Service service entered the stopped state.
11/15/2026 1:58:09 PM 7000 The NetBackup Client Service service failed to start due to the following error: ...
11/15/2026 1:58:09 PM 7009 A timeout was reached (30000 milliseconds) while waiting for the NetBackup Client Service...
11/15/2026 1:58:09 PM 7036 The NetBackup Privileged Access Service service entered the running state.
11/15/2026 1:54:39 PM 7036 The NetBackup Privileged Access Service service entered the stopped state.
11/15/2026 1:54:38 PM 7000 The NetBackup Client Service service failed to start due to the following error: ...

This shows our nbfsd’s TCP port 7394 is likely not open

Connection test proves nbfsd’s not open

PS C:\Program Files\Cohesity NetBackup\NetBackup\logs> Test-NetConnection nbu-media01.nbu.local -Port 7394
WARNING: TCP connect to (172.16.11.171 : 7394) failed


ComputerName           : nbu-media01.nbu.local
RemoteAddress          : 172.16.11.171
RemotePort             : 7394
InterfaceAlias         : Ethernet
SourceAddress          : 172.16.11.6
PingSucceeded          : True
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded       : False


How it works during a GRT restore

  1. You ask to restore one AD user.
  2. bpbrm starts nbfsd on the media server, on demand. It isn’t always running, which is why the error said “cannot start nbfsd”.
  3. nbfsd exposes the backup image from MSDP as an NFS share on TCP 7394.
  4. The DC mounts it with Client for NFS, and NetBackup’s agent reads just that user’s object out of the AD database inside the image, then writes it back to the live AD.
  5. When the job finishes, the share is unmounted and nbfsd stops.

You can do this restore via the B&R on the AD VM itself or it can be done via from the master server

Under Recovery > Choose Source Client and Destination Client to Restore Data to

Navigate the tree structure to the item we wish to restore

Restore to default location

Click Start Recovery

The restored Item is back in our AD

References

Configuring a different network port for NBFSD — NetBackup 8.1.2 | Cohesity Documentation

About installing and configuring Network File System (NFS) for Active Directory Granular Recovery — NetBackup 11.2 | Cohesity Documentation

System requirements for Active Directory granular NetBackup backups and recovery — NetBackup 11.0 | Cohesity Documentation

Active Directory granular backups and recovery — NetBackup 11.0 | Cohesity Documentation

(Visited 3 times, 1 visits today)

By Ash Thomas

Ash Thomas is a seasoned IT professional with extensive experience as a technical expert, complemented by a keen interest in blockchain technology.