Forum Discussion

Level 5

10 years ago

NBU 7.5.0.3 backup job fails with error 130

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

Marianne
Level 6
10 years ago
Is circular logging enabled on the DAG? Incr backups are not supported.
Michal_Mikulik1
Moderator
10 years ago
Hello,

onl\y incr backups are failing, not full. I would say that full backups must fail , too. It looks like VSS related issue.

Check health of VSS by OS command: vssadmin list writers.

I think there will be some problem, follow VSS steps then (sometimes node restart is required).

Michal
grigori
Level 5
10 years ago
hi Michal and Marianne.

thanks for replying.

@Marianne

the policy is of type inc differential backup. backup was running fine before and circular logging isnt enabled

@Michal

i have actually restarted the mailbox01 server, but the issue is still there also the writers are all stable on both mailbox servers.

thanks
Marianne
Level 6
10 years ago

.... the policy is of type inc differential backup.....

Full and Incr schedules need to be in the same policy.
Please confirm?

Also confirm that DAG virtual hostname is in Policy clients tab and not DAG node(s).

The next step is to enable logs - create bpfis log folder on all DAG nodes to troubleshoot snapshot failure.
Any VSS errors in Windows Event Viewer?
Mark_Solutions
Level 6
10 years ago
There is quite a big gap here .. what are the other jobs showing during that period?

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

It may just be hitting a 1 hour timeout (Client read timeout of 3600 on media server?)
cruisen
Level 6
10 years ago
I do not remember quite well, but if your dag is on a virtual machines, you need to intstall the snaphhot provider from veritas, because the incremental flushes the logs.

https://www.veritas.com/support/en_US/article.HOWTO85812

I looked for you the technote, i hope it helps:

https://www.veritas.com/support/en_US/article.HOWTO85812

The Symantec VSS provider is recommended instead of the VMware VSS provider in the following cases:

You want VMware backups to truncate the logs on Exchange Server virtual machines. The Symantec VSS provider truncates logs for Exchange Server, by means of full VSS backups.

The virtual machine you want to back up is a node in an Exchange 2010 DAG or an Exchange 2007 CCR. In this case, only the active copies of the database are cataloged and the log files for only those same databases are truncated.

You want to use an exclude file list for Exchange. See the following for details on how to configure an exclude file list for Exchange.
Marianne
Level 6
10 years ago
Seems snapshot attempt took this long before giving up?
grigori
Level 5
10 years ago
hi,

sorry it has been a while

@Cruisen;

our environment is based on physical server

@Mariane;

we are using virtual name in the clients tab selection also Full and Incr schedules are in the same policy.

i have enabled the bpfis logs on the master server and the mailbox servers.

it seems that the administrator has 2 public database folder that he says he is not using them but looking at them from the exchange console, these databases are mounted on mailbox01. i think the issue resides here.

i will try to exclude these database from backup selection and give the job a try.

i will post the bpfis logs later since i forgot to get them.
cruisen
Level 6
10 years ago
I remember something about claering in the public folders, let me check.
cruisen
Level 6
10 years ago
I am sorry, I did not get the information. Please try the folowing, try to trace exchange logs and find out which erreur message on the public folders happen. Aftre that with simple exchange commands you should e able to fix you issue. Please post your logs from the exchange.

I remember that items were not visible, or 0 KB or not mounted but , i can not exactly tell you whiic erreur message i got. Try to check with your Exchange admin, and often they have heard about the error message before, but never fixed it because actually, it makes no difference on an Exchange perpective, but it will importent for a clean the backup.