Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL backup failure

Status
Not open for further replies.

santam2007

IS-IT--Management
Feb 20, 2007
18
HK
We are running a Schedule backup under cluster env.

Server info.
cluster virture server: cisuq101
physical node: cisuq199 and cisuq198

error messages:
1 retry attempted
[4640] [E] 03/22/07 15:50:49 Error detecting SVS logon name for domain.net
[4640] [E] 03/22/07 15:51:01 Microsoft SQL Server Provider error:
[4640] [E] 03/22/07 15:51:01 Named Pipes Provider: Could not open a connection to SQL Server [2]. .
[4640] [E] 03/22/07 15:51:01 An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..
[4640] [E] 03/22/07 15:51:01 Login timeout expired.
[4640] [E] 03/22/07 15:51:01
Cannot login to SQL Server null.
 
You should put backup command like this: nsrsqlsv -a cisuq101. Add physical hosts to remote access list and give also username and password which has permissions to execute SQL backup.
 
I follow the pervious suggestion, and get the output:

cisuq101.heh.net
MSSQL:master
abandoned:full:save:nsrsqlsv [-a mydomain.net]
* Probe job had unrecoverable failure(s)

mydomain.net
index
succeeded:full:index
mydomain.net: index:mydomain.net level=full, 1949 KB 00:00:01 31 files

mydomain.net
bootstrap
succeeded:0:bootstrap
mydomain.net: bootstrap level=full, 635 KB 00:00:02 569 files
* mydomain.net:bootstrap nsrlpr: Either a printer isn't defined for printing the Bootstrap for this savegroup,
* mydomain.net:bootstrap or the '-PPRINTER' part of the notification resource is absent.
* mydomain.net:bootstrap Please correct as appropriate.
* mydomain.net:bootstrap printing bootstrap information failed (reproduced below).
* mydomain.net:bootstrap
* mydomain.net:bootstrap
* mydomain.net:bootstrap March 22 16:56 2007 mydomain.net's bootstrap information Page 1
* mydomain.net:bootstrap
* mydomain.net:bootstrap date time level ssid file record volume

* mydomain.net:bootstrap 21/03/2007 17:44:27 full 3758161531 26 0 mydomain.net.00
* mydomain.net:bootstrap 1

* mydomain.net:bootstrap 21/03/2007 20:03:39 full 2969640731 5 0 daily.006

* mydomain.net:bootstrap 21/03/2007 20:03:51 full 2852200231 10 0 daily.006

* mydomain.net:bootstrap 21/03/2007 20:04:19 full 2801868610 12 0 daily.006

* mydomain.net:bootstrap 22/03/2007 12:29:29 full 2667709993 27 0 daily.001

* mydomain.net:bootstrap 22/03/2007 12:31:48 full 2583824052 34 0 mydomain.net.00
* mydomain.net:bootstrap 1

* mydomain.net:bootstrap 22/03/2007 14:37:21 full 2533499937 36 0 mydomain.net.00
* mydomain.net:bootstrap 1

* mydomain.net:bootstrap 22/03/2007 14:47:03 full 2499946087 38 0 mydomain.net.00
* mydomain.net:bootstrap 1

* mydomain.net:bootstrap 22/03/2007 14:53:26 full 2466392038 40 0 cisnq199.heh.net.00
* mydomain.net:bootstrap 1

* mydomain.net:bootstrap 22/03/2007 15:51:42 full 4278334862 14 0 daily.006

* mydomain.net:bootstrap 22/03/2007 16:18:29 full 4244782037 16 0 daily.006

* mydomain.net:bootstrap 22/03/2007 16:23:22 full 4211227898 3 0 mydomain.net.00
* mydomain.net:bootstrap 2

* mydomain.net:bootstrap 22/03/2007 16:36:34 full 4177674258 5 0 mydomain.net.00
* mydomain.net:bootstrap 2

* mydomain.net:bootstrap 22/03/2007 16:42:09 full 4144120161 18 0 daily.006

* mydomain.net:bootstrap 22/03/2007 16:43:12 full 4110565792 20 0 daily.006

* mydomain.net:bootstrap 22/03/2007 16:54:34 full 4077012042 22 0 daily.006

* mydomain.net:bootstrap 22/03/2007 16:56:20 full 4043457717 24 0 daily.006

 
Remove the domain name from backup command, just put -a cisuq101. Did you create the client for this backup with virtual name cisuq101? Also is it working if you initiate backup from hostside with Networker User fo SQL?
 
Hello,

The error message points to a hostname called mydomain.net. And that NetWorker is not able to log in to this server. Without knowing more of your configuration it is hard to tell what is causing the problem.

Try to start to determine what works and not. The best way is probably to start with a simple file backup from the virtual server. If that doesn't work, you'll have to start investigating that instead of the SQL backup. Further, you can run the SQL backup from command line or from GUI and select debugging. You can then check nsr\applogs\nsrsqlsv.log for errors, you should be able to find the cause of the error there.
 
yes, "Rif123". It works after I put -a mydomain

The other problem is that I cannot start the Networker User of SQL on the client side "mydomain"

error message: cannot find the file specify !


While I can start it on "mydomain", but cannot find the NWS!
 
To start with, if you haven't done so already, is to create a client defnition that actually is named cisuq102. You and others will probably be confused if data from cisuq102 is saved in cisuq101's index. Not to mention that NetWorker also will be confused.

I know there were a problem with "Cannot find the file specified" in NMSQL 4.1 but I guess you are running 5.0!? The error doesn't seem very informative to me.

If you can start the GUI you should be able to connect to the correct server from within the GUI.

Is it an active/passive cluster? Or is it active/active and therby two virtual servers, ie cisuq101 and cisuq102? Why would it otherwise be 2 names for one virtual server?

If passive, what phys node owns the cluster resources right now? If you have the possibility, could you try to fail over to the other node and see if the error persist?

Cheers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top