12-10-2018 04:30 AM - edited 12-10-2018 04:30 AM
We got may errors with status code 191, with nbstlutil.exe we cancel the -backupid, later we see that the JOB is finaly succeeded. How can we get rid of these errors?
10-dec-2018 13:15:09 - requesting resource LCM_*Remote*Master*
10-dec-2018 13:15:09 - granted resource LCM_*Remote*Master*
10-dec-2018 13:15:10 - Info nbreplicate (pid=12936) Suspend window close behavior is not supported for nbreplicate
10-dec-2018 13:15:10 - Info nbreplicate (pid=12936) window close behavior: Continue processing the current image
10-dec-2018 13:15:10 - started process RUNCMD (pid=12936)
10-dec-2018 13:15:10 - requesting resource @aaaab
10-dec-2018 13:15:10 - reserving resource @aaaab
10-dec-2018 13:15:10 - resource @aaaab reserved
10-dec-2018 13:15:10 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dp_disk_bs003;Path=PureDiskVolume;StorageServer=bs003;MediaServer=bs003
10-dec-2018 13:25:46 - Error nbreplicate (pid=12936) ReplicationJob::Replicate: Replication failed for backup id bs001.wsrl.local_1544432559: media write error (84)
10-dec-2018 13:25:46 - Replicate failed for backup id bs001.wsrl.local_1544432559 with status 84
10-dec-2018 14:14:13 - Info bpdm (pid=215986) started
10-dec-2018 14:14:13 - started process bpdm (pid=215986)
10-dec-2018 14:14:14 - Info bs003 (pid=215986) Using OpenStorage to replicate backup id bs001.wsrl.local_1544432559, media id @aaaab, storage server bs003, disk volume PureDiskVolume
10-dec-2018 14:14:15 - Info bs003 (pid=215986) Replicating images to target storage server bs004, disk volume PureDiskVolume
10-dec-2018 14:24:45 - Critical bpdm (pid=215986) Storage Server Error: (Storage server: PureDisk:bs003) async_get_job_status: Replication started but failed to complete successfully: __sosend: _crStreamWrite failed: broken pipe. Look at the replication logs on the source storage server for more information. V-454-105
10-dec-2018 14:24:45 - Error bpdm (pid=215986) wait failed: error 150
10-dec-2018 14:24:45 - Error bpdm (pid=215986) <async> cancel failed: error 2060001: one or more invalid arguments
10-dec-2018 14:24:45 - Error bpdm (pid=215986) copy cancel failed: error 174
10-dec-2018 14:24:46 - Info bs003 (pid=215986) StorageServer=PureDisk:bs003; Report=PDDO Stats for (bs003): scanned: 4 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
no images were successfully processed (191)
12-11-2018 11:28 PM
bpdm & replication
(/<storage path>/log/spad/replication.log)
xxx[PID]<32> and xxx PID <16> and
Replication started but failed to complete successfully: Error occured during replication. Look at the replication logs on the source storage server for more information. V-454-105
12-11-2018 11:36 PM
I see the following in Job Details:
Replication started but failed to complete successfully: __sosend: _crStreamWrite failed: broken pipe. Look at the replication logs on the source storage server for more information.
The moment I see 'broken pipe', it says to me that there was a break in network comms.
Get your network team to investigate and monitor connections.