cancel
Showing results for 
Search instead for 
Did you mean: 

NBU 7.5.0.3 backup job fails with error 130

grigori
Level 5

hi All,

i have a dag incremental backup that is failing with error 130 folowed by DB_BACKUP_STATUS 103 and "snapshot preparation failed - Error attempting to find volumes to snap., status 130"

my NBU server is a solaris 10

i have 2 Exchange servers 2010 with dag

below are the job details of the failing job

2/29/2016 10:57:18 AM - Info nbjm(pid=22955) starting backup job (jobid=100168) for client MAILBOX01, policy XY-DAG, schedule XY-DAG-Daily  
2/29/2016 10:57:18 AM - Info nbjm(pid=22955) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=100168, request id:{0DD2FDC8-DEB1-11E5-8EE3-00269E9C1838})  
2/29/2016 10:57:18 AM - requesting resource Any
2/29/2016 10:57:18 AM - requesting resource SL500-Bserver.NBU_CLIENT.MAXJOBS.MAILBOX01
2/29/2016 10:57:18 AM - requesting resource SL500-Bserver.NBU_POLICY.MAXJOBS.XY-DAG
2/29/2016 10:57:19 AM - granted resource SL500-Bserver.NBU_CLIENT.MAXJOBS.MAILBOX01
2/29/2016 10:57:19 AM - granted resource SL500-Bserver.NBU_POLICY.MAXJOBS.XY-DAG
2/29/2016 10:57:19 AM - granted resource COM381
2/29/2016 10:57:19 AM - granted resource HP.ULTRIUM4-SCSI.000
2/29/2016 10:57:19 AM - granted resource mailbox01-hcart-robot-tld-0
2/29/2016 10:57:20 AM - estimated 43598370 Kbytes needed
2/29/2016 10:57:20 AM - begin Parent Job
2/29/2016 10:57:20 AM - begin Exchange 14 Snapshot, Step By Condition
Status 0
2/29/2016 10:57:20 AM - end Exchange 14 Snapshot, Step By Condition; elapsed time: 00:00:00
2/29/2016 10:57:20 AM - begin Exchange 14 Snapshot, Read File List
Status 0
2/29/2016 10:57:20 AM - end Exchange 14 Snapshot, Read File List; elapsed time: 00:00:00
2/29/2016 10:57:20 AM - begin Exchange 14 Snapshot, Create Snapshot
2/29/2016 10:57:20 AM - started
2/29/2016 10:57:21 AM - started process bpbrm (3068)
2/29/2016 10:58:14 AM - end writing
Status 130
2/29/2016 10:58:14 AM - end Exchange 14 Snapshot, Create Snapshot; elapsed time: 00:00:54
2/29/2016 10:58:14 AM - begin Exchange 14 Snapshot, Stop On Error
Status 0
2/29/2016 10:58:14 AM - end Exchange 14 Snapshot, Stop On Error; elapsed time: 00:00:00
2/29/2016 10:58:14 AM - begin Exchange 14 Snapshot, Delete Snapshot
2/29/2016 10:58:14 AM - started process bpbrm (1900)
2/29/2016 10:58:17 AM - end writing
Status 1542
2/29/2016 10:58:17 AM - end Exchange 14 Snapshot, Delete Snapshot; elapsed time: 00:00:03
Status 130
2/29/2016 10:58:17 AM - end Parent Job; elapsed time: 00:00:57
2/29/2016 12:01:47 PM - Info bpbrm(pid=3068) MAILBOX01 is the host to backup data from     
2/29/2016 12:01:47 PM - Info bpbrm(pid=3068) reading file list from client        
2/29/2016 12:01:47 PM - Info bpbrm(pid=3068) start bpfis on client         
2/29/2016 12:01:47 PM - Info bpbrm(pid=3068) Starting create snapshot processing         
2/29/2016 12:01:48 PM - Info bpfis(pid=8684) Backup started           
2/29/2016 12:02:34 PM - Critical bpbrm(pid=3068) from client MAILBOX01: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130
2/29/2016 12:02:34 PM - Info bpbrm(pid=3068) DB_BACKUP_STATUS is 103          
2/29/2016 12:02:40 PM - Info bpbrm(pid=3068) DB_BACKUP_STATUS is 103          
2/29/2016 12:02:40 PM - Critical bpbrm(pid=3068) from client MAILBOX01: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130
2/29/2016 12:02:41 PM - Info bpbrm(pid=1900) Starting delete snapshot processing         
2/29/2016 12:02:41 PM - Info bpfis(pid=0) Snapshot will not be deleted        
2/29/2016 12:02:42 PM - Info bpfis(pid=9092) Backup started           
2/29/2016 12:02:42 PM - Critical bpbrm(pid=1900) from client MAILBOX01: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.XY-dag_1456728774.1.0      
system error occurred(130)
 

 

regards,

 

23 REPLIES 23

cruisen
Level 6
Partner Accredited

please have a look at, just in case , it sound similar, WMI namespace erreurs:

https://www.veritas.com/community/forums/remote-backup-failing

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Circular logging is not supported with Incr backups.

grigori
Level 5

hi,

 thanks all for the great shares,

as per my reply to Marianne above about circular logging and following Cruisen and Mark Advices, i sit with the Exchange admin and asked him to provide me access to the Exchange GUI and found one of the mailbox databases having its circular logging enabled, disabling that should be done by unmounting the databse and mounting it back. also while checking the vssadmin writers, it was obvious that some of them were in error state and other were in waiting state. so i agreed with the admin to perform a reboot on mailbox servers and to disable circular logging on the mailbo database.

also while looking into the DB backup status using the command 

bpclient -client <DAG_name> -EXDB

i found some DB backup status is 156. so i used the following command 

bpclient -client DAG_Name -update -exdb DAG_DB3:EXSRV1:0:0:0

to reset their status.

after rebooting both DAG members and disabling circular logging and managing the DB backup exit status we arrived to solve this problem.

thanks again.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Please close off this discussion by selecting 'Request split solution' and then mark the posts that pointed you in the right direction. Thanks!