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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Networker, SQL & Virtual cluster servers

Status
Not open for further replies.

TheDugsBaws

Technical User
Oct 23, 2007
114
EU
Folks,

I'm having difficulty backing up a virtual client's SQL databases through Networker.

I have NWSQL 5.2 installed on the client, SQL 2005 server.

The client setup in Networker is as follows:

Name: SQLvirtServ1.sqlvirt.com
Save Set: MSSQL:
Backup Command: nsrsqlsv -a SQLvirtServ1
Remote User: Domain\Username
Password: password
Remote Access field: *@phyhost1
*@phyhost2


I can run a save of both filesystem &sql data from the command line on the client, but the scheduled SQL save fails as does the filesystem save. What could be the problem?



 
What is your client ressource for the scheduled Backup ?

For Filesystembacup in a mscs Cluster you have to use the virtual Server for the client ressource and specify the Disks for savesets eg. P:\ L:\ etc.
Saveset "All" will only backup the non shared drives.

For the sql backup you have to define the virtual server SQLvirtServ1.sqlvirt.com as the networker client for scheduled backup.
 
Ok so the physical clusters need to back up the filesystem and the virtual backs up the SQL. I'll give this a go, I still expect the MSSQL to fail though.
 
This nugget again.

So I am able to backup filesystem data from server to client.

I am able to backup SQL data from client to server through both the command line and the GUI when specifying the virtual server.

However, I cannot perform a server initiated backup. When I kick it off, it looks like the probe is abandoned due to the remote username & password being used*. However, I can log on locally with these credentials. Has anyone seen this behaviour before? I've tried countless permutations.



*When I leave the fields blank I get "User SYSTEM cannot login to SQL DB" or a similar error message. It looks like the username & password is where the probe fails, but these are definitely able to login to the local machine.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top