AIR error 84 during Replication.

[CSG3060]

I have some issues with AIR. OS is W2K8-R2 and W2K12-R2 NBU version 7.5.5 and 7.6.01 hostA.domain1(Master&Media server) > hostB.domain1(Master&Media server) AIR OK hostA.domain1 > hostC.domain2 (Dedicated Media server) AIR error 84 during replication on hostA. hostB.domain1 > hostC.domain2 (Dedicated Media server) AIR error 84 during replication on hostB. I have a feeling it is the different Windows domains which is giving the error. Is is some caveats when using AIR between 2 different Windows Domains.

[Mark_Solutions]

The domain should have no effect on NetBackup AIR - only TCPIP really matters so just make sure they resolve correctly to the correct IP addresses (both ways) and ensure that you have entered the de-dupe passwords correctly for each pool

[CSG3060]

Quick reply, Mark, thanks. I'd tried the DNS and it was OK booth ways. When you add the Replication Target you add the server and the credentials for the MSDP. I persume you wouldn't get connection if the credentials didn't match.

[CSG3060]

Here is the output from the activity monitor: " 02-04-2014 09:35:36 - requesting resource LCM_*Remote*Master* 02-04-2014 09:35:36 - granted resource LCM_*Remote*Master* 02-04-2014 09:35:37 - started process RUNCMD (2456) 02-04-2014 09:35:38 - Info nbreplicate(pid=2456) Suspend window close behavior is not supported for nbreplicate 02-04-2014 09:35:38 - Info nbreplicate(pid=2456) window close behavior: Continue processing the current image 02-04-2014 09:35:39 - requesting resource @aaaab 02-04-2014 09:35:39 - reserving resource @aaaab 02-04-2014 09:35:39 - reserved resource @aaaab 02-04-2014 09:35:39 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=C02-D2P-C02-ADV-G;Path=PureDiskVolume;StorageServer=hostA.domain1;MediaServer=hostA.domain1 02-04-2014 09:35:41 - Info bpdm(pid=7184) started 02-04-2014 09:35:41 - started process bpdm (7184) 02-04-2014 09:35:42 - Info hostA.domain1(pid=7184) Using OpenStorage to replicate backup id hostA.domain1_1396423687, media id @aaaab, storage server hostA.domain1, disk volume PureDiskVolume 02-04-2014 09:35:42 - Info hostA.domain1(pid=7184) Replicating images to target storage server hostC.domain2, disk volume PureDiskVolume 02-04-2014 09:41:43 - Critical bpdm(pid=7184) Storage Server Error: (Storage server: PureDisk:hostA.domain1) 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 02-04-2014 09:41:43 - Error bpdm(pid=7184) wait failed: error 150 02-04-2014 09:41:43 - Error bpdm(pid=7184) cancel failed: error 2060001: one or more invalid arguments 02-04-2014 09:41:43 - Error bpdm(pid=7184) copy cancel failed: error 174 02-04-2014 09:41:43 - Info hostA.domain1(pid=7184) StorageServer=PureDisk:hostA.domain1; Report=PDDO Stats for (hostA.domain1): scanned: 4 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled 02-04-2014 09:41:43 - Error nbreplicate(pid=2456) ReplicationJob::Replicate: Replication failed for backup id hostA.domain1_1396423687: media write error (84) 02-04-2014 09:41:43Replicate failed for backup id hostA.domain1_1396423687 with status 84 02-04-2014 09:41:43 - end operation no images were successfully processed(191 "

[Mark_Solutions]

ok - work through this one to see if it helps .. if nothing else the logs may throw some light on things:

http://www.symantec.com/docs/HOWTO89078

[watsons · Accepted solution]

As the job details pointed out:

  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

Please have a look into this log in your source MSDP server:

/<storage path>/log/spad/replication.log

This will give us more details of that error message, and if needed, other MSDP logs.

[CSG3060]

Hi Mark and Watsons. You both showed the way to the solution, but Watsons was a little more excact according to the name of the logfile. The log mentioned "unable to resolve the hostname". The hostname mentioned was WITHOUT SUFFIX. I use FQDN everywhere so it seems like a bug in the communication between Master server (hostC1.domain2) and mediaserver (hostC.domain2). I cannot se where the hosts name without suffix should come from. Watsons gets the "solved" in close competition with Mark.

[CSG3060]

I missed to mention that I used the HOSTS file to resolve the host.