-
- Expert
- Posts: 159
- Liked: 37 times
- Joined: Jan 19, 2016 1:28 pm
- Full Name: Jóhannes Karl Karlsson
- Contact:
Problem restoring SQL DB
hi,
This issue has been logged as case #05334528
We had been doing SQL DB restores for a certain SQL server in our environment last week. Then we needed some more restoring with the same SQL server this week, but now it does not work.
We get 'No such host is known' on the second page of the restore wizard (after specifying the credentials).
Backups have no errors. The error is both when trying to restore to the same server and different server. Also if we do 'export backup' to a bak file, we get the same error.
It is possible to restore windows guest files to same and different server.
As I mentioned in the beginnining, the problem was not last week and in the mean time the only change we can think of is installing P20220302. Are anyone else having the same problem?
Regards,
Jóhannes
This issue has been logged as case #05334528
We had been doing SQL DB restores for a certain SQL server in our environment last week. Then we needed some more restoring with the same SQL server this week, but now it does not work.
We get 'No such host is known' on the second page of the restore wizard (after specifying the credentials).
Backups have no errors. The error is both when trying to restore to the same server and different server. Also if we do 'export backup' to a bak file, we get the same error.
It is possible to restore windows guest files to same and different server.
As I mentioned in the beginnining, the problem was not last week and in the mean time the only change we can think of is installing P20220302. Are anyone else having the same problem?
Regards,
Jóhannes
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Problem restoring SQL DB
Hi Johannes,
I doubt that it is related to P20220302 build. Did you try to check DNS resolution from Veeam B&R server and Mount server to the target SQL server? For example, you can try "nslookup hostname" or "ping -a hostname". One more idea is to specify IP address of the target server at this step of restore wizard. Anyway, I'm sure that our support team will find out the cause of this problem, let's wait for their conclusion.
Thanks!
I doubt that it is related to P20220302 build. Did you try to check DNS resolution from Veeam B&R server and Mount server to the target SQL server? For example, you can try "nslookup hostname" or "ping -a hostname". One more idea is to specify IP address of the target server at this step of restore wizard. Anyway, I'm sure that our support team will find out the cause of this problem, let's wait for their conclusion.
Thanks!
-
- Novice
- Posts: 7
- Liked: never
- Joined: Feb 06, 2022 4:05 am
- Full Name: Andy Perkins
- Contact:
Re: Problem restoring SQL DB
Interesting I have had issues with Veeam not being able to resolve hosts on some of my linux proxy after upgrading to P20220302
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Problem restoring SQL DB
Hi Andy,
Do you have a support case ID for the issue you're talking about?
Thanks!
Do you have a support case ID for the issue you're talking about?
Thanks!
-
- Novice
- Posts: 7
- Liked: never
- Joined: Feb 06, 2022 4:05 am
- Full Name: Andy Perkins
- Contact:
Re: Problem restoring SQL DB
Yes it is Case #05338605
-
- Expert
- Posts: 159
- Liked: 37 times
- Joined: Jan 19, 2016 1:28 pm
- Full Name: Jóhannes Karl Karlsson
- Contact:
Re: Problem restoring SQL DB
Just to inform that in our case #05334528 this error was because the proxy/mount server had problems with DNS. It was resolved by fixing the DNS setting on the proxy. What was a bit confusing for us is that guest restore was working fine, but SQL not.
-
- Lurker
- Posts: 1
- Liked: 2 times
- Joined: Jan 28, 2016 10:59 am
- Full Name: Marcelo Viegas
- Contact:
Re: Problem restoring SQL DB
Hi Jóhannes,
That also fixed this issue for me!
Not exactly DNS servers, but DNS suffix...it was missing on the proxy/mount servers and because those servers are in a workgroup, they couldn't mount the databases when performing application item-> SQL restore.
Funny thing is that everything else was working fine, apart from that.
Marcelo
That also fixed this issue for me!
Not exactly DNS servers, but DNS suffix...it was missing on the proxy/mount servers and because those servers are in a workgroup, they couldn't mount the databases when performing application item-> SQL restore.
Funny thing is that everything else was working fine, apart from that.
Marcelo
Who is online
Users browsing this forum: Semrush [Bot], vottak and 33 guests