Quantcast
Channel: Symantec Connect - Backup and Recovery - 讨论
Viewing all articles
Browse latest Browse all 3749

Air Replication Job Fails with Status Code 84 media write error

$
0
0
我需要解决方案

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


Viewing all articles
Browse latest Browse all 3749

Trending Articles