August 10, 2009 at 8:48 am
I ran my clean up job @12:05 am, and then ran the backup @12:15, now I am getting this error
August 10, 2009 at 9:24 am
Hi,
Is there any more information, other than the code? Try having a look in the error log and event viewer.
Is this error occuring when you run a backup or another job? Any additional information would help.
Regards,
August 10, 2009 at 9:40 am
when I am running my backup job, I am getting following error
Executed as user: XXXXXX ...sion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 12:15:01 AM Progress: 2009-08-10 00:15:03.36 Source: {4531EE5F-AE49-4961-B180-343DE9395D23} Executing query "DECLARE @GUID UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress Progress: 2009-08-10 00:15:03.55 Source: Maintenance Cleanup Task Executing query "EXECUTE master.dbo.xp_delete_file 0,N'\\De1smsfp01".: 100% complete End Progress Error: 2009-08-10 00:15:05.45 Code: 0xC002F210 Source: Back Up Database Task Execute SQL Task Description: Executing the query "BACKUP DATABASE [xxxx] TO DISK = N'\\De1smsfp01\Backups\SQL\XXXXXX\xxx1.bak', DISK = N'\\De1smsfp01\Backups\SQL\XXXXXX\crs5_oltp2.bak', DISK = N'\\De1smsfp01\Backups\SQL\XXXXXX\xxx3.bak', DISK = N'\\De1smsfp01\Backups\SQL\XXXXXX\XXX... The package execution fa... The step failed.
August 10, 2009 at 9:54 am
Thanks for the additional info.
I assume the agent has permissions to write where you are trying to backup to.
Have you tried logging in (assuming you have permissions) and manually running the backup script in SSMS.
I've had similar messages in the past and they have nearly all been done to permissions. So I think we should start there. If you can write to the location, but the job wont run then that would imply that the SQL agent doesnt have permissions to write to the disk.
Another test/method would to do the backup locally to see if that works for you, you could then if you wanted copy the backup across the network.
I'll keep looking for anything else I can find.
December 1, 2015 at 6:05 am
I get the same error message..
@backupSetId =...".: 100% complete End Progress Progress: 2015-12-01 03:02:37.21 Source: Back Up Database (Transaction Log) Executing query "BACKUP LOG [DBNAME] TO DISK = N'...".: 50% complete End Progress Progress: 2015-12-01 03:02:38.07 Source: Back Up Database (Transaction Log) Executing query "declare @backupSetId as int select @backupSetId =...".: 100% complete End Progress Progress: 2015-12-01 03:02:38.27 Source: Back Up Database (Transaction Log) Executing query "BACKUP LOG [[DBNAME] ] TO DISK ...".: 50% complete End Progress Progress: 2015-12-01 03:02:39.10 Source: Back Up Database (Transaction Log) Executing query "declare @backupSetId as int select @backupSetId =...".: 100% complete End Progress Error: 2015-12-01 03:02:39.16 Code: 0xC002F210 ... The package execution fa... The step failed.
But, the surprising thing is backups are successful and that is a valid backupset.
What I have changed is in the Maintenance plan of the backup job, I have moved the cleanup job before the Full Or log Backup to happen. I see both the clean up and Full and Log backups are happening just fine but still the job showing as failed.
I did ensure the job steps quits reporting success when ran successfully and Reports failure when failed.
Any suggestions what I can check or how I can get rid of this unnecessary error?
December 1, 2015 at 10:20 am
mshashi259 (12/1/2015)
I get the same error message..@backupSetId =...".: 100% complete End Progress Progress: 2015-12-01 03:02:37.21 Source: Back Up Database (Transaction Log) Executing query "BACKUP LOG [DBNAME] TO DISK = N'...".: 50% complete End Progress Progress: 2015-12-01 03:02:38.07 Source: Back Up Database (Transaction Log) Executing query "declare @backupSetId as int select @backupSetId =...".: 100% complete End Progress Progress: 2015-12-01 03:02:38.27 Source: Back Up Database (Transaction Log) Executing query "BACKUP LOG [[DBNAME] ] TO DISK ...".: 50% complete End Progress Progress: 2015-12-01 03:02:39.10 Source: Back Up Database (Transaction Log) Executing query "declare @backupSetId as int select @backupSetId =...".: 100% complete End Progress Error: 2015-12-01 03:02:39.16 Code: 0xC002F210 ... The package execution fa... The step failed.
But, the surprising thing is backups are successful and that is a valid backupset.
What I have changed is in the Maintenance plan of the backup job, I have moved the cleanup job before the Full Or log Backup to happen. I see both the clean up and Full and Log backups are happening just fine but still the job showing as failed.
I did ensure the job steps quits reporting success when ran successfully and Reports failure when failed.
Any suggestions what I can check or how I can get rid of this unnecessary error?
Are you doing the backup to a NAS and is the backup compressed? When the backup starts the NAS allocates an estimated amount of disk space that the file will require. If the compressed file uses less space the NAS has to reset the end of file to the smaller file. This may take longer than the timeout value for the backup. The backup file is good but because the NAS does not respond in a timely manner it thinks it failed when it didn't.
January 11, 2016 at 5:00 am
Backup is happening on local drives of the server. I think it's a SAN drive.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply