Video Screencast Help

Every time am Backing up Exchange I got partially successful solution

Created: 12 Jun 2013 • Updated: 24 Jul 2013 | 5 comments
This issue has been solved. See solution.

Dear Experts;

 

When am running a backup to Exchange DAG (GRT) I got partially successful solution which means that we have some files still not backed up.
The NBU version used is 7.5.0.5 and the job detailed log is below. 

 

Also, is there any way from Exchange I can know that some thing is missing or some data is not backed up.

 

 

6/12/2013 12:00:00 AM - Info nbjm(pid=5840) starting backup job (jobid=370084) for client exchange-dag.sipchem.local, policy Exch2010-GRT-Exec, schedule Full 
6/12/2013 12:00:00 AM - Info nbjm(pid=5840) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=370084, request id:{58344C70-92EF-4EEC-ADFC-DF961A8CF31D}) 
6/12/2013 12:00:00 AM - requesting resource STU1-MBXDB02
6/12/2013 12:00:00 AM - requesting resource sipc-netbackup.NBU_CLIENT.MAXJOBS.exchange-dag.sipchem.local
6/12/2013 12:00:00 AM - requesting resource sipc-netbackup.NBU_POLICY.MAXJOBS.Exch2010-GRT-Exec
6/12/2013 12:00:00 AM - requesting resource EXCHANGE_RESOLVER.sipc-netbackup.Exch2010-GRT-Exec.exchange-dag.sipchem.local
6/12/2013 12:00:00 AM - granted resource sipc-netbackup.NBU_CLIENT.MAXJOBS.exchange-dag.sipchem.local
6/12/2013 12:00:00 AM - granted resource sipc-netbackup.NBU_POLICY.MAXJOBS.Exch2010-GRT-Exec
6/12/2013 12:00:00 AM - granted resource EXCHANGE_RESOLVER.sipc-netbackup.Exch2010-GRT-Exec.exchange-dag.sipchem.local
6/12/2013 12:00:00 AM - estimated 237810894 Kbytes needed
6/12/2013 12:00:00 AM - begin Parent Job
6/12/2013 12:00:00 AM - begin Exchange 14 Resolver, Start Notify Script
6/12/2013 12:00:01 AM - Info RUNCMD(pid=8056) started           
6/12/2013 12:00:01 AM - Info RUNCMD(pid=8056) exiting with status: 0        
Status 0
6/12/2013 12:00:01 AM - end Exchange 14 Resolver, Start Notify Script; elapsed time: 00:00:01
6/12/2013 12:00:01 AM - begin Exchange 14 Resolver, Step By Condition
Status 0
6/12/2013 12:00:01 AM - end Exchange 14 Resolver, Step By Condition; elapsed time: 00:00:00
6/12/2013 12:00:01 AM - begin Exchange 14 Resolver, Read File List
Status 0
6/12/2013 12:00:01 AM - end Exchange 14 Resolver, Read File List; elapsed time: 00:00:00
6/12/2013 12:00:01 AM - begin Exchange 14 Resolver, Resolver Discovery
6/12/2013 12:00:02 AM - started process bpbrm (8984)
6/12/2013 12:00:05 AM - Info bpbrm(pid=8984) exchange-dag.sipchem.local is the host to restore to     
6/12/2013 12:00:05 AM - Info bpbrm(pid=8984) reading file list from client       
6/12/2013 12:00:21 AM - Info bpbrm(pid=8984) client_pid=7424           
6/12/2013 12:00:22 AM - Info bpbrm(pid=8984) from client exchange-dag.sipchem.local: TRV - BPRESOLVER has executed on server (SIPC-MBXDB02) 
6/12/2013 12:00:34 AM - Info bpbrm(pid=8984) from client exchange-dag.sipchem.local: TRV - Last backup attempt of database 'Microsoft Information Store:\Public Folder' on server SIPC-MBXDB01 failed.  Will try to find another server in preferred server list.
6/12/2013 12:00:34 AM - Info bpbrm(pid=8984) from client exchange-dag.sipchem.local: TRV - Last backup attempt of database 'Microsoft Information Store:\Managers & SecMgrs' on server SIPC-MBXDB01 failed.  Will try to find another server in preferred server list.
6/12/2013 12:00:34 AM - Info bpbrm(pid=8984) from client exchange-dag.sipchem.local: TRV - Last backup attempt of database 'Microsoft Information Store:\Executives' on server SIPC-MBXDB02 failed.  Will try to find another server in preferred server list.
6/12/2013 12:00:34 AM - Info bpbrm(pid=8984) from client exchange-dag.sipchem.local: TRV - Last backup attempt of database 'Microsoft Information Store:\IT' on server SIPC-MBXDB01 failed.  Will try to find another server in preferred server list.
Status 0
6/12/2013 12:00:35 AM - end Exchange 14 Resolver, Resolver Discovery; elapsed time: 00:00:34
6/12/2013 12:00:35 AM - begin Exchange 14 Resolver, Persist Discovery
Status 0
6/12/2013 12:00:35 AM - end Exchange 14 Resolver, Persist Discovery; elapsed time: 00:00:00
6/12/2013 12:00:35 AM - begin Exchange 14 Resolver, Policy Execution Manager Preprocessed
Status 1
6/12/2013 12:42:55 AM - end Exchange 14 Resolver, Policy Execution Manager Preprocessed; elapsed time: 00:42:20
6/12/2013 12:42:55 AM - begin Exchange 14 Resolver, Validate Image
Status 0
6/12/2013 12:42:55 AM - end Exchange 14 Resolver, Validate Image; elapsed time: 00:00:00
6/12/2013 12:42:55 AM - begin Exchange 14 Resolver, End Notify Script
6/12/2013 12:42:56 AM - Info RUNCMD(pid=7512) started           
6/12/2013 12:42:56 AM - Info RUNCMD(pid=7512) exiting with status: 0        
Status 0
6/12/2013 12:42:56 AM - end Exchange 14 Resolver, End Notify Script; elapsed time: 00:00:01
Status 1
6/12/2013 12:42:56 AM - end Parent Job; elapsed time: 00:42:56
the requested operation was partially successful(1)

