Unsolved
This post is more than 5 years old
1 Rookie
•
48 Posts
0
5575
March 31st, 2017 08:00
Avamar managed file replication failing with error Replication failed: could not open connection to dest DDR
avtar FATAL <10608>: Replication failed: could not open connection to dest DDR G3PPTS1004-mgmt.1dc.com, dest LSU: avamar-1479479996, handle: -1, DDR result code: 5037, desc: illegal operation (Log #2) 2017-03-28 14:47:23 avtar FATAL <40009>: DDR encountered errors. (Log #2) 2017-03-28 14:47:23 avtar Error <6655>: Replicate interrupted. (Log #2) 2017/03/28-18:47:23.84852 avtar DEBUG-INTERNAL ERROR <0001> assert error (result == MSG_ERR_NONE), /local/jenkins/workspace/client_HarmonySP1_SLES11-64/abs2/work/src/avtar/ade/adelib/interfaceade.cpp line 396 (Log #2)
*********** /usr/local/avamar/var/client/MOD-1490726335021#4-1008-Replicate-avtar.log ***********
Log #1: avtar log 2017-03-28 14:46:16 EDT [7.2.101-32 Linux-x86_64]
2017-03-28 14:46:16 avtar Info <5008>: Logging to /usr/local/avamar/var/client/MOD-1490726335021#4-1008-Replicate-avtar.log
2017-03-28 14:46:16 avtar Info <5551>: Command Line: /usr/local/avamar/bin/avtar.bin --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --sysdir=/usr/local/avamar/etc --sysdir=/usr/local/avamar/etc/client --bindir=/usr/local/avamar/bin --vardir=/usr/local/avamar/var/client --ctlcallport=55471 --ctlinterface=1008-MOD-1490726335021#4 --replicate --logfile=/usr/local/avamar/var/client/MOD-1490726335021#4-1008-Replicate-avtar.log
END avtar log 2017-03-28 14:46:16 EDT (0 warnings, 0 errors, 0 fatal errors)
We have dedicated bond2 created in source and destination avamar. the job completed with error code 10020.
GbAustin
4 Posts
0
April 26th, 2017 09:00
I'm having the same issue. Was any resolution found?
lpphiggp
1 Rookie
•
53 Posts
0
August 30th, 2017 10:00
Same here. I've had EMC looking into for over a week, so far, no solutions. In my case, it's intermittent, and affects two different sources talking to a single destination.
All are Avamar/DataDomain integrated solutions running 7.2.1-32 and 5.6.1.0.
lpphiggp
1 Rookie
•
53 Posts
0
September 6th, 2017 07:00
I think my issue is solved, I didn't have a virtual/bonded interface on my target datadomain, the replication ports were just separate interfaces. This doesn't work well with 7.2.1-32 or older. As a test I shut one of the two interfaces down and modified DNS to point to just the one interface, and I got no more errors for replication.
I see yours are bonded but it might help if on the source, you enter the target's IP and hostname in the hosts file and make a static route.
subranshu
1 Message
0
October 6th, 2017 03:00
Can you give the exact steps to troubleshoot this issue
GbAustin
4 Posts
0
October 6th, 2017 05:00
My issue was related to an avamar backup image that was written to DD but was corrupted. So when Avamar instructs DD to replicate that backup image/file, it errors out with that code.
It is difficult to narrow down the exact backup image that is corrupt, but there's two options here: 1) comb through the logs to find what client's backups are being replicated at time of faillure, note the name, remove the client from the replication scope, rerun replication, if it fails again, repeat the procedure and keep a running list of clients that fail until the replication job succeeds. Then create a separate replication job that just has the failed servers, and narrow the data range of the replication scope until you find the backup image that is causing the issue. Likely, if there are multiple servers with this issue, the failures will trace back to the same date/time. Once you have the Avamar backup images identified, you can delete it from Avamar. I'm not entirely sure if that removes the image from DD, so if the backup image is sizable, you may want to engage EMC support to dig into the array to remove the file.
ionthegeek
2 Intern
•
2K Posts
0
May 28th, 2018 10:00
The message shown is a generic message. I'd recommend working with support.