We help IT Professionals succeed at work.

Database Maintenance Plan Fails to Perform Backup

rjander77
rjander77 asked
on
Medium Priority
467 Views
Last Modified: 2012-06-27
We have several SQL databases I am attempting to back up with a maintenance plan.

I am attempting to back the files up to another server on the same domain.  I have tried it with a mapped network drive and with the UNC path, but both attempts have failed.

I receive no errors and no log file is created, even though I have specifically selected this option.

No users are connecting to any of the databases in question during the time the backup should be attempting to run.

Any ideas?
Comment
Watch Question

Commented:
<<I have tried it with a mapped network drive and with the UNC path, but both attempts have failed.>>


What account are you using to run the maintenance plan? Does that account has permissions to access UNC Path?

Author

Commented:
I'm logged in as the domain administrator.
Commented:
Look at the job history and expand to show all steps.  Selecting the steps in the listbox will sometimes show helpful errror messages if your error log isn't being created.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Commented:
Do you see any thing in the error logs?

Author

Commented:
Thanks for that.  Hadn't seen that before.

It's empty as the check box for 'Write history to the table...' wasn't checked.  It is now, but I won't get anything for a week as the backup is set to run Sunday mornings.  If I run it at nights, it might interfere with the regular Veritas BackupExec backups running on this same SQL Server.

Any other ideas that don't require waiting until next Monday?

Thanks!

Author

Commented:
@ Sirees - The error log was not created.

Commented:
Can you check under Managemnet->SQL Server Agent->Jobs rightclick on the job and View Job History

Check the Show Step details and see if there are any errors there

Author

Commented:
@ Sirees

All right.

Not sure what this all means, but you may have hit on something here.

The SQL Server Agent was not running.  I started it and followed your directions.  The only jobs showing are from my initial test setup from a long time ago.  That job has since been deleted.

Am I right in assuming that the SQL Server Agent not running might have something to do with the backups not running?

Will anything be affected now that this service is started, such as our regular backups by Veritas BackupExec?

Thanks!

Author

Commented:
So I got a log today, which is weird because the job is set to run on Sunday mornings, not random Tuesday nights.  Here's the log, with certain names changed, as noted by {} containers:


Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server 'SQLSERVER\SQLSERVER' as '{domain}\Administrator' (trusted)
Starting maintenance plan 'Complete DB Maintenance' on 11/1/2006 12:00:04 AM
[1] Database {db1}: Transaction Log Backup...
    Destination: [\\{file server}\SQL Backups\{db1}\{db1}_tlog_200611010000.TRN]

    ** Execution Time: 0 hrs, 0 mins, 25 secs **

[2] Database {db1}: Verifying Backup...

    ** Execution Time: 0 hrs, 0 mins, 26 secs **

Backup can not be performed on database '{db2}'. This sub task is ignored.

Backup can not be performed on database 'master'. This sub task is ignored.

Backup can not be performed on database 'msdb'. This sub task is ignored.

Backup can not be performed on database '{db3}'. This sub task is ignored.

[3] Database {db4}: Transaction Log Backup...
    Destination: [\\{file server}\SQL Backups\{db4}\{db4}_tlog_200611010000.TRN]

    ** Execution Time: 0 hrs, 0 mins, 1 secs **

[4] Database {db4}: Verifying Backup...

    ** Execution Time: 0 hrs, 0 mins, 1 secs **

[5] Database {db5}: Transaction Log Backup...
    Destination: [\\{file server}\SQL Backups\{db5}\{db5}_tlog_200611010000.TRN]

    ** Execution Time: 0 hrs, 0 mins, 2 secs **

[6] Database {db5}: Verifying Backup...

    ** Execution Time: 0 hrs, 0 mins, 2 secs **

Backup can not be performed on database '{db6}'. This sub task is ignored.

Backup can not be performed on database '{db7}'. This sub task is ignored.

Deleting old text reports...    0 file(s) deleted.

End of maintenance plan 'Complete DB Maintenance' on 11/1/2006 12:01:00 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.