Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
NeilG
Aged Yak Warrior
530 Posts |
 Posted - 2009-10-07 : 08:55:19
|
| Hi Guys, I’m really hoping that people can point me in the correct direction.I have a real problem with a Live system which keeps failing with an overnight job and returns the same error all the time Executing the query "BACKUP DATABASE [Live_CRM] TO DISK = N'\\\\CRM_backups\\Live_CRM_backup_200910012300.bak' WITH NOFORMAT, NOINIT, NAME = N'Live_CRM_backup_20091001230008', SKIP, REWIND, NOUNLOAD, STATS = 10" failed with the following error: "A nonrecoverable I/O error occurred on file "\\\\CRM_backups\\Live_CRM_backup_200910012300.bak:" 64(error not found).BACKUP DATABASE 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.Processed 1332472 pages for database 'SRM_MSCRM', file 'mscrm' on file 1.Processed 17 pages for database 'Live_CRM', file 'sysft_ftcat_documentindex_6adeb687bd2d4b80800726a71b236831' on file 1.Processed 78 pages for database 'Live_CRM', file 'Livecrm_log' on file 1.100 percent processed.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.The problem is after google’ing etc I’m still unable to find the problem, I believe that the problem lies with the backup file being located on a second server not the server where the database is located and losing connection at somepoint.Any advice would be excellent!!!--------------------------SQL Server MCP & MCTS |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2009-10-07 : 15:06:02
|
| 1. what is the size of the final backup file? has it ever succeeded? if not, you can take a local backup or somewhere bigger than the destination, might be a space issue (although if it is, the message would be explicit, worth checking)2. run a ping with trace towards the destination server from the sql server and see if you get network glitches, otherwise you will need to consult your network guy to verify this for you during those timesusually caused by heavy traffic especially if the backup process is ran on the same network as everything else you have...good practice is to separate admin transactions to run on a different network tha the one you have for your production3. is there corruption in the database? run dbcc commands to check the integrity of the database4. the disk location where the backup file is being written might have bad clusters, have your storage guy run some diagnostics to be sure the backup is not being written on a bad sector or the likesjust some things to check...--------------------keeping it simple... |
 |
|
|
|
|
|
|
|
HELP!!! with and constant overnight job failure