December 24, 2010 at 1:21 am
Hi,
I do my backups with the MMS Maintenance Plan. Until recently it all went well. Currently, of the 50 databases that are backupped, a number of 0 to 8 fail. There's no pattern I can discover; each day it involves other databases. Both the larger and the smaller databases can fail. They are backupped to a networkdrive within a VMWare enviroment. Looking at the error message, they seem to have been processed 100%... but obviously I don't trust the backup.
Someone any ideas? Thanks, and Merry Christmas & Happy New Year!
Raymond
Executing the query "BACKUP LOG [_performance] TO DISK = N'\\\\Storagecl..." failed with the following error: "The operating system returned the error '64(failed to retrieve text for this error. Reason: 15105)' while attempting 'FlushFileBuffers' on '\\\\Storagecl.codelogic.local\\storage\\SQLBACKUP\\_performance_backup_2010_12_23_014628_4912380.trn'.
BACKUP LOG is terminating abnormally.
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.
100 percent processed.
Processed 23199 pages for database '_performance', file '_performance_log' on file 1.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
December 24, 2010 at 1:26 am
do you have sufficient access to write to the destination location?
Try to restore a backup and see what errors are generated.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
December 24, 2010 at 2:09 am
Also, please check "DBCC CHECKDB" output. It checks the logical and physical integrity of all the objects in the specified database. you use the PHYSICAL_ONLY option for frequent use on production systems.
Thanks
December 24, 2010 at 10:13 am
That error indicates that there was an issue with the network. When backing up across the network, if there are any issues with the connection it will cause the backups to fail.
There are numerous articles about how to get around this issue. This could be a problem with how SMB is configured on the destination, or it could be a problem with the TCP Chimney setting, or other issues.
The best way to get around this issue is to backup locally - then copy the backup files to the network share.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
December 26, 2010 at 7:34 am
Hi,
Why you will not try local system, If you give the path of local it's taking proper means N/W issue.....
Satish
December 29, 2010 at 8:43 am
Thanks for all your replies.
I wanted to do a local backup, but I saw that there's not enough diskspace. That's why I backup across the network - to a cheaper diskarray.
I am still investigating, if I come acroos something I'll post it....
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply