I have a problem with the backups of a Windows 2003 cluster with sql server 2005. I was running normally and suddenly stopped. The errors are always the same and nothing works.
savegrp: suppressed 3 lines of verbose output
38008: (pid 6112): Internal system error, please see nsr \ applogs \xbsa.messages on the client system for reason.
29085: (pid 6112): Microsoft SQL Server Provider error:
38006: (pid 6112): A nonrecoverable I / O error occurred on file "Legato #690decaa-f3c3-4481-8584-8938f1da837e:" 995 (The I / O operation has Beenaborted because of either a thread exit or an application request .) ..
38006: (pid 6112): BACKUP DATABASE is terminating abnormally ..
53084: (pid 6112): Processing msdb failed, the item will be skipped.
43709: (pid 6112): Stop time: Mon Apr 30 15:00:51 2012
<Error>: Backup operation finished with error (s). Refer to the module backuplog file for details.
Any ideas? I was told by support that the problem is with SQL Server, but thesebackups worked correctly until recently, when the messages started to happen.
Solved! Go to Solution.
Please add the user (mssql) into the remote field of the client pointed out in the logs as follows:
Go to the client configuration and for example *@mssql in the remote access field, or else try with *@*
You need to look the following logs to gather more information:
These 2 logs should give you more information about the cause of the failure, however I would recommend you to check also the Application and System event logs, as this could be a SQL issue instead.
Please go through the following KB article which provide more information related to the issue you are facing
Hope it helps you,
This problem did not happen this instance (cluster).
Due to the specific needs of business, even as a cluster, I had to configure theNetworker of the nodes in a cluster so that the robot acceded to the basesthrough the fiber directly. After the change of the node Custer, this problem hasoccurred. This group operated at 100%, without producing any problem.
This same problem occurred in another instance, which now has no moreoccur. No intervention was performed for the problem that failed to happen.
Please help me URGENTLY.
PS: Sorry for the english, I'm using google translator because I do not speakEnglish.
What is your native language?
Ok, so if I understood correctly you have created new client entries in NetWorker to back them up being the clients also storage nodes, is this correct? Otherwise what do you mean you had to create 2 clients to access the robot through fiber?
What I think is that the configuration, or actually the re-configuration has not been done correctly.
Please note that if you want these clients to be storage nodes you need to install the storage node software, configure the devices for those storage nodes, change the client configuration to specify the storage node (in Globals 2 of 2 tab), etc.
Apart from that bear in mind that you will need to create a virtual client for the SQL virtual instances so that the virtual DB's are being backed up.
This is explained in the documentation:
◆ A client associated with a physical node in the cluster backs up files on private disks attached to that node.
◆ A client associated with a virtual server backs up only files on disks in the cluster resource group belonging to that virtual server.
Based on the error message I think it's an issue with the configuration of the storage nodes and/or devices.
Hope this helps to clarify the configuration.
Does this always happen with msdb? I noticed in my environment that sometimes msdb will fail for transaction logs when server is under high load and message would be pretty much the same.
We are having this same problem:
"37994:(pid 2852):Backing up master...
4690:(pid 2852):BACKUP database [master] TO virtual_device='Legato#34788932-4d18-4a47-adc0-351928411ec6' WITH name=N'LegatoNWMSQL', description=N'MSSQL:master'
38008:(pid 2852):Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
29085:(pid 2852):Microsoft SQL Server Provider error:
38006:(pid 2852):Write on "Legato#34788932-4d18-4a47-adc0-351928411ec6" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.).
38006:(pid 2852):A nonrecoverable I/O error occurred on file "Legato#34788932-4d18-4a47-adc0-351928411ec6:" 995(The I/O operation has been aborted because of either a thread exit or an application request.)..
38006:(pid 2852):BACKUP DATABASE is terminating abnormally..
53084:(pid 2852):Processing master failed, the item will be skipped.
nsrsqlsv: MSSQL:master level=full, 0 KB 00:00:00, 1-file(s)-processed, 0-file(s)-succeeded
Backup operation finished with error(s). Refer to the module backup log file for details.
43709:(pid 2852):Stop time: Wed Jan 22 10:55:34 2014"
Did not help.
In the monitoring writes
Cannot run savefs: The requested operation requires elevation. (Win32 error 0x2e4)
servername:savefs: retried 1 times.
Who can help?
can you paste the last few lines from nsr/ applogs/xbsa.messages here.
--- Original Message ---