06-08-2015 04:31 AM
Hi all,
Have tried looking for the answer but am struggling to find consistent information. We are using BackupExec 2014.
I am trying to backup the VMs on an ESXi 5.0 host. I have configured the firewall to allow port 902, but am still unable to add the server. Are any other ports required?
This ESX host does belong to a vCenter, but I only want to directly connect as I will never have the need to backup anything else in that vCenter.
Many thanks
James
Solved! Go to Solution.
06-11-2015 07:54 AM
Hi all,
Just to update the thread. In the end I got the network team to help trace the traffic.
We found we needed port 443 and 902 to get this working properly.
Cheers
06-08-2015 04:48 AM
...here is a TN listing the ports BE uses:
https://support.symantec.com/en_US/article.TECH49563.html
Thanks!
06-08-2015 04:52 AM
Are you able to ping from the BE server to the ESX host and vice-versa ? Using both IP address and name ?
Are you using the ESX's root account to add the hypervisor ?
06-08-2015 05:20 AM
Thanks CraigV but that document doesnt mention VMware anywhere.
VJware, I cannot ping, but we do not allow ping through. Are any other ports required to 902? Yes we are using the root account.
Thanks
James
06-08-2015 05:23 AM
06-08-2015 05:35 AM
Thanks CraigV, those instructions are for ESX 3 though which is ancient. I have successfully added multiple ESXi 5+ hosts without the need to configure anything on the host itself.
I am just trying to find out what configuration is needed between the Backup exec server and the ESXi host so I can ask our network team to configure the firewall between accordingly.
06-08-2015 05:42 AM
Hi, If ping is not allowed check the port 80, 443 using telnet. VMWare port is mentioned on CraigV document. Please co-ordinate with your team and try to temporary allow ping for find out the root cause. How many ESX/ESXi servers you are included in backup server? Is other VM backup is working fine? Regards, Yogesh Patil
06-11-2015 07:54 AM
Hi all,
Just to update the thread. In the end I got the network team to help trace the traffic.
We found we needed port 443 and 902 to get this working properly.
Cheers