RDA Library error code: 39, means there's a communication issue between the Server, Client and DR. There are different reasons for this but usually falls on one of these two branches:
1. Network.
2. RDA Library.
FIX:
Upgrade to minimum version of netvault 12.2.0.18 where RDA plugin bug QS-1870 fix was applied.
This fix was introduced because of difficulty in manually modifying “TcpMaxDataRetransmissions” on windows servers after windows 2008.
Workaround:
Network:
A . If using Windows, the TcpMaxDataRetransmissions can be increased from the default: 5, to 15 (which is the default on Linux). By creating or modifying the following key on the registry:
B. If using Jumbo Frames, confirm the MTU is the same across all devices: Server, Client, DR, Switch. Different switches may have different limits. In order to confirm Jumbo Frames a ping can be done without defragmentation and specifying the Jumbo Frame payload. If this fails, something may be wrong with the Jumbo Frames. Examples below assuming a 9000 Jumbo Frame:
For Windows: ping -S <source_address> -f -l 9000 <destination_address>
For Linux: ping -I <source_interface> -M do -s 9000 <destination_address>
RDA Library
As of NV 10.0.5.x the RDA library is included as part of the platform installation. If there's an improper or corrupt NetVault installation, this could be another cause for this error and reinstalling NV would be another possible solution.
The DR OS version, whenever possible should always match the RDS Plugin on the client. An older RDS Plugin may still work with a newer DR OS. A newer RDS Plugin than the DR OS would give some issues.
