Video Screencast Help

New Exchange 2010 Backup fails

Created: 29 Nov 2012 | 11 comments

We have just fired up new Exchange 2010 servers and the policy i created using this article (among other things) https://www-secure.symantec.com/connect/articles/exchange-serve-2010-backup-databases-and-restore-rdb continues to fail.

Here is the job details. Can anyone offer advice/help/opinions? Thanks!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

11/29/2012 9:21:18 AM - Info nbjm(pid=6572) starting backup job (jobid=274518) for client mbx01, policy Exchange, schedule Full 
11/29/2012 9:21:18 AM - Info nbjm(pid=6572) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=274518, request id:{39CBF352-9057-4313-85F1-51FF7FCF1DC2}) 
11/29/2012 9:21:18 AM - requesting resource horus-hcart-robot-tld-1
11/29/2012 9:21:18 AM - requesting resource horus.NBU_CLIENT.MAXJOBS.mbx01
11/29/2012 9:21:18 AM - requesting resource horus.NBU_POLICY.MAXJOBS.Exchange
11/29/2012 9:21:18 AM - requesting resource EXCHANGE_RESOLVER.horus.Exchange.mbx01
11/29/2012 9:21:18 AM - granted resource horus.NBU_CLIENT.MAXJOBS.mbx01
11/29/2012 9:21:18 AM - granted resource horus.NBU_POLICY.MAXJOBS.Exchange
11/29/2012 9:21:18 AM - granted resource EXCHANGE_RESOLVER.horus.Exchange.mbx01
11/29/2012 9:21:19 AM - estimated 0 Kbytes needed
11/29/2012 9:21:19 AM - begin Parent Job
11/29/2012 9:21:19 AM - begin Exchange 14 Resolver, Start Notify Script
11/29/2012 9:21:19 AM - Info RUNCMD(pid=2588) started           
11/29/2012 9:21:19 AM - Info RUNCMD(pid=2588) exiting with status: 0        
Status 0
11/29/2012 9:21:19 AM - end Exchange 14 Resolver, Start Notify Script; elapsed time: 00:00:00
11/29/2012 9:21:19 AM - begin Exchange 14 Resolver, Step By Condition
Status 0
11/29/2012 9:21:19 AM - end Exchange 14 Resolver, Step By Condition; elapsed time: 00:00:00
11/29/2012 9:21:19 AM - begin Exchange 14 Resolver, Read File List
Status 0
11/29/2012 9:21:19 AM - end Exchange 14 Resolver, Read File List; elapsed time: 00:00:00
11/29/2012 9:21:19 AM - begin Exchange 14 Resolver, Resolver Discovery
11/29/2012 9:21:20 AM - started process bpbrm (10168)
11/29/2012 9:21:21 AM - Info bpbrm(pid=10168) mbx01 is the host to restore to     
11/29/2012 9:21:21 AM - Info bpbrm(pid=10168) reading file list from client       
11/29/2012 9:21:30 AM - Info bpbrm(pid=10168) client_pid=9972           
11/29/2012 9:21:30 AM - Info bpbrm(pid=10168) from client mbx01: TRV - BPRESOLVER has executed on server (MBX01) 
11/29/2012 9:21:41 AM - Info bpresolver(pid=9972) done.  status: 2        
11/29/2012 9:21:41 AM - Error bpbrm(pid=10168) no worklist items returned from bpresolver on client  mbx01  
11/29/2012 9:21:41 AM - Info bpresolver(pid=9972) done. status: 2: none of the requested files were backed up 
Status 2
11/29/2012 9:21:41 AM - end Exchange 14 Resolver, Resolver Discovery; elapsed time: 00:00:22
11/29/2012 9:21:41 AM - begin Exchange 14 Resolver, Stop On Error
Status 0
11/29/2012 9:21:41 AM - end Exchange 14 Resolver, Stop On Error; elapsed time: 00:00:00
11/29/2012 9:21:41 AM - begin Exchange 14 Resolver, End Notify Script
11/29/2012 9:21:41 AM - Info RUNCMD(pid=1076) started           
11/29/2012 9:21:41 AM - Info RUNCMD(pid=1076) exiting with status: 0        
Status 0
11/29/2012 9:21:41 AM - end Exchange 14 Resolver, End Notify Script; elapsed time: 00:00:00
Status 2
11/29/2012 9:21:41 AM - end Parent Job; elapsed time: 00:00:22
none of the requested files were backed up(2)

Comments 11 CommentsJump to latest comment

Mark_Solutions's picture

Can we see your policy listing please - it looks like you have the mailbox server as the client name rather than the name of the DAG

You obviously also need to ensure all other pre-requisites have been completed

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

pmc214's picture

we have 2 mbx servers and a client access sever (cas01).

Policy Listing - ?

 

Mark_Solutions's picture

What is your actual DAG name? that is what should be in the policy

You can do a bppllist policyname -U to pipe out the policy details

Have the mailbox servers and CAS server had the NetBackup clients installed

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

pmc214's picture

i tried using - Microsoft Exchange Database Availability Groups:\DAG01.xxxxxx.xxx

the cas server does not have client installed... we are backing it up using VM.

