Request to verify this configuration (VMware Exchange 2010 GRT)

Hi,

I wonder if somebody might be able to validate our configuration before we start using NBU 7.6.1 for Exchange 2010 backups / restores.  We are using a minimal account rather than full Exhange / Domain admin account.  We will be using a vmware policy with the Exchange Recovery & Logs options selected.  All servers are virtual.

Environment consists of the following:

Exchange

• Two node DAG cluster (MBX-1 & MBX-2). Each contain active & passive DB's.
• Three Client Access Servers (CAS-1, CAS-2 & CAS-3).
• Hardware Load Balancer sat in front of above CAS servers (CAS Array: outlook.domain.co.uk).
• Two HUB Transport Servers (HUB-1 & HUB-2)

NetBackup

• 1 x Master Server (NBU-MASTER)
• 2 x Media Server (NBU-MASTER & NBU-MEDIA)

Configuration:

• Created Active Directory user called 'NBU-MBX'
• Member of: 'Domain Users', 'NetBackup Roles'
• Created mailbox for above account

Scripts:

Ran the following scripts within MBX-1 EMS:

• New-RoleGroup -Name NetBackupRoles -Roles @("Database Copies", "Databases", "Exchange Servers", "Monitoring", "Mail Recipient Creation", "Mail Recipients", "Recipient Policies")
• Add-RoleGroupMember -Identity NetBackupRoles -Member NBU-MBX
• New-ManagementRole -Name SymantecEWSImpersonationRole -Parent ApplicationImpersonation
• New-ManagementRoleAssignment -Role SymantecEWSImpersonationRole -User NetBackupUser -Name "NBU-MBX-EWSImpersonation"
• New-ThrottlingPolicy -Name "SymantecEWSRestoreThrottlingPolicy" -EWSPercentTimeInCAS $null -EWSPercentTimeInAD $null -EWSMaxConcurrency $null -EWSPercentTimeInMailboxRPC $null -PowerShellMaxConcurrency $null
• Set-Mailbox -Identity NBU-MBX -ThrottlingPolicy "SymantecEWSRestoreThrottlingPolicy"

NBU-MASTER

• Server for NFS Role Installed
• Server for NFS service stopped & disabled
• Ran "sc config portmap start=auto" command

NBU-MEDIA

• Server for NFS Role Installed
• Server for NFS service stopped & disabled
• Ran "sc config portmap start=auto" command

Within NBU Console

• Client Properties of MBX-1 -> Windows Client -> Exchange -> Entered credentials of NBU-MBX account.
• Client Properties of MBX-2 -> Windows Client -> Exchange -> Entered credentials of NBU-MBX account.
• Host Properties -> Master servers -> NBU-MASTER -> Distributed Application Restore Map -> added the following:

Application Host    Component Host
----------------------------------------
DAG1                   MBX-1
DAG1                   MBX-2

MBX-1

• Added NBU-MBX account to local Administrators group.
• Installed NBU Client.
• Configured all NBU Client services to logon using NBU-MBX account.
• Installed Symantec VSS.
• Added NBU-MBX account to "Replace a process level token" group.
• Installed 'Server for NFS' Role.
• 'Server for NFS' Service set to Disabled.
• Installed 'Client for NFS'.
• 'Client for NFS' service set to Automatic Startup however when click start it stops immediately.  Normal?

MBX-2

• Added NBU-MBX account to local Administrators group
• Installed NBU Client
• Configured all NBU Client services to logon using NBU-MBX account
• Installed Symantec VSS
• Added NBU-MBX account to "Replace a process level token" group
• Installed 'Server for NFS' Role
• 'Server for NFS' Service set to Disabled
• Installed 'Client for NFS'
• 'Client for NFS' service set to Automatic Startup however when click start it stops immediately.  Normal?

Questions I have are:

• Do we not need to specify the CAS Array somewhere?
• Is it best practice to add entry within hosts file on Media Server for single CAS server rather than VIP of Hardware Load Balancer?
• Only the NFS Client is required on MBX & CAS servers?

Many thanks,

Graham