cancel
Showing results for 
Search instead for 
Did you mean: 

AIR replication is failing

Hi All,

 

I have master server on windows 2008 datacentre x64 and two 5230 Netbackup appliances.

Main Site : One windows master server and one Netbackup 5230 appliance as media server

DR site : One Netbackup 5230 appliace as media server.

 

I am configuring AIR between main site windows master server and DR site Netbackup Appliance 5230 as master server.

 

I have configured the aAIR as per standard configuration. I am facing an issue during replication. Please see the below replication job detail and help me. Thank you...

==========================================================================================================

Logs :

9/10/2014 2:43:31 PM - requesting resource LCM_*Remote*Master*:msdp_sql_dc_to_dr_2_week
9/10/2014 2:43:31 PM - granted resource LCM_*Remote*Master*:msdp_sql_dc_to_dr_2_week
9/10/2014 2:43:31 PM - Info nbreplicate(pid=6296) Suspend window close behavior is not supported for nbreplicate    
9/10/2014 2:43:31 PM - Info nbreplicate(pid=6296) window close behavior: Continue processing the current image     
9/10/2014 2:43:31 PM - started process RUNCMD (6296)
9/10/2014 2:43:32 PM - requesting resource @aaaae
9/10/2014 2:43:32 PM - reserving resource @aaaae
9/10/2014 2:43:32 PM - reserved resource @aaaae
9/10/2014 2:43:32 PM - granted resource MediaID=@aaaae;DiskVolume=PureDiskVolume;DiskPool=dp_disk_dc-nbmedia01;Path=PureDiskVolume;StorageServer=dc-nbmedia01;MediaServer=dc-nbmedia01
9/10/2014 2:47:39 PM - Error nbreplicate(pid=6296) ReplicationJob::Replicate: Replication failed for backup id sqlf02_1410349007: media write error (84)  
9/10/2014 2:47:39 PMReplicate failed for backup id sqlf02_1410349007 with status 84
9/10/2014 2:47:39 PM - end operation
9/10/2014 2:48:31 PM - Info bpdm(pid=206039) started            
9/10/2014 2:48:31 PM - started process bpdm (206039)
9/10/2014 2:48:34 PM - Info dc-nbmedia01(pid=206039) StorageServer=PureDisk:dc-nbmedia01; Report=PDDO Stats for (dc-nbmedia01): scanned: 4 KB, CR sent: 1 KB, CR sent over FC: 0 KB, dedup: 75.0%, cache disabled
9/10/2014 2:48:35 PM - Info dc-nbmedia01(pid=206039) Using OpenStorage to replicate backup id sqlf02_1410349007, media id @aaaae, storage server dc-nbmedia01, disk volume PureDiskVolume
9/10/2014 2:48:35 PM - Info dc-nbmedia01(pid=206039) Replicating images to target storage server dr-nbmaster, disk volume PureDiskVolume   
9/10/2014 2:52:35 PM - Critical bpdm(pid=206039) Storage Server Error: (Storage server: PureDisk:dc-nbmedia01) async_get_job_status: 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
9/10/2014 2:52:35 PM - Error bpdm(pid=206039) wait failed: error 150         
9/10/2014 2:52:35 PM - Error bpdm(pid=206039) <async> cancel failed: error 2060001: one or more invalid arguments   
9/10/2014 2:52:35 PM - Error bpdm(pid=206039) copy cancel failed: error 174        
9/10/2014 2:52:35 PM - Info dc-nbmedia01(pid=206039) StorageServer=PureDisk:dc-nbmedia01; Report=PDDO Stats for (dc-nbmedia01): scanned: 4 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
no images were successfully processed(191)

 

4 Replies

Error: Replication started

Error:

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

Check the following logs on the source 5230 for more info:

/usr/openv/netbackup/logs/bpdm/log.091014
/disk/log/spad/replication.log


 

As watsons says the

As watsons says the replication.log should have the cluses in .. often a name resolution issue and in a orevious similar case it was down to not being able to resolve both the short and FQDN of the target server .. so check hosts files / DNS etc. to ake sure you have short and FQDN resolution both ways between your servers.

Getting this error myself.

Getting this error myself. Were you able to locate a solution? What's odd is that sometimes, it does run and completes the import to the dr master, and duplicate to the remote storage, but only about once out of 20 attempts.

 

2/6/2015 9:03:21 AM - requesting resource LCM_*Remote*Master*
2/6/2015 9:03:22 AM - Info nbreplicate(pid=7908) Suspend window close behavior is not supported for nbreplicate   
2/6/2015 9:03:22 AM - Info nbreplicate(pid=7908) window close behavior: Continue processing the current image    
2/6/2015 9:03:22 AM - granted resource LCM_*Remote*Master*
2/6/2015 9:03:22 AM - started process RUNCMD (7908)
2/6/2015 9:03:22 AM - requesting resource @aaabw
2/6/2015 9:03:22 AM - reserving resource @aaabw
2/6/2015 9:03:24 AM - reserved resource @aaabw
2/6/2015 9:03:24 AM - granted resource MediaID=@aaabw;DiskVolume=PDC4200_DDSU1_DR;DiskPool=PDC4200_DP1_DR;Path=PDC4200_DDSU1_DR;StorageServ...
2/6/2015 9:03:25 AM - Info bpdm(pid=34928) started           
2/6/2015 9:03:25 AM - started process bpdm (34928)
2/6/2015 9:03:54 AM - Error nbreplicate(pid=7908) ReplicationJob::Replicate: Replication failed for backup id PDC00IESW101W_1423160571: media manager - system error occurred (174)
2/6/2015 9:03:54 AMReplicate failed for backup id PDC00IESW101W_1423160571 with status 174
2/6/2015 9:03:54 AM - end operation
no images were successfully processed(191)

 

 

I'm not sure if the author

I'm not sure if the author got his issue resolved, but I did. My master server was running a DataDomain OST pluging older than 2.6. I knew it was running an older version, but since my master server is NOT a media server, I did not think that this would come into play. But, apparently with AIR (and possibbly other types of duplicatoon) it made a big difference.