The job was successfully completed, but some files may have been
busy or unaccessible. See the problems report or the client's logs for more details.

Operating Systems:

Comments 5 CommentsJump to latest comment

Nagalla's picture

hi,

does it ever worked fine?

did you enable the  NFS services?

Nagalla's picture

hi,

so its never worked previously ..right?

let us know how you configured this..

show us the output of bppllist <policyname> -U

what is the netbackup version in Exchage server?

BasigDegrasia3's picture

Hi Nagalla,

No, it was working fine

the Netbackup version is 7.5.0.5 in all MAster, Medias, and Clients servers.

The output of bpplist command is shown below

------------------------------------------------------------

Policy Name:       exch2010-weekly-full

  Policy Type:         MS-Exchange-Server
  Active:              yes
  Effective date:      11/08/2010 14:42:02
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           sipc-mbxdb01-hcart2-robot-tld-2
  Volume Pool:         Exchange_LTO5
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Exchange Source passive db if available: yes
  Exchange 2010 Preferred Server:  sipc-mbxdb02 sipc-mbxdb01  Application Discov
ery:      no
  Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  yes
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows2008   exchange-dag.sipchem.local

  Include:  Microsoft Exchange Database Availability Groups:\Exchange-DAG.sipche
m.local\Microsoft Information Store

  Schedule:              Full
    Type:                Automatic Backup
    Frequency:           every 7 days
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     3 (1 month)
    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:
          Friday     00:10:00  -->  Friday     04:00:00

  Schedule:              Daily-Inc-BK
    Type:                Differential Incremental 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:
          Sunday     17:10:00  -->  Sunday     21:50:00
          Monday     17:10:00  -->  Monday     21:50:00
          Tuesday    17:10:00  -->  Tuesday    21:50:00
          Wednesday  17:10:00  -->  Wednesday  21:50:00
          Thursday   17:10:00  -->  Thursday   21:50:00
          Saturday   17:10:00  -->  Saturday   21:50:00

 

 

Bader N. AL-Shammari

Systems Engineer

SOLUTION