Exchange backup on disk failing with error code 84 and 87

[Varma_Chiluvuri]

error code 84 log

08/02/2014 22:24:24 - Info bpbrm (pid=4348) WINS8207 is the host to backup data from
08/02/2014 22:24:24 - Info bpbrm (pid=4348) reading file list from client
08/02/2014 22:24:44 - Info bpbrm (pid=4348) starting bpbkar32 on client
08/02/2014 22:27:01 - Info bpbkar32 (pid=9708) Backup started
08/02/2014 22:27:01 - Info bptm (pid=5004) start
08/02/2014 22:27:01 - Info bptm (pid=5004) using 262144 data buffer size
08/02/2014 22:27:01 - Info bptm (pid=5004) setting receive network buffer to 1049600 bytes
08/02/2014 22:27:01 - Info bptm (pid=5004) using 30 data buffers
08/02/2014 22:27:01 - Info bptm (pid=5004) start backup
08/02/2014 22:27:02 - Info bptm (pid=5004) backup child process is pid 4088.2476
08/02/2014 22:27:02 - Info bptm (pid=4088) start
08/02/2014 22:34:35 - Info nbjm (pid=9437218) starting backup job (jobid=2639324) for client WINS8207, policy MS_EXCHANGE_06, schedule Daily
08/02/2014 22:34:35 - estimated 46278500 kbytes needed
08/02/2014 22:34:35 - Info nbjm (pid=9437218) started backup (backupid=whqexchange_1407033275) job for client WINS8207, policy MS_EXCHANGE_06, schedule Daily on storage unit WIN_EXCHANGE_2010_AdvancedDisk_Logs
08/02/2014 22:34:36 - started process bpbrm (pid=4348)
08/02/2014 22:34:58 - connecting
08/02/2014 22:35:00 - connected; connect time: 0:00:00
08/02/2014 22:37:18 - begin writing
08/02/2014 23:43:38 - Critical bptm (pid=5004) image write failed: error 2060013: no more entries
08/02/2014 23:43:38 - Critical bptm (pid=5004) sts_close_handle failed: 2060017 system call failed
08/02/2014 23:43:39 - Error bptm (pid=5004) cannot write image to disk, Invalid argument
08/02/2014 23:43:39 - Info bptm (pid=5004) EXITING with status 84 <----------
08/02/2014 23:43:43 - Error bpbrm (pid=4348) cannot send mail to NB_Notify
08/02/2014 23:43:44 - Info bpbkar32 (pid=9708) done. status: 84: media write error
08/02/2014 23:54:00 - end writing; write time: 1:16:42
media write error  (84)

[Varma_Chiluvuri]

error code 87 log -- any suggestions

08/02/2014 18:24:45 - Info bpbrm (pid=4768) WHQS8204 is the host to backup data from
08/02/2014 18:24:45 - Info bpbrm (pid=4768) reading file list from client
08/02/2014 18:24:49 - Info bpbrm (pid=4768) starting bpbkar32 on client
08/02/2014 18:25:24 - Info bpbkar32 (pid=11576) Backup started
08/02/2014 18:25:24 - Info bptm (pid=4852) start
08/02/2014 18:25:24 - Info bptm (pid=4852) using 262144 data buffer size
08/02/2014 18:25:24 - Info bptm (pid=4852) setting receive network buffer to 1049600 bytes
08/02/2014 18:25:24 - Info bptm (pid=4852) using 30 data buffers
08/02/2014 18:25:24 - Info bptm (pid=4852) start backup
08/02/2014 18:25:25 - Info bptm (pid=4852) backup child process is pid 2600.2788
08/02/2014 18:25:25 - Info bptm (pid=2600) start
08/02/2014 18:34:56 - Info nbjm (pid=9437218) starting backup job (jobid=2638996) for client WHQS8204, policy MS_EXCHANGE_07, schedule Weekly
08/02/2014 18:34:56 - estimated 0 kbytes needed
08/02/2014 18:34:56 - Info nbjm (pid=9437218) started backup (backupid=whqexchange_1407018896) job for client WHQS8204, policy MS_EXCHANGE_07, schedule Weekly on storage unit WHQ_EXCHANGE_2010_AdvancedDisk
08/02/2014 18:34:56 - started process bpbrm (pid=4768)
08/02/2014 18:35:02 - connecting
08/02/2014 18:35:04 - connected; connect time: 0:00:00
08/02/2014 18:35:41 - begin writing
08/03/2014 01:40:01 - Info bpbrm (pid=4768) DB_BACKUP_STATUS is 0
08/03/2014 01:40:03 - Info bpbkar32 (pid=11576) 5000 entries sent to bpdbm
08/03/2014 01:40:04 - Info bpbkar32 (pid=11576) 10000 entries sent to bpdbm
08/03/2014 01:40:05 - Info bpbkar32 (pid=11576) 15000 entries sent to bpdbm
08/03/2014 01:40:05 - Info bptm (pid=4852) waited for full buffer 4212 times, delayed 59541 times
08/03/2014 01:43:11 - Critical bptm (pid=4852) sts_close_handle failed: 2060017 system call failed
08/03/2014 01:43:11 - Error bptm (pid=4852) cannot write image to disk, media close failed with status 2060017 
08/03/2014 01:43:19 - Info bptm (pid=4852) EXITING with status 87 <----------
08/03/2014 01:43:20 - Error bpbrm (pid=4768) cannot send mail to NB_Notify
08/03/2014 01:43:21 - Info bpbkar32 (pid=11576) done. status: 87: media close error
08/03/2014 01:53:37 - end writing; write time: 7:17:56
media close error  (87)

[Pangal]

Is this dedupe disk ??

[Varma_Chiluvuri]

Pangal, this is normal disk but after this backup is completed dedupe will start

[RiaanBadenhorst]

post

bpstulist -label WIN_EXCHANGE_2010_AdvancedDisk_Logs -U

[Marianne]

So, 2 different STU's with different errors:

Status 84 STU:
WIN_EXCHANGE_2010_AdvancedDisk_Logs

Status 87:
WHQ_EXCHANGE_2010_AdvancedDisk

Are these STUs connected to same or different media servers?

Have you enabled bptm log on media server(s)?

Which OS on media server(s)?
Which NBU version on media server(s)?

Status 87 backup seems to fail right at the end - after about 7 hours. 
Any firewall in the picture? Between client and media server? Or between media server and master?

[Varma_Chiluvuri]

@Marianne

Are these STUs connected to same or different media servers?

No, they are connected to same media server.

Have you enabled bptm log on media server(s)?

No, we dont have access to these servers.

Which OS on media server(s)?

Windows 2008

Status 87 backup seems to fail right at the end - after about 7 hours. 
Any firewall in the picture? Between client and media server? Or between media server and master?

There is no firewall, we have observed recently the backup is failing with 84 and 87 on the exchange backups intermittently, they have completed successfully for the last fewdays.

[Varma_Chiluvuri]

@Marianne 

My question here is if backup fails with error code 84 that suggests we have issue on tape, but in our scenario backup is writing to disk and failing with error code 84.

Recently 2 days back some backups failed with error code 129 due to lack of insufficient disk space.

I doubt 84 is also occuring due to lack of insufficient space . Does 129 relate with 84 ?

[Andy_Welburn]

They can both relate to insufficient disk space issues.

Checking online & reading between the lines it *seems* that a 129 will occur if the DSU is full at the start of the job & an 84 if the DSU fills during the backup ..... but I could be wrong!

[Marianne · Accepted solution]

Status 84 is a 'Media write error'. This can apply to disk or tape.
To troubleshoot, create bptm and bpdm log folders on all media servers (or as server owner(s) to create the folders under netbackup\logs).

For status 87, create bptm, bpdm and bpbrm folders on the media server(s).

You may want to have a look at KeepAlive settings (even with no firewall):

• HOWTO56221   Adjusting the TCP KeepAliveTime parameter