September 7, 2011 at 3:25 am
My maintenance plan encounter this problem intermittently.
This is the error message from event viewer.
BackupIoRequest::ReportIoError: write failure on backup device '\\servername/sharedfolder/xxx.bak'. Operating system error 1394(There is no user session key for the specified logon session.).
The most outrageous is the server will shutdown itself after this error. It has happened 5 times in 1 month.
September 7, 2011 at 3:50 am
Sounds like something going wrong on the Windows Server. Have you checked there for errors?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 7, 2011 at 4:09 am
If you use your favourite internet search engine to look for that error message, high up on the list should be a Microsoft support page that gives lots of information about the error. Have you tried working through that?
John
September 7, 2011 at 4:46 am
Somebody also encountered same issue here but no solution also.
http://www.sqlservercentral.com/Forums/Topic1096952-357-1.aspx#bm1139974
September 7, 2011 at 9:42 am
Can you backup to a local drive ok?
Is this a typo?
\\servername/sharedfolder/xxx.bak'
if so it should be
\\servername\sharedfolder\xxx.bak'
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 8, 2011 at 1:38 am
Hi, apart from the possible typo as already suggested, it looks like the path to save the backup is a network share. In order for SQL Server to recognise a new share you would have to restart the SQL Service.
Please correct me if I'm wrong anyone, but I had this problem when saving backups to a network share. 🙂
September 8, 2011 at 1:42 am
No problem with the network path. The backup works almost every day except for few random failures each month. Each time it fails, the same operating system error pops out and then system will shut down. That is the puzzling part.
September 8, 2011 at 1:47 am
I've just run a test. I created a new share on my PC and then backed up a database from a server to that share. No problem.
I suspect either this issue isn't very urgent for the original poster, or he/she wants the answer on a plate, because there have been no replies to the questions asked by Grant, me and Perry.
John
September 8, 2011 at 1:53 am
As this appears to be an intermittent problem, I think I would start with possible operating system errors, there may be some problems that occur around the same time.
It could also be something hardware based, like memory I have seen problems that occur intermittently due to a memory problem.
Updates sometimes cause strange problem too.
You need to check when it first started happening and if there were any updates around the same time.
September 8, 2011 at 2:25 am
For me, backing up across a network is just asking for trouble. I prefer local then mirroring out as necessary
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 8, 2011 at 3:13 am
John,
Like I said this is intermittent problem. Local backup instantly works fine. Network backup also works almost fine only except for random failures. IF you want me to answer whether local backup/mirroring works 100% fine I would need it to run for a duration of time before I can answer back.
For me there are 3 possibilities.
1. Pure windows / registry problem - The error only occurs during backup time and only caused by 1 application. If it is windows problem, it should happen more randomly and caused by more than 1 app. Also checked the windows update history, no updates or patches done prior to this. I am leaving out this possibility.
2. Hardware problem - The timing of the occurrences also leave this possibility out. Memory problem should be more random than this.
3. Application conflict or sql 2008 bug such as overflow - I am more inclined to this for now.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply