Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NBU 7.1 with Exchange DAG 2010 - host names

Created: 24 Oct 2012 • Updated: 13 Jan 2013 | 6 comments
Willie_SA's picture
This issue has been solved. See solution.

Master and Media server        Windows 2008      

NetBackup                            7.1

Exchange                              DAG 2010

Phyusical host names            PRASAGPPMBX01  and PRASAGPPMBX02

Virtual hyost name                 PRASAGPPDAG01

 

Attempting to create new policy for Exchange backups. Followed tech tip/note for DAG backups. Firstly for PPMBX01.

Error when running manual test backup at botom.  client/server handshaking failed  (26)

Must we be able to ping the Virtual host name from master and media server? If yes - can we add it to HOSTS file?

Must we build same policy with same virtual host for PPMBX02?

What handshaking is happening?

 

10/24/2012 10:54:20 - Error bpbrm (pid=4504) bpcd on PRASAGPPDAG01.prasa.com exited with status 48: client hostname could not be found

10/24/2012 10:54:20 - Info bpbrm (pid=4504) PRASAGPPDAG01.prasa.com is the host to restore data

10/24/2012 10:54:20 - Info nbjm (pid=4368) starting backup job (jobid=1348) for client PRASAGPPDAG01.prasa.com, policy Exchange, schedule Daily-Full

10/24/2012 10:54:20 - Info nbjm (pid=4368) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=1348, request id:{F3115823-0F32-42C1-AB55-159044BB526C})

10/24/2012 10:54:20 - requesting resource prasagppbck02-hcart2-robot-tld-0

10/24/2012 10:54:20 - requesting resource prasagppbck01.prasa.com.NBU_CLIENT.MAXJOBS.PRASAGPPDAG01.prasa.com

10/24/2012 10:54:20 - requesting resource prasagppbck01.prasa.com.NBU_POLICY.MAXJOBS.Exchange

10/24/2012 10:54:20 - requesting resource EXCHANGE_RESOLVER.prasagppbck01.prasa.com.Exchange.PRASAGPPDAG01.prasa.com

10/24/2012 10:54:20 - granted resource  prasagppbck01.prasa.com.NBU_CLIENT.MAXJOBS.PRASAGPPDAG01.prasa.com

10/24/2012 10:54:20 - granted resource  prasagppbck01.prasa.com.NBU_POLICY.MAXJOBS.Exchange

10/24/2012 10:54:20 - granted resource  EXCHANGE_RESOLVER.prasagppbck01.prasa.com.Exchange.PRASAGPPDAG01.prasa.com

10/24/2012 10:54:20 - estimated 0 kbytes needed

10/24/2012 10:54:20 - begin Parent Job

10/24/2012 10:54:20 - Info RUNCMD (pid=2816) started

10/24/2012 10:54:20 - Info RUNCMD (pid=2816) exiting with status: 0

Operation Status: 0

10/24/2012 10:54:20 - end Parent Job; elapsed time 0:00:00

Operation Status: 0

Operation Status: 0

10/24/2012 10:54:20 - started process bpbrm (pid=4504)

Operation Status: 26

Operation Status: 0

10/24/2012 10:54:26 - Info RUNCMD (pid=6968) started

10/24/2012 10:54:26 - Info RUNCMD (pid=6968) exiting with status: 0

Operation Status: 0

Operation Status: 26

client/server handshaking failed  (26)

 

 

 

 

Comments 6 CommentsJump to latest comment

Nicolai's picture

You use the virtual service name in the policy. 

Ping of the virtual hostname must work. Yes you can add it to the host file - but please use some additional time to ensure name resolution is in place - both forward and reverse. Also ensure physical nodes are resolvable.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Marianne's picture

ONLY use virtual name in backup policy.

Map physical node names to Virtual name as per this section in NBU For Exchange Manual:

 

To configure restores for multiple Exchange Server hosts
1 On the master server, open the NetBackup Administration Console.
2 Select NetBackup Management > Host Properties > Master Servers.
3 In the right pane, double-click on the master server.
4 Select Distributed Application Restore Mapping.
5 Click Add.
6 Provide the name of the application host and the name of the component host, as follows:
(See manual for examples)
 
If I remember correctly, the above is also mentioned in NBU for Exchange Video:
Configuring Exchange 2010 Database Availability Group (DAG) Backups with NetBackup 7.0 
 
You need to ensure that DNS can resolve shortnames to FQDN.  
See this error: 
 bpcd on PRASAGPPDAG01.prasa.com exited with status 48: client hostname could not be found
Symantec recommends that you use the fully qualified domain name (FQDN) of the nodes in NBU config.

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
Willie_SA's picture

Let me first sort out the network communication because at the moment the master and media server cannot ping the virtual host name(it can ping the physial host names).

Marianne's picture

Get hold of Network/DNS admin.
You should not have this issue in an 'All Windows' environment.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

captain jack sparrow's picture

Just an update Willie

In case of host file entries, ensure hostname and fqdn both are added. Also same (hostname and fqdn , or prefer to add fqdn only under host properties)

Follow same fqdn method for policy creation (it's best to keep same naming trend with NBU,

For virtual name not able to ping from master/media. Cross check what IP does it resolves

 

 Cheers !!!

CJS

 

captain jack sparrow's picture

Hi Willie

 

Missed this, Do update all mailbox servers under preferred servers (under policy attribute) according to active or passive you choose). So NBU can sync with CAS accordingly which indirectly resolves where DB copies are active or passive)

 

 Cheers !!!

CJS