August 4, 2010 at 5:56 am
I have a SQL 2005 maintenance Plan to back-up databases; remove old backup files; and then remove old report files.
The Plan is intermittantly failing, and the report is as below:-
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.4035 Report was generated on "wavy-agr-db01".
Maintenance Plan: WAVY-AGR-DB01 - Db MaintenancePlan
Duration: 01:47:49
Status: Warning: One or more tasks failed..
Details:
Back Up Database Task (wavy-agr-db01)
Backup Database on Local server connection Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Full
Append existing
Task start: 2010-08-04T10:29:42.
Task end: 2010-08-04T12:17:28.
Failed:(-1073548784) Executing the query "BACKUP DATABASE [agresso] TO DISK = N'\\\\sql-back-001\\e$\\Non_SQLSafe_Backups\\WAVY-AGR-DB01\\agresso_backup_201008041029.bak' WITH RETAINDAYS = 7, NOFORMAT, NOINIT, NAME = N'agresso_backup_20100804102942', SKIP, REWIND, NOUNLOAD, STATS = 10 " failed with the following error: "A nonrecoverable I/O error occurred on file "\\\\sql-back-001\\e$\\Non_SQLSafe_Backups\\WAVY-AGR-DB01\\agresso_backup_201008041029.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 7092248 pages for database 'agresso', file 'agressodata1' on file 1.
100 percent processed.
Processed 2 pages for database 'agresso', file 'agressolog1' on file 1.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Maintenance Cleanup Task (wavy-agr-db01) Task start: 2010-08-04T12:17:28.
Task end: 2010-08-04T12:17:28.
Success
Maintenance Cleanup Task 1 (wavy-agr-db01) Task start: 2010-08-04T12:17:28.
Task end: 2010-08-04T12:17:28.
Success
However, I have successfully restored the database from the 'failed' backup without any problems.
The Server is running 2005 SP3
Any ideas please
August 4, 2010 at 7:02 am
Are you backing up to a network location? If so, check and make sure your destination still exists.
Best practice is to backup locally and move a copy of the backup later. This way the backup process itself doesn't fail. And file copies can always be re-run without the same amount of hassle as troubleshooting backup issues.
August 4, 2010 at 7:07 am
Yes, it is to a network location, and yes it still exists
Other backups to the same location complete without problems
August 4, 2010 at 10:49 am
Chances are you were having network troubles when the job tried to complete. It could have been anything from noise to inaccessibility. Try the job again, while you're sure the network connection works, and I'll bet that it succeeds (unless passwords got changed or something).
I stand by my earlier advice, though. Backup locally, then copy over to the network destination.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply