Air Replication Job Fails with Status Code 84 media write error

[rsakimoto]

Hi,

Im getting error on my replication job with status 84. Is it because the replicating server nbu6 encountered a disk failed on its EVA storage? Although it was replaced already and status now is still levelling. Maybe from the source media server - nbu4, when trying to replicate to other site nbu6 it cannot fully complete cause of the replaced disk currently levelling?

4/1/2015 5:48:04 AM - Info bpdm(pid=5848) started           
4/1/2015 5:48:04 AM - started process bpdm (5848)
4/1/2015 5:48:05 AM - Info nbu4(pid=5848) Using OpenStorage to replicate backup id BS1030_1427803200, media id @aaaap, storage server nbu4, disk volume PureDiskVolume
4/1/2015 5:48:05 AM - Info nbu4(pid=5848) Replicating images to target storage server nbu6, disk volume PureDiskVolume  
4/1/2015 5:49:06 AM - Critical bpdm(pid=5848) Storage Server Error: (Storage server: PureDisk:nbu4) async_get_job_status: Replication started but failed to complete successfully:  __sosend: _crStreamWrite failed to send crc: connection reset by peer. Refer to the replication logs on the source storage server for more information. V-454-105
4/1/2015 5:49:06 AM - Error bpdm(pid=5848) wait failed: error 2060014        
4/1/2015 5:49:06 AM - Error bpdm(pid=5848) <async> cancel failed: error 2060001: one or more invalid arguments  
4/1/2015 5:49:06 AM - Error bpdm(pid=5848) copy cancel failed: error 2060001       
4/1/2015 5:49:06 AM - Info nbu4(pid=5848) StorageServer=PureDisk:nbu4; Report=PDDO Stats for (nbu4): scanned: 4 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%
4/1/2015 5:49:07 AM - Info bpdm(pid=6184) started           
4/1/2015 5:49:07 AM - started process bpdm (6184)

Thanks and Regards

[RiaanBadenhorst]

Hi,

You need to check if the nbu6 MSDP is working correctly. Try run a backup to it from a client in its domain.

You can verify if the deduplication processes spad and spoold are running.

You can also run nbdevquery -listdp -stype PureDisk -U on nbu6's to see if the pool is shown as UP.

If the pool is up and can be written to then the issue could be related to networking.

[rsakimoto · Accepted solution]

Hi Riaan,

I have checked msdp nbu6 and disk pool is UP state. I tried to run a clioent backup but failed. No issue with network too.I suspected based on the event logs that even some of the backups (on disk) failed with status 83 and thats when one of the disk in EVA storage failed. Somehow it affected the backup jobs of our media server which replication job failed too. I just restarted netbackup services and restarted the media server nbu6. After which replication jobs continued successfully. Thanks for the suggestions.

[RiaanBadenhorst]

Glad its working.