Re: SQL servers Backup failing: Cannot connect to Media Agent on system (341 Views)
Reply
Occasional Contributor
ed_for
Posts: 7
Registered: ‎11-07-2013
Message 1 of 4 (375 Views)

SQL servers Backup failing: Cannot connect to Media Agent on system

 

 

Hello,

 

My SQL backups are failing randomly with error:

 

[Critical] From: BDA-NET@MySql.mydomain.local "(DEFAULT)"  Time: 17/11/2013 20:16:30

 

      Cannot connect to Media Agent on system DPserver.mydomain.local, port 65032 (IPC Cannot Connect) => aborting.

 

 

[Critical] From: OB2BAR_MyApp@MySql.mydomain.local"(DEFAULT)"  Time: 17/11/2013 20:16:30

 

      Unexpected close reading NET message => aborting.

 

 

[Major] From: OB2BAR_ MyApp@MySql.mydomain.local "(DEFAULT)"  Time: 17/11/2013 20:16:30

 

      Aborting connection to BSM. Abort code -2.

 

 

the error happens randomly on different servers. Also the Ports in the error vary from 65030 to 65040.

 

Any Ideas?

 

 

Thanks!

 

 

HP Expert
Bob_Clark
Posts: 1,473
Registered: ‎08-14-2013
Message 2 of 4 (361 Views)

Re: SQL servers Backup failing: Cannot connect to Media Agent on system

Normally, the error

 

"  Cannot connect to Media Agent on system DPserver.mydomain.local"

 

where it references a port number, in your case 'port 65032' means there is a firewall between the disk agent and the Media agent.  Data Protector uses Dynamic Port Addressing, which means that after the initial contact on port 5555 between the disk agent and the media agent, then Data Protector will try to use any available port

 

The firewall administrator needs to set a rule to allow Data Protector a range of ports to pass backup data through, and on the Data Protector disk agent and media agent, you must add this line to the 'omnirc' file

 

OB2PORTRANGE=[number-[number]

 

where [number-[number] represents the range of ports allowed by the firewall rule.  So, for example, suppose that you are allowed to use ports 6500 through 6550, the line would read

 

OB2PORTRANGE=6500-6550

 

Save the file.  On Windows clients stop and restart the Data Protector INET service

 

In the GUI, if you click on 'Help -> Help Topics', you can search for 'portrange' to get more information

 

However,  if you are getting these errors randomly, then it is ouside the normal realm of Data Protector.  It sould be that you have several firewalled systemss trying to backup to a media agent that does not have sufficient portrange, for that you can just inscrease the portrange on the Media Agent

 

If you are not using a portrange, if there are no firewalls involved, then something else is blocking that TCP port, and is probably more of a system issue that a Data Protector issue

Occasional Contributor
ed_for
Posts: 7
Registered: ‎11-07-2013
Message 3 of 4 (348 Views)

Re: SQL servers Backup failing: Cannot connect to Media Agent on system

 

 


 

Hi,

 

Thanks for your reply.

I do not have the OB2PORTRANGE set on DP.

 

But the firwall has a rule to allow limit to ports: 65000-65030

it explaim the errors.

 

In order  increase the port Range on the firewall, what is the is the default port range in DP 7.0?

 

the help topics are not specific. And the omnir file metion:

#OB2PORTRANGE=65000-66000

 

is that correct?

 

Thanks

HP Expert
Bob_Clark
Posts: 1,473
Registered: ‎08-14-2013
Message 4 of 4 (341 Views)

Re: SQL servers Backup failing: Cannot connect to Media Agent on system

[ Edited ]

There is no 'Default Portrange' for DP 7, or any prior or subsequent version.

 

However, in your 'omnirc' file, you are showing this

 

#OB2PORTRANGE=65000-66000

 

The # sign means this is commented out.  Edit the 'omnirc' file to remove the # sign, set the range to what your firewall rule specifies,

 

OB2PORTRANGE=65000-65030

 

 save the file, if on Windows, stop and restart the DP INET service

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.