Dear all,
i have SQL Server 2012 running , ive created a MSQL database for the Veeam, however after trying to connect to this MSQL while installing it keep giving me error !
opend ports are ?
Unfortunately it will be, because it does not include the ID of support case with debug logs attached. You must include one when posting about any technical issue, or your topic will be removed, as explained when you click New Topic... in big red fond, really hard to miss, and as such can only be ignored purposely, really...
Without seeing the debug logs, we cannot say more than you can read yourself in the error message (there is an invalid connection string to your SQL server).
We will likely need a setup log in this case, our support engineers will instruct you how to collect one once you open a case.
According to your case I can see that our engineer is responding to your emails and is trying to arrange a remote WebEx session to troubleshoot it. Please continue working on your issue with our support team.
thank you Vitaliy,
a questions ? what ports need to be open on the firewall for Veeam to connect to the database SQL ?
i've already opend the below ports:
TCP 135 - SQL Transact Debugger/RPC
TCP 1433 - SQL Server Default Instance
TCP 1434 - SQL Server Admin Connection
TCP 2382 - SQL Server Browser
TCP 2383 - SQL Analysis Services
TCP 4022 - SQL Service Broker
UDP 1434 - SQL Server Browser Multicast Response
Note : if i disable the firewall on the SQL server it works, so it firewalling problems now !
waiting for the support is taking long,
can you please provide me the ports numbers that needs to be open on the SQL server to connect the Database ? in the mean while my SQL server firewall is off and i dont want to keep it that way !
Julien, I believe you should open the same ports as it is required for SQL Management Studio to connect to the SQL Server. BTW, what about Named Pipes (139/445) traffic?
Vitaliy S. wrote:Julien, I believe you should open the same ports as it is required for SQL Management Studio to connect to the SQL Server. BTW, what about Named Pipes (139/445) traffic?
those are already open
the SQL ports as wel,
i beleive V7 needs other ports than the normal ones?
According to the users, in case of SQL 2012 some additional steps might be required in order to allow remote connection. These steps include the following:
1) Right-click on TCP/IP and select Properties.
2) Verify that, under IP2, the IP Address is set to the computer's IP address on the local subnet.
3) Scroll down to IPAll.
4) Make sure that TCP Dynamic Ports is blank. (Mine was set to some 5-digit port number.)
5) Make sure that TCP Port is set to 1433. (Mine was blank.)
v.Eremin wrote:According to the users, in case of SQL 2012 some additional steps might be required in order to allow remote connection. These steps include the following:
1) Right-click on TCP/IP and select Properties.
2) Verify that, under IP2, the IP Address is set to the computer's IP address on the local subnet.
3) Scroll down to IPAll.
4) Make sure that TCP Dynamic Ports is blank. (Mine was set to some 5-digit port number.)
5) Make sure that TCP Port is set to 1433. (Mine was blank.)
Thanks.
Thank you Erwin,
those ports and configuration where fine however i've noticed Veeam needs ports 9392, 9393 i think those ports are clients one!
i managed to find those ports failler connection from the netstat !
i've opend those two ports and my issues is fixed
for those who out there may face this issue , please make sure those two ports are open !
Thank you Erwin,
those ports and configuration where fine however i've noticed Veeam needs ports 9392, 9393 i think those ports are clients one!
i managed to find those ports failler connection from the netstat !
i've opend those two ports and my issues is fixed
for those who out there may face this issue , please make sure those two ports are open !
Yep, those are basic ports used by the Veeam Backup service and Veeam Catalog service and they are specified during product installation, in the setup wizard.
foggy wrote:Yep, those are basic ports used by the Veeam Backup service and Veeam Catalog service and they are specified during product installation, in the setup wizard.
while installing Veeam to connect to SQL you need to have those ports first open, otherwise you won't be able to pas the installation connection to the SQL
jamerson wrote:
while installing Veeam to connect to SQL you need to have those ports first open, otherwise you won't be able to pas the installation connection to the SQL
thank you for your confirmation, all is working fine on my lab now!
the last questions how can i save the configuration to the SQL rather than local C:\Config ?
i've checked the option to change the location but i can't find a way to connect to the SQL,
Veeam B&R stores its configuration in the SQL database, in addition to this, it dumps the backup of the configuration to the folder you have mentioned.
Thank you so much Vitaliy,
does it means i can also save VM's Snapshots to the SQL rather than another Partition ?
also when i tried to add the Vsphere server it pop's with CLHelp Root account even i still keep getting error can't connect to the Vsphere on Port 443 !
jamerson wrote:does it means i can also save VM's Snapshots to the SQL rather than another Partition ?
No, snapshots are not backups, besides backups are not stored in the SQL Server database. VM backups are saved into your repositories.
Are you adding vCenter Server or standalone host? How are you doing it? Are you able to connect to your vSphere Server from the same machine via vSphere Client?
Vitaliy S. wrote:Julien,
No, snapshots are not backups, besides backups are not stored in the SQL Server database. VM backups are saved into your repositories.
Are you adding vCenter Server or standalone host? How are you doing it? Are you able to connect to your vSphere Server from the same machine via vSphere Client?
Thanks!
apologies for getting back late to you!
yes its vCenter
can integrate the Veeam to the Vcenter to manage the back-ups from the vCenter?
Yes, you can do that, moreover adding vCenter Server as opposed to adding standalone hosts is a recommended way of configuring your backup jobs. If you still can't add the vCenter Server, please do contact our technical team, our engineers will be able to assist you via a remote WebEx session. Thanks!
Vitaliy S. wrote:Yes, you can do that, moreover adding vCenter Server as apposed to adding standalone hosts is a recommended way of configuring your backup jobs. If you still can't add the vCenter Server, please do contact our technical team, our engineers will be able to assist you via a remote WebEx session. Thanks!
thank you
i am al set,
all is operational again,
one more questions , i've added the vcenter to the servers, is it possible to backup the ESXI server ( physique server) ?
or is Veeam just for Virtualisation ?