Hi Folks,
I'm relatively new to Veeam. I'm trying to restore a database from a MSSQL server hosted in Hyper-V. I'm able to launch Veeam Explorer from the VBR server, however when trying to do a restore, I encountered the following error, "A connection was successfully established with the server, but then an error occurred during pre-login handshake." Not sure what went wrong, for some context my DBA encrypted the databases and we are using custom port.
For the restore process, i tested on a database where i chose "Restore Database" --> "Restore to another Server", where i indicated the custom port, for example "domain\instance,40000".
Not sure if anyone encountered anything like this..
Thank you!
-
roundrobin
- Novice
- Posts: 3
- Liked: never
- Joined: Dec 13, 2024 5:41 am
- Contact:
-
david.domask
- Product Manager
- Posts: 3602
- Liked: 870 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Trying to do a database restore from MSSQL hosted in Hyper-V
Hi roundrobin,
Sounds like a technical issue, so please open a Support Case for this, as looks like a technical issue and will require an investigation of the debug logs as noted when creating a topic. Please note the name of the server you tried to restore from in your case notes as it will help Support in their investigation. The custom port notation _should_ work, but the solution here may be applicable; if it doesn't help, then support case is the way to go.
The issue itself looks to be related to the SSL handshake, but unclear why, so best to let Veeam Support review the situation.
Please share your case number once created, thanks!
Sounds like a technical issue, so please open a Support Case for this, as looks like a technical issue and will require an investigation of the debug logs as noted when creating a topic. Please note the name of the server you tried to restore from in your case notes as it will help Support in their investigation. The custom port notation _should_ work, but the solution here may be applicable; if it doesn't help, then support case is the way to go.
The issue itself looks to be related to the SSL handshake, but unclear why, so best to let Veeam Support review the situation.
Please share your case number once created, thanks!
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Amazon [Bot] and 7 guests