Policy Name:       Exchange

  Policy Type:         MS-Exchange-Server
  Active:              yes
  Effective date:      11/28/2012 16:55:18
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           horus-hcart-robot-tld-1
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Exchange Source active db:               yes
  Exchange 2010 Preferred Server: (none defined)
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows2008   mbx01
                 Windows-x86   Windows2008   mbx02

  Include:  Microsoft Exchange Database Availability Groups:\DAG01.xxxxxx.xxx

  Schedule:              Full
    Type:                Automatic Backup
    Frequency:           every 1 day
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Wednesday  06:00:00  -->  Wednesday  23:50:00

Mark_Solutions's picture

The client should just be DAG01, not the mailbox servers and the CAS will need a NetBackup client installing as it talks to that to do the resolving of the mailbox servers

Alternatively if on 7.5 do it all via VM but again you need a client installing plus the Symantec Snapshot Provider installing

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Will Restore's picture

from the Admin Guide

 

Install the NetBackup client software on the computer that has the Exchange

Server, any off-host clients, and all CAS servers that are used for mailbox

databases. In an Exchange Server cluster, install the NetBackup client on each

node in the cluster.

Will Restore -- where there is a Will there is a way

pmc214's picture

detail status after changes and installing 7.5 client on cas01

11/29/2012 12:27:08 PM - Info nbjm(pid=6572) starting backup job (jobid=274529) for client dag01, policy Exchange, schedule Full 
11/29/2012 12:27:08 PM - Info nbjm(pid=6572) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=274529, request id:{4D993E0C-6262-4C6B-8358-C2FF2527E3E5}) 
11/29/2012 12:27:08 PM - requesting resource Any
11/29/2012 12:27:08 PM - requesting resource horus.NBU_CLIENT.MAXJOBS.dag01
11/29/2012 12:27:08 PM - requesting resource horus.NBU_POLICY.MAXJOBS.Exchange
11/29/2012 12:27:08 PM - requesting resource EXCHANGE_RESOLVER.horus.Exchange.dag01
11/29/2012 12:27:08 PM - granted resource horus.NBU_CLIENT.MAXJOBS.dag01
11/29/2012 12:27:08 PM - granted resource horus.NBU_POLICY.MAXJOBS.Exchange
11/29/2012 12:27:08 PM - granted resource EXCHANGE_RESOLVER.horus.Exchange.dag01
11/29/2012 12:27:09 PM - estimated 0 Kbytes needed
11/29/2012 12:27:09 PM - begin Parent Job
11/29/2012 12:27:09 PM - begin Exchange 14 Resolver, Start Notify Script
11/29/2012 12:27:09 PM - Info RUNCMD(pid=3648) started           
11/29/2012 12:27:09 PM - Info RUNCMD(pid=3648) exiting with status: 0        
Status 0
11/29/2012 12:27:09 PM - end Exchange 14 Resolver, Start Notify Script; elapsed time: 00:00:00
11/29/2012 12:27:09 PM - begin Exchange 14 Resolver, Step By Condition
Status 0
11/29/2012 12:27:09 PM - end Exchange 14 Resolver, Step By Condition; elapsed time: 00:00:00
11/29/2012 12:27:09 PM - begin Exchange 14 Resolver, Read File List
Status 0
11/29/2012 12:27:09 PM - end Exchange 14 Resolver, Read File List; elapsed time: 00:00:00
11/29/2012 12:27:09 PM - begin Exchange 14 Resolver, Resolver Discovery
11/29/2012 12:27:10 PM - started process bpbrm (10132)
11/29/2012 12:30:46 PM - Info bpbrm(pid=10132) connect failed STATUS (18) CONNECT_FAILED       
11/29/2012 12:30:46 PM - Info bpbrm(pid=10132)  status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO dag01 128.1.9.13 bpcd VIA pbx
11/29/2012 12:30:46 PM - Info bpbrm(pid=10132)  status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO dag01 128.1.9.13 bpcd VIA vnetd
11/29/2012 12:30:46 PM - Info bpbrm(pid=10132)  status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO dag01 128.1.9.13 bpcd
11/29/2012 12:30:46 PM - Error bpbrm(pid=10132) Cannot connect to dag01        
Status 26
11/29/2012 12:30:46 PM - end Exchange 14 Resolver, Resolver Discovery; elapsed time: 00:03:37
11/29/2012 12:30:46 PM - begin Exchange 14 Resolver, Stop On Error
Status 0
11/29/2012 12:30:46 PM - end Exchange 14 Resolver, Stop On Error; elapsed time: 00:00:00
11/29/2012 12:30:46 PM - begin Exchange 14 Resolver, End Notify Script
11/29/2012 12:30:47 PM - Info RUNCMD(pid=7908) started           
11/29/2012 12:30:47 PM - Info RUNCMD(pid=7908) exiting with status: 0        
Status 0
11/29/2012 12:30:47 PM - end Exchange 14 Resolver, End Notify Script; elapsed time: 00:00:01
Status 26
11/29/2012 12:30:47 PM - end Parent Job; elapsed time: 00:03:38
client/server handshaking failed(26)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Policy Name:       Exchange

  Policy Type:         MS-Exchange-Server
  Active:              yes
  Effective date:      11/28/2012 16:55:18
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Exchange Source active db:               yes
  Exchange 2010 Preferred Server: (none defined)
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x86   Windows2008   dag01

  Include:  Microsoft Exchange Database Availability Groups:\

  Schedule:              Full
    Type:                Automatic Backup
    Frequency:           every 1 day
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Wednesday  06:00:00  -->  Wednesday  23:50:00

Will Restore's picture

Cannot connect to dag01        
Status 26
 

 

What is the virtual name?  DAG01 ?    Client name in the Policy is case-sensitive.

Will Restore -- where there is a Will there is a way

pmc214's picture

changed name in policy... still handshake problem?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

11/30/2012 11:34:01 AM - Info nbjm(pid=6496) starting backup job (jobid=274792) for client DAG01, policy Exchange, schedule Full 
11/30/2012 11:34:01 AM - Info nbjm(pid=6496) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=274792, request id:{EE019903-A9EB-4506-A0A8-318F713A3315}) 
11/30/2012 11:34:01 AM - requesting resource Any
11/30/2012 11:34:01 AM - requesting resource horus.NBU_CLIENT.MAXJOBS.DAG01
11/30/2012 11:34:01 AM - requesting resource horus.NBU_POLICY.MAXJOBS.Exchange
11/30/2012 11:34:01 AM - requesting resource EXCHANGE_RESOLVER.horus.Exchange.DAG01
11/30/2012 11:34:01 AM - granted resource horus.NBU_CLIENT.MAXJOBS.DAG01
11/30/2012 11:34:01 AM - granted resource horus.NBU_POLICY.MAXJOBS.Exchange
11/30/2012 11:34:01 AM - granted resource EXCHANGE_RESOLVER.horus.Exchange.DAG01
11/30/2012 11:34:01 AM - estimated 0 Kbytes needed
11/30/2012 11:34:01 AM - begin Parent Job
11/30/2012 11:34:01 AM - begin Exchange 14 Resolver, Start Notify Script
11/30/2012 11:34:02 AM - Info RUNCMD(pid=3512) started           
11/30/2012 11:34:02 AM - Info RUNCMD(pid=3512) exiting with status: 0        
Status 0
11/30/2012 11:34:02 AM - end Exchange 14 Resolver, Start Notify Script; elapsed time: 00:00:01
11/30/2012 11:34:02 AM - begin Exchange 14 Resolver, Step By Condition
Status 0
11/30/2012 11:34:02 AM - end Exchange 14 Resolver, Step By Condition; elapsed time: 00:00:00
11/30/2012 11:34:02 AM - begin Exchange 14 Resolver, Read File List
Status 0
11/30/2012 11:34:02 AM - end Exchange 14 Resolver, Read File List; elapsed time: 00:00:00
11/30/2012 11:34:02 AM - begin Exchange 14 Resolver, Resolver Discovery
11/30/2012 11:34:02 AM - started process bpbrm (3460)
11/30/2012 11:37:38 AM - Info bpbrm(pid=3460) connect failed STATUS (18) CONNECT_FAILED       
11/30/2012 11:37:38 AM - Info bpbrm(pid=3460)  status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO DAG01 128.1.9.13 bpcd VIA pbx
11/30/2012 11:37:38 AM - Info bpbrm(pid=3460)  status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO DAG01 128.1.9.13 bpcd VIA vnetd
11/30/2012 11:37:38 AM - Info bpbrm(pid=3460)  status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO DAG01 128.1.9.13 bpcd
11/30/2012 11:37:38 AM - Error bpbrm(pid=3460) Cannot connect to DAG01        
11/30/2012 11:37:38 AM - Info (pid=0) done. status: 58: can't connect to client     
Status 26
11/30/2012 11:37:38 AM - end Exchange 14 Resolver, Resolver Discovery; elapsed time: 00:03:36
11/30/2012 11:37:38 AM - begin Exchange 14 Resolver, Stop On Error
Status 0
11/30/2012 11:37:38 AM - end Exchange 14 Resolver, Stop On Error; elapsed time: 00:00:00
11/30/2012 11:37:38 AM - begin Exchange 14 Resolver, End Notify Script
11/30/2012 11:37:39 AM - Info RUNCMD(pid=9872) started           
11/30/2012 11:37:39 AM - Info RUNCMD(pid=9872) exiting with status: 0        
Status 0
11/30/2012 11:37:39 AM - end Exchange 14 Resolver, End Notify Script; elapsed time: 00:00:01
Status 26
11/30/2012 11:37:39 AM - end Parent Job; elapsed time: 00:03:38
client/server handshaking failed(26)

captain jack sparrow's picture

Can you disable OS firewall (if enabled) at client end. Do verify required ports are allowed in bi-directional in between NBU Master/Media and clients

Have seen this similar due to ports being blocked

 Cheers !!!

CJS

 

raj08's picture

Please check if "dag01 " is in dns and able to get ping reply from the netbackup master server. Sometimes this error happens when netbackup is not able to ping DAG.

..RAJ

..Raj