• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 27 subscribers
  • Views 12854 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Replication - GetResponse Timed Out

pancraziop
over 6 years ago

When attempting to replicate from core1 to core2 the replication is failing.   Both cores are running Rapid Recovery 6.1.1.137

Error
GetResponse timed out
GetResponse timed out

The operation has timed out
GetResponse timed out
GetResponse timed out

The operation has timed out
 
I've completely rebuilt core2.   Server 2012 R2 - removed respository and setup new.   Moved the server to a different network location for better network throughput.  
 
What other information can I provide?
 
Phil
Parents
  • 0 over 6 years ago
    That looks to me like a straight timeout issue. That generally means that enough packets were dropped that the job couldn't continue and timed out. Usually that means networking connectivity issues, WAN stability, or possibly even NIC issues on one or both of the machines. One workaround in the software would be to try the changes in this KB - support.quest.com/.../121363.

    To isolate the issue it may be worth throwing Wireshark on both cores and then running a capture of all traffic on port 8006 to see what's happening to the packets. If you have lots of retransmits or out of order packets, that could definitely point to what's going on.
Reply
  • 0 over 6 years ago
    That looks to me like a straight timeout issue. That generally means that enough packets were dropped that the job couldn't continue and timed out. Usually that means networking connectivity issues, WAN stability, or possibly even NIC issues on one or both of the machines. One workaround in the software would be to try the changes in this KB - support.quest.com/.../121363.

    To isolate the issue it may be worth throwing Wireshark on both cores and then running a capture of all traffic on port 8006 to see what's happening to the packets. If you have lots of retransmits or out of order packets, that could definitely point to what's going on.
Children
No Data