chmilhouse
asked on
SQL 2005 Maintenance Plan Issues
Hello Everyone,
I am really hoping that someone will be able to help me here.. I am at my wits end and I can't figure out what the problem is.
I have created multiple Maintenance Packages (one for differential and one for full backups of all of my databases). I have not altered the subplans that were created along with the packages. The problem I am having is neither my Differential job NOR my Full backup job complete successfully. The consistently fail with the following error:
Executed as user: FILE3\SYSTEM. ...rsion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:58:35 PM Progress: 2008-10-17 15:58:46.94 Source: {34269DD8-BCB9-4590-B079-B 5446E21CDA C} Executing query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress Progress: 2008-10-17 15:58:47.76 Source: Configuration Management Differential Backup Executing query "BACKUP DATABASE [ConfigurationManagement] TO DISK".: 100% complete End Progress Progress: 2008-10-17 15:58:49.32 Source: NetPerfMon Differential Backup Executing query "BACKUP DATABASE [NetPerfMon] TO DISK = N'D:\Datab".: 100% complete End Progress Progress: 2008-10-17 15:58:50.30 Source: ePO4_NMS1 Differential Backup Executing query "BACKUP DATABASE [ePO4_NMS1] TO DISK = N'D:\Databa".: 100% complete End Progress Progress: 2008-10-17 15:58:51.73 Source: SUSDB Differential Backup ... The package execution fa... The step failed.
The database that the job will fail on will change from time to time (it seems that most of the time it is failing on the SUSDB though). I have no idea why this database would be failing as I am able to successfully perform a manual backup of the ALL the databases using both the wizard and direct SQL Statements plugged into the query analyzer.
I have identical jobs set up at other locations for the exact same databases and I have NO problems whatsoever. I have double checked the settings across a working site with the problem site and there are no differences in configuration.
If any one can help me or at least point me in the right direction I would be extremely Grateful.
Thank you all for you input and assistance.
I am really hoping that someone will be able to help me here.. I am at my wits end and I can't figure out what the problem is.
I have created multiple Maintenance Packages (one for differential and one for full backups of all of my databases). I have not altered the subplans that were created along with the packages. The problem I am having is neither my Differential job NOR my Full backup job complete successfully. The consistently fail with the following error:
Executed as user: FILE3\SYSTEM. ...rsion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:58:35 PM Progress: 2008-10-17 15:58:46.94 Source: {34269DD8-BCB9-4590-B079-B
The database that the job will fail on will change from time to time (it seems that most of the time it is failing on the SUSDB though). I have no idea why this database would be failing as I am able to successfully perform a manual backup of the ALL the databases using both the wizard and direct SQL Statements plugged into the query analyzer.
I have identical jobs set up at other locations for the exact same databases and I have NO problems whatsoever. I have double checked the settings across a working site with the problem site and there are no differences in configuration.
If any one can help me or at least point me in the right direction I would be extremely Grateful.
Thank you all for you input and assistance.
ASKER
Hi Daniel,
Thank you for the reply. I was actually able to track down the issue this morning. One of the databases that was being backed up by this maintenance plan was located on a remote computer. The user credentials entered to connect to that server were not correct and it was causing the jobs to fail. I wasn't able to immediately notice this problem b/c the log I pasted above was pointing at a different database than the one that was causing the issue. I am not 100% if there is a character limit on an SQL log file but would you happen to know?
Thank you for the reply. I was actually able to track down the issue this morning. One of the databases that was being backed up by this maintenance plan was located on a remote computer. The user credentials entered to connect to that server were not correct and it was causing the jobs to fail. I wasn't able to immediately notice this problem b/c the log I pasted above was pointing at a different database than the one that was causing the issue. I am not 100% if there is a character limit on an SQL log file but would you happen to know?
>> I am not 100% if there is a character limit on an SQL log file but would you happen to know?
No ... I'm not sure on that.
No ... I'm not sure on that.
ASKER
Ok. Thanks for the help Daniel.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
We've got to figure out WHY that one fails ... in my experience it's usually been due to disk space, but that doesn't really sound like the problem you're having.