June 6, 2011 at 11:49 pm
Hi,
Mydb is about 2GB. When doing a backup everyday, following error is coming although the backup is done successfully. I use the dbcc checkdb and there is no errors.
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.
Msg 3202, Level 16, State 2, Line 1
Write on "\\inbackup01\FINAL2\FULL\mydb_backup_201106070921.bak" failed: 64(The specified network name is no longer available.)
Msg 3271, Level 16, State 1, Line 1
A nonrecoverable I/O error occurred on file "\\inbackup01\FINAL2\FULL\mydb_backup_201106070921.bak:" 64(The specified network name is no longer available.).
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
June 7, 2011 at 2:07 am
Bhuvnesh (6/6/2011)
I use the dbcc checkdb and there is no errors.
DBCC CHECKDB is not enough. It checks only the database. Not the backup.
Run RESTORE VERIFYONLY.
June 9, 2011 at 11:04 am
Have you ever gone to that network location and verified that the file is still there?
Have you ever run a network sniffer to make sure you weren't disconnected at the last moment?
Have you ever checked that network location to verify it has plenty of disk space available for your backup?
June 10, 2011 at 2:18 am
I used to get this message because of a space issue to where i was writing too.
June 10, 2011 at 2:30 am
thanks it has been resolved it happened due to some network issues.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
June 10, 2011 at 2:46 am
Bhuvnesh (6/10/2011)
thanks it has been resolved it happened due to some network issues.
That's usually what that error means. Glad you got it resolved.
May 10, 2012 at 5:52 pm
Hello Bhuvnesh,
I have the same problem. Can you please tell me what Network issue you had. In my case,
1. I am able to navigate from my SQL server database to that network share properly.
2. I have provided FULL ACCESS to EveryOne on the network shared folder.
3. Also I am doing this through a scheduled task. It works fine for couple of databases but it always fails with the same exception always.
Your help will be much appreciated.
Thanks in advance.
May 10, 2012 at 10:33 pm
Nagendra Rao (5/10/2012)
Hello Bhuvnesh,I have the same problem. Can you please tell me what Network issue you had. In my case,
1. I am able to navigate from my SQL server database to that network share properly.
2. I have provided FULL ACCESS to EveryOne on the network shared folder.
3. Also I am doing this through a scheduled task. It works fine for couple of databases but it always fails with the same exception always.
Your help will be much appreciated.
Thanks in advance.
Here are few things you need to check
1. IS there any IO contentions ( high IO spikes ) / do you have high graded sql box ?
2. are you directly taking the backup on shred drives ? if yes then first copy the backups on local drive then move them on shred drive.
3. are there any other backend processes running like jobs ? if yes then change the backup timing
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
May 11, 2012 at 1:20 am
Personally I would backup to a local drive and mirror the backup to the network, that way you have multiple points of failure to the bak/trn files incase you have eithere a local disk or network drive failure and need to restore.
It's the old saying of backups are worthless but restores are priceless.
Remembering back to an old position there where 8 points of failure for backups. Each server had its own drive (1), it then had a on site standby server where the backup was replicated to (2), it was then replicated to the SAN backup area (3) and then copied to tape (4). While all this was going on it was replicated to the DR site main DR server (5), the secondary DR server (6), the DR SAN backup area (7) and the DR sites tape drives (8).
May 11, 2012 at 5:30 am
I find it amusing that this is the only time that having multiple points of failure is a good thing.
Of course, I'm not really sure you should have used that phrase in regards to backups, because it is misleading. But it is still amusing.
May 11, 2012 at 5:36 am
Brandie Tarvin (5/11/2012)
I find it amusing that this is the only time that having multiple points of failure is a good thing.Of course, I'm not really sure you should have used that phrase in regards to backups, because it is misleading. But it is still amusing.
I see your point, maybe best changed to multiple backup locations. I was going off the premis that I could lose 7 out of 8 points and still be able to recover, if the OP is only backing up to a network drive and it fails then if you needed a restore it couldnt be done. But I'm sure that the OP is also shipping to tape or some other location other than the network drive and has a good backup strategy in place to mitigate such occurances.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply