March 7, 2006 at 3:13 pm
I'm having problems getting a backup through our Maintenance Plan.
We had a vendor create a database and ship it to us. We attached it to our server and created the necessary SQL accounts to read/write. Everyting "looks" fine. I included this database in the Maintenance Plan and the plan fails to back the new database. The plan executes as SA. I'm pretty sure I'm missing something but for the life of me I can't find it.
Thanks for your suggestions.
Paul
--Paul Hunter
March 7, 2006 at 3:16 pm
Hello Paul,
Have you checked the error logs? any information you found.
try to take a manual backup of the said attached database. if it works, then try to create a new maintenance plan and execute the same for cross verfication.
Thanks and have a great day!!!
Lucky
March 7, 2006 at 3:38 pm
The Manual backup worked fine (thanks). There isn't anything in the SQL Log but in the event Log I get:
"SQL Server Scheduled Job 'User DBs - Backup' (0xEC880ABCC4DD814DB9558DA78BCE8526) - Status: Failed - Invoked on: 2006-03-07 16:27:50 - Message: The job failed. The Job was invoked by User sa. The last step to run was step 1 (Step 1)."
There are three databases in the plan, two back up fine every time only one fails. Same results when I create a new MP.
--Paul Hunter
March 7, 2006 at 11:27 pm
I have a similar problem. I scheduled backups to be run every morning at 5AM. All the databases but one will be backedup. I can take manual backup for this particular database. Every morning, I see a notification e-mail saying that the Maintenance plan failed. When I check my backup folder, I find all the backed up databases but one. The SQL Error log displays a message like this :
BACKUP failed to complete the command BACKUP DATABASE [teriws_dev] TO DISK = N'G:\xxx_backup\xxx_db_200603060600.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Some times all the databases would be backedup but still the notification says that the Maintenance plan failed.
Any ideas will be appreciated.
Thanks for your time,
Kiran.
Future belongs to those who believe in the beauty of their dreams
March 8, 2006 at 2:39 am
Space is often an issue if there is a optimization task running prior to the backup - This creates a large transaction log.
Also do these backups fail when you recreate the maintenance plan?
March 8, 2006 at 2:55 am
I had a problem with the sqlmaint.exe. So I deleted the maintenance plan and recreated. I clean up my backup folder often and make sure that there is no space issue. Also...I have a batch file to delete the 1 day old backups. I have the option to delete the 1 day old files from the folder in Maintenance plan which never works.
Future belongs to those who believe in the beauty of their dreams
March 8, 2006 at 7:29 am
Hi Paul,
Is it the database backup that fails or the transaction log (if the TN log is part of the maintenance plan)?
Check if the new DB is on a Simple Recovery Model and the others might be on Bulk or Full.
However, if it is the DB backup that is failing, this won't help!!
March 8, 2006 at 9:49 am
I got it solved. The third time is the charm. Initially I had created a second plan to test out using a "new" plan. The third time I deleted the existing plan and recreated it from scratch.
Thanks for the suggestions.
Paul
--Paul Hunter
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply