cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

file write failed (14) - Exchange DAG

hello everyone, everything good? I'm having a pretty annoying problem in a DAG exchange 2013 backup below:

20/12/2018 23:00:48 - Info nbjm (pid = 5408) starting backup job (jobid = 889994) for client ANVSSDF331.ANVISA.GOV.BR, policy ANVISA_EXCHANGE, schedule FULL_DIARIO
20/12/2018 23:00:48 - Info nbjm (pid = 5408) requesting STANDARD_RESOURCE resources from RB for backup job (jobid = 889994, request id: {6B695674-8AC2-4391-8CE4-2D014078CF6B})
12/20/2018 23:00:48 - requesting resource stu_disk_anvssdf143
12/20/2018 23:00:48 - requesting resource anvssdf37.NBU_CLIENT.MAXJOBS.ANVSSDF331.ANVISA.GOV.BR
12/20/2018 23:00:48 - requesting resource anvssdf37.NBU_POLICY.MAXJOBS.ANVISA_EXCHANGE
12/20/2018 23:00:48 - granted resource anvssdf37.NBU_CLIENT.MAXJOBS.ANVSSDF331.ANVISA.GOV.BR
12/20/2018 23:00:48 - granted resource anvssdf37.NBU_POLICY.MAXJOBS.ANVISA_EXCHANGE
20/12/2018 23:00:48 - granted resource MediaID = @ aaaaU; DiskVolume = PureDiskVolume; DiskPool = dp_disk_anvssdf143; Path = PureDiskVolume; StorageServer = anvssdf143; MediaServer = anvssdf143
12/20/2018 23:00:48 - granted resource stu_disk_anvssdf143
12/20/2018 23:00:48 - estimated 0 kbytes needed
20/12/2018 23:00:48 - Info nbjm (pid = 5408) started backup (backupid = dag01.anvisa.gov.br_1545354048) job for client ANVSSDF331.ANVISA.GOV.BR, policy ANVISA_EXCHANGE, schedule FULL_DIARIO on storage unit stu_disk_anvssdf143
12/20/2018 23:00:59 - started process bpbrm (pid = 84948)
12/20/2018 23:01:49 - connecting
20/12/2018 23:01:58 - Info bpbrm (pid = 84948) ANVSSDF331.ANVISA.GOV.BR is the host to backup data from
20/12/2018 23:02:03 - Info bpbrm (pid = 84948) reading file list for client
12/20/2018 23:02:03 - connected; connect time: 0:00:00
20/12/2018 23:02:18 - Info bpbrm (pid = 84948) starting bpbkar on client
20/12/2018 23:02:33 - Info bpbkar (pid = 21024) Backup started
20/12/2018 23:02:33 - Info bpbrm (pid = 84948) bptm pid: 85903
20/12/2018 23:02:34 - Info bptm (pid = 85903) start
20/12/2018 23:02:35 - Info bpbkar (pid = 21024) change time comparison: <disabled>
20/12/2018 23:02:35 - Info bpbkar (pid = 21024) archive bit processing: <disabled>
20/12/2018 23:02:52 - Info bptm (pid = 85903) using 262144 data buffer size
20/12/2018 23:02:52 - Info bptm (pid = 85903) using 30 data buffers
20/12/2018 23:03:06 - Info anvssdf143 (pid = 85903) Using OpenStorage client direct to backup from client dag01.anvisa.gov.br to anvssdf143
12/20/2018 23:03:35 - begin writing
20/12/2018 23:03:52 - Info bpbkar (pid = 21024) INF - waiting for mount mutex ...
12/21/2018 08:27:44 - Info anvssdf143 (pid = 85903) StorageServer = PureDisk: anvssdf143; Report = PDDO Stats for (anvssdf143): scanned: 246284293 KB, CR sent: 1381809 KB, CR sent over FC: 0 KB, dedup: 99.4%, cache hits: 13872 (0.7%)
12/21/2018 08:28:10 - end writing; write time: 9:24:35
21/12/2018 08:28:16 - Info bptm (pid = 85903) EXITING with status 14 <----------
12/21/2018 08:28:27 - Info bpbkar (pid = 21024) done. status: 14: file write failed
file write failed (14)

Media server: appliance 5230
Master Server: Win 2012 R2 (Virtual Machine)
Exchange DAG: Win2012 R2 Virtual Machine

Please help me.

 

 

Tags (2)
2 Solutions

Accepted Solutions
Highlighted
Accepted Solution!

Re: file write failed (14) - Exchange DAG

If you are using an Exchange policy rather than a VMware policy, bpfis and bpbkar32 run on Exchange server nodes of the DAG. The Activity Monitor tells you which client runs each job. Make sure the bpfis and bpbkar log folders exist on the clients. Also the beds folder. Set the global logging level for each client to at least 3 and and the Windows client logging level to 2.

For each Exchange server, also specify an Exchange account in the client host properties, in accordance with the instructions in the NetBackup admin guide for Exchange.

If you can't see all the Exchange servers as clients in the NetBackup console, create a dummy MS-Windows policy for each of them. Setting properties on the DAG is not sufficient. At any given time, it resolves to one specific Exchange server.

Please specify the Exchange version and the specific NetBackup version.

View solution in original post

Highlighted
Accepted Solution!

Re: file write failed (14) - Exchange DAG

Thank you for your help. I tested the hosts on the servers and the problem was solved. I diagnosed that the problem was related to DNS, I checked the DNS entries of the DNS servers and noticed that the "reverse" was not configured on our media server (appliance 5230) after setting the reverse the problem was solved. Thank you and sorry for the delay.

View solution in original post

4 Replies
Highlighted

Re: file write failed (14) - Exchange DAG

Please give more information and do a little log analysis before posting a 400,000 line log.

The log provided shows portions of 7 bpbkar executions, all of which finished with status 0. The log does not include the error status in your job details.

Your log snippet shows that accelerator is involved. Is this bpbkar log from a VMware backup? If so, what happens when you use an Exchange policy to back up the DAG?

Your job details show 9 hours sending data to PureDisk before the failure. Have you investigated this from the media server side? What happens if you back up to disk?

Highlighted

Re: file write failed (14) - Exchange DAG

ok other backups work normally on the media server.
My problem is related in isolation to the exchange backup via DAG.
When starting the backup, I checked the job details that the status "20/12/2018 20:18:44 - Info bpbkar (pid = 37684) INF - waiting for mount mutex ..." is for a long time running and then displays the error "file write failed (14)"

I am having difficulty locating the log regarding this error could they help me?

Tags (2)
Highlighted
Accepted Solution!

Re: file write failed (14) - Exchange DAG

If you are using an Exchange policy rather than a VMware policy, bpfis and bpbkar32 run on Exchange server nodes of the DAG. The Activity Monitor tells you which client runs each job. Make sure the bpfis and bpbkar log folders exist on the clients. Also the beds folder. Set the global logging level for each client to at least 3 and and the Windows client logging level to 2.

For each Exchange server, also specify an Exchange account in the client host properties, in accordance with the instructions in the NetBackup admin guide for Exchange.

If you can't see all the Exchange servers as clients in the NetBackup console, create a dummy MS-Windows policy for each of them. Setting properties on the DAG is not sufficient. At any given time, it resolves to one specific Exchange server.

Please specify the Exchange version and the specific NetBackup version.

View solution in original post

Highlighted
Accepted Solution!

Re: file write failed (14) - Exchange DAG

Thank you for your help. I tested the hosts on the servers and the problem was solved. I diagnosed that the problem was related to DNS, I checked the DNS entries of the DNS servers and noticed that the "reverse" was not configured on our media server (appliance 5230) after setting the reverse the problem was solved. Thank you and sorry for the delay.

View solution in original post