We were never able to satisfactorily resolve this issue, instead we chose to duplicate within each datacenter and complete all of the outstanding SLPs in that fashion.
Thanks for your advice and assistance, apologies for not replying sooner.
Hi Alun
Can you confirm you are looking for the differences between SLP controlled duplication within one site (which is working) and AIR replication between sites (which is not working)?
If nothing else has changed other than the re-platform, then I'd first be looking at firewall configurations (local windows firewall). How did you go about the replatform work (for both the master server cluster and media servers (i.e. what process)?
Have you used the nbstlutil command to determine what the state of the SLP managed image is?
David
Hi David,
I'm referring to SLP controlled duplication between media servers in the same physical location and also SLP controlled duplication between media servers in two physical locations (we don't use AIR).
The networking is in theory no different between the new servers in both datacenters, disabling the Windows firewall makes no difference to the success or failure of the SLP duplications.
New servers were built on new hardware with newer OSs and new IP addresses, once the old media servers were removed the new media servers were allocated the IP addresses from the old media servers.
The Master server cluster nodes were replaced by performing in place OS upgrades on the old nodes, adding the two new nodes into the cluster, installing NetBackup on them, failing over between each to confirm that they were all working as anticipated and then finally removing the old nodes form the cluster.
Alun
Can you please show us all text in Job Details of a failed duplication?
This will tell us which processes and PIDs on master and media servers to troubleshoot.
If you do not want to display hostnames, please replace real names with generic names, e.g.
master, media1, media2.
Ensure that log folders exist on master: admin (I don't think more legacy logs are needed on the master)
On media servers : bpbrm, bptm, bpdm.
Increase logging level to 3 (level 3 is sufficient for this forum; if you log a call with Veritas Support, they will ask for level 5).
Depending on what we see in Job Details, we will know which logs to check.
Job Details for two duplications are attached, Job01 reported a different error from Job02 (and Job03 which I omitted).
The errors reported in Job02 are caused by me terminating the bpduplicate.exe processes on the master server after almost 60 minutes of inactivity in the job log (no conflicting jobs are running that would prevent the duplications from accessing their requested tapes or drives).
This is the behaviour that is repeatable whenever SLP secondary operations are enabled that require media servers in different datacenters.
