April 27, 2010 at 11:22 pm
Hi Experts,
Sometimes we are getting a below error in VERITAS while taking backup of ProductionDB database backup. All other B2B database backups are happening properly.
Error message:-
Backup on client SPN-PRD-DBS3 for user AGTech_M by server bkp-prd-app1 failed.
Status = the backup failed to back up the requested files.
00000000026840D0 may have more information.
File list
---------
/SPN-PRD-DBS3.MSSQL7.SPN-PRD-DBS3.db.B2BProductionDB.~.7.001of001.20100423093500..C
Any idea???
Thankx a ton in advance.
Cheers
Cheers
April 28, 2010 at 5:56 am
What's the error on the SQL Server side? Is there one?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 28, 2010 at 6:13 am
From instinct here...
Assuming this job has already run succesfully in the past :
1 - Either the permissions changed (NTSF or sql login)
2 - You're out of space on the backup drive.
3 - Maybe the db has been detached and is no longer there (or no longer available for backup.... which I can't think of any other reasons than the ones I mentionned AND single_user mode).
April 28, 2010 at 6:53 am
Ninja's_RGR'us (4/28/2010)
From instinct here...Assuming this job has already run succesfully in the past :
1 - Either the permissions changed (NTSF or sql login)
2 - You're out of space on the backup drive.
3 - Maybe the db has been detached and is no longer there (or no longer available for backup.... which I can't think of any other reasons than the ones I mentionned AND single_user mode).
No argument. Space is so frequently the issue with backups, you're almost always going to be right saying it.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 28, 2010 at 9:17 am
Grant Fritchey (4/28/2010)
Ninja's_RGR'us (4/28/2010)
From instinct here...Assuming this job has already run succesfully in the past :
1 - Either the permissions changed (NTSF or sql login)
2 - You're out of space on the backup drive.
3 - Maybe the db has been detached and is no longer there (or no longer available for backup.... which I can't think of any other reasons than the ones I mentionned AND single_user mode).
No argument. Space is so frequently the issue with backups, you're almost always going to be right saying it.
Ya this called for a "is it [still] plugged in" moment :-D.
April 28, 2010 at 11:12 am
Ninja's_RGR'us (4/28/2010)
Grant Fritchey (4/28/2010)
Ninja's_RGR'us (4/28/2010)
From instinct here...Assuming this job has already run succesfully in the past :
1 - Either the permissions changed (NTSF or sql login)
2 - You're out of space on the backup drive.
3 - Maybe the db has been detached and is no longer there (or no longer available for backup.... which I can't think of any other reasons than the ones I mentionned AND single_user mode).
No argument. Space is so frequently the issue with backups, you're almost always going to be right saying it.
Ya this called for a "is it [still] plugged in" moment :-D.
Excellent!
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 28, 2010 at 11:54 pm
disc space might be an issue.. i will revert back with the error log details when i see the error again...
Thankx for you replies... 🙂
Cheers,
Cheers
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply