Unsolved
This post is more than 5 years old
5 Posts
0
2420
Cannot restore Sql Server Database
Hello, I'm trying to restore a SQL Server R2 database with networker and it stucks all the time(i'm using e verify only herer but I tried also the copy method) . I'm attaching a PNG with the version of my Networker module for SQL Server.
Follow the full stack of errors - then, the restore simply get stuck.
Recovering files of client 'dbhost.tinet.net' from server 'networker' to client 'dbhost'.
43708:(pid 3732):Start time: Mon Apr 11 19:27:55 2016
43621:(pid 3732):Computer Name: dbhost User Name: alessandro.aste
NSR_CLIENT: dbhost.domain.local;
NSR_SERVER: networker.domain.local;
37721:(pid 3732):Recovering database 'AX2012PROD' ...
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
51281:(pid 3732):nsrsqlrc.c(7643): Could not get saveset record from mmdb; error: 0x00013882
failed query for savetime 1458518478, (Remote system error - The requested address is not valid in its context.
)
80282:(pid 3732):nsrsqlrc.c(4161): Error getting backup endtime from media Database.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
51281:(pid 3732):nsrsqlrc.c(7643): Could not get saveset record from mmdb; error: 0x00013882
failed query for savetime 1458442863, (Remote system error - The requested address is not valid in its context.
)
80282:(pid 3732):nsrsqlrc.c(4161): Error getting backup endtime from media Database.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
51281:(pid 3732):nsrsqlrc.c(7643): Could not get saveset record from mmdb; error: 0x00013882
failed query for savetime 1458424871, (Remote system error - The requested address is not valid in its context.
)
80282:(pid 3732):nsrsqlrc.c(4161): Error getting backup endtime from media Database.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
61320:(pid 3732): Cannot bind socket to connection port in configured port range on system dbhost.domain.local: The requested address is not valid in its context.
4690:(pid 3732):RESTORE VERIFYONLY FROM virtual_device='Legato#f7e22770-d221-492a-8fd8-d8c8135962b9'
aaste
5 Posts
0
April 11th, 2016 12:00
Hello, thanks for your reply. There is no firewall in the middle, the networker server and the dbhost are in the same lan
ble1
2 Intern
2 Intern
•
14.3K Posts
0
April 11th, 2016 12:00
2.4? Man, that is ooooold. Anyway, what it complains is that it can't contact server over ports it wants to use (connection ports). Initial handshake of data went over service ports, but actual data (like backup or restore) goes over connection ports and it seems something is blocking it. Could be fw for example.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
April 11th, 2016 13:00
Did SQL module 2.4.0 supported DDBoost in the first place? Anyway, issue seems to be connection from client to server (or DD if DDboost is used, but top of my head I doubt SQL module ever supported DDBooost - you had to use NMM I believe - you are pretty much behind what is current and supported in those terms with that module version). You can try to restart services on client and try once again. If it happens again, try to run it from CLI in debug mode to see which part of connection establishing fails in more details.
gautamgp
226 Posts
0
April 11th, 2016 20:00
The error is clearly related to firewall ports. You can disable windows firewall on the client and that should take care of the errors that you are facing. Also, the version you are using is end of support life, i advise you to upgrade to the supported version and then try the restore.
aaste
5 Posts
0
April 12th, 2016 02:00
Thanks for your reply. Obviously I have windows firewall disabled in both Networker Server and Dbhost........and yes, the DNS is ok.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
April 12th, 2016 05:00
Hello
Please refer to https://support.emc.com/kb/410071
it refers to the errors and how you can fix the Port Exhaustion
the Windows operating systems have a default limit on the number of user ports that can be claimed by an application. In a large and busy NetWorker environment, the number of ports used can exhaust the operating system's limit, leading to errors.
also please note NMM 2.4 Is EOSL and you should consider upgrading to a supported version
thank you
aaste
5 Posts
0
April 12th, 2016 05:00
Thank for your reply. I tried to browse that link (I created an account) but when I try to login I see this:
I don't know if this is temporary problem or not.
StuartWhitby
45 Posts
0
April 12th, 2016 08:00
I just get that I'm not authorized to view the content on that link Diana. However, this *IS* a case of your backup server is unable to connect to anything within the configured port range on dbhost.
Run nsrports on both systems. The should generally both come back with something along the lines of:
Service ports: 7937-9936
Connection ports: 0-0
I suspect that one of these will be coming back with different numbers, and that they can't talk to each other due to that. Most likely someone's gone "aha, we can improve security by shutting down unnecessary ports!" without considering why so many are available in the first place.
nsrports -S -
should fix it.
aaste
5 Posts
0
April 12th, 2016 11:00
Thanks for your reply - I get exactly this
Service ports: 7937-9936
Connection ports: 0-0
When I run nsrports on both servers.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
April 12th, 2016 23:00
Hello ,
this is from the KB
Please See http://msdn.microsoft.com/en-us/library/aa560610%28v=bts.20%29.aspx for details.
nsradmin -p nsrexec
In the interactive prompt:
option hidden
print type: nsrla (look for max auth thread count should be 0 or unlimited)
update max auth thread count: 50 (then confirm with y)
print type: nsrla (and confirm the change has been made).
http://support.microsoft.com/kb/2722392
http://support.microsoft.com/kb/2645640
http://support.microsoft.com/kb/2553549