Skip to main content
Question

Backup Exec External Data Connector


Forum|alt.badge.img+14

Greetings

I’m busy testing the EDC to migrate from Backup Exec to Commvault.
I must stress that I”m using a trial license of Backup Exec and Commvault to test this, so this may be causing my issue. 

When I install and configure the EDC on the BE Master Server, I don’t get the option to configure the connection settings to the BE server as listed below.
It auto configs with no options to edit any settings.

https://documentation.commvault.com/2024/expert/discover_and_migrate_external_data_connector.html

 

I simply get the below with no options to configure the instance options:

 

 

As a result, the Discovery fails in connecting to BE.

I tried to then create the xml answer file using the below example that could be used to run the discover. The file doesn’t create.

 

CVForeignHandler –collectdata –vendor 13 –user "bsmith" –password "be348n2" -vm "Instance001" –cn "client1"

 

What I did note is that when running the edc_backupexec.bat command from the cloud option, I get the below errors in the files created:

 

 

I suspect that SQL connectivity is the issue in all the above. However, I have sysadmin roles with the accounts I”m using.

Any ideas on what is happening here?

Thanks,

Mauro

2 replies

Damian Andre
Vaulter
Forum|alt.badge.img+23

Hi Mauro,

It does look like a SQL issue. Is there a firewall or separate network segment between the target BE server and the Commvault install?

If a separate network segment, then discovery of SQL will fail (it uses UDP broadcasts) - you might have to define a static TCP port (1433) using SQL management studio configuration manager - make sure the firewall has allowed this port as well.

I dont think its a permission issue - it having trouble locating and connecting to the right port.


Forum|alt.badge.img+14
  • Author
  • Byte
  • 101 replies
  • April 30, 2024
Damian Andre wrote:

Hi Mauro,

It does look like a SQL issue. Is there a firewall or separate network segment between the target BE server and the Commvault install?

If a separate network segment, then discovery of SQL will fail (it uses UDP broadcasts) - you might have to define a static TCP port (1433) using SQL management studio configuration manager - make sure the firewall has allowed this port as well.

I dont think its a permission issue - it having trouble locating and connecting to the right port.

Thanks so much.

I”m simulating this all on the same network in my lab, so this shouldn’t be an issue. I’ll try force the static port as suggested and try again.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings