asked
fullbackupfail
can anyone tell me all possible reasons of full backup fail in sql 2008 standard Edition and Enterprise edition? thanks
Can you provide the specific error message that you're getting?
*inter alia*, - lack of disk space, - incorrect privileges for the user running the backup job, - login authentication failure for the task running the job. - backup destination not available - backup user doesn't have permissions on the backup device... A few questions before we can help more: - Is it a scheduled task? - Part of a maintenance plan? - Has it always failed, or has it only just started failing? - Does it fail every time, or just occasionally? EDIT: Oh, and what error message are you getting? Or am I just helping you with your homework?
I agree with all of Thomas' suggestions but your question is so open there are limitless reasons. a few more could be: you use incorrect TSQL syntax the database doesnt exist another back up process is already running the server got turned off you tried a full(*) backup on a database thats in simple recovery mode and so on can you tell us more about your problem so that we can give a more accurate answer? [EDIT] * - As pointed out in the comments a Full backup will safely occur on a Simple database, I meant to suggest that a LOG backup would fail on a SIMPLE database. Thanks for pointing this out. Error left in above to let comment make sense.
A full backup should work just fine whether its in simple recovery or not, the rest of the possibilities are excellent additions.
There are certain Reason for Failure of Full Back , Some of the Reason are give below :- 1. Lack of space in Drive where you are 2. taking the backup Wrongly Written 3. Query. Unavailibility of Database. 4. Another backup is going on
Another backup going on won't necessarily cause a backup to fail. You can take simultaneous full backups, for.example...
