Verification request

[JHeaton]

NBU - 7.0 Capacity

OS - Server 2K8 R2

In order to backup my Active Directory metabase, is it necessary to implement NFS on the Domain Controller and the media server?

[Will_Restore]

About installing and configuring Network File System

(NFS) for Active Directory Granular Recovery

NetBackup Granular Recovery leverages Network File System, or NFS, to read

individual objects from a database backup image. Specifically, the NetBackup

client uses NFS to extract data from the backup image on the NetBackup media

server. The NetBackup client uses “Client for NFS” to mount and access a mapped

drive that is connected to the NetBackup media server. The NetBackup media

server handles the I/O requests from the client through NBFSD.

NBFSD is the NetBackup File System (NBFS) service that runs on the media server.

NBFSD makes a NetBackup backup image appear as a file system folder to the

NetBackup client over a secure connection.

Network File System, or NFS, is a widely recognized, open standard for client and

server file access over a network. It allows clients to access files on dissimilar

servers through a shared TCP/IP network. NFS is typically bundled with the host

operating system. NetBackup uses Granular Recovery Technology (GRT) and NFS

to recover the individual objects that reside within a database backup image, such

as:

■ A user account from an Active Directory database backup

■ Email messages or folders from an Exchange database backup

■ A document from a SharePoint database backup

Multiple NetBackup agents that supportGRT(for example, Exchange, SharePoint,

and Active Directory) can use the same media server.

[JHeaton]

I read that too, Chapter 28 of the Admin Guide, Vol. 1.

Doesn't really answer the question, which is why I asked it.

In order to backup my Active Directory metadata, do I have to implement GRT, and therefore, NFS?

[Andy_Welburn]

restore individual objects & attributes from AD - i.e. Granular Restore

[JHeaton]

Ok, so if I don't want/need the granularity (at least at this moment), is there something in the client install process that recognizes that the client is a DC, and therefore needs to have the AD data backed up?  My biggest concern at the moment is to ensure that AD is being backed up.

[Andy_Welburn · Accepted solution]

you can just treat it as a 'normal' Windows client - just ensure you get good copies of Shadow Copy Components/System State (not sure if anything of relevance "leaks" onto C:\ drive?) - maybe speak to your Windows admins?

From the Admin Guide:

The Volume Shadow Copy components include the following:
■ System State writers, which can include:
■ System files
■ COM+ Class Registration Database
■ SYSVOL
■ Active Directory
■ Cluster quorum
■ Certificate Services
■ Registry
■ Internet Information Services
■ System Service writers, which can include:
■ Removable Storage Manager
■ Event logs
■ Windows Internet Name Service
■ Windows Management Instrumentation
■ Remote Storage
■ Dynamic Host Configuration Protocol
■ Terminal Server Licensing
■ Background Intelligent Transfer Service
■ UserData writers, which include any items that the computer does not require to operate. For example, Active Directory Application Mode.

[JHeaton]

That's what I was looking for, thanks Andy :)

And I am one of the Windows Admins, hehe....