Solved

Database Maintenance Plan Fails to Perform Backup

Posted on 2006-10-30
9
440 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?
0
Comment
Question by:rjander77
  • 5
  • 3
9 Comments
 
LVL 20

Expert Comment

by:Sirees
Comment Utility
<<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?
0
 

Author Comment

by:rjander77
Comment Utility
I'm logged in as the domain administrator.
0
 
LVL 21

Accepted Solution

by:
mastoo earned 500 total points
Comment Utility
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.
0
 
LVL 20

Expert Comment

by:Sirees
Comment Utility
Do you see any thing in the error logs?
0
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 

Author Comment

by:rjander77
Comment Utility
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!
0
 

Author Comment

by:rjander77
Comment Utility
@ Sirees - The error log was not created.
0
 
LVL 20

Expert Comment

by:Sirees
Comment Utility
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
0
 

Author Comment

by:rjander77
Comment Utility
@ 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!
0
 

Author Comment

by:rjander77
Comment Utility
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)
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Join & Write a Comment

Having an SQL database can be a big investment for a small company. Hardware, setup and of course, the price of software all add up to a big bill that some companies may not be able to absorb.  Luckily, there is a free version SQL Express, but does …
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now