Maintenance Plan Log time stamps

microsoft.public.sqlserver.tools

11 May 2007 7:47 PM

Michelle

I have a simple Maintenance Plan, it does the integrity check and then a
Backup.
The Log reads as follows:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
'ServerA' as 'DOMAIN\ADMINUSER' (trusted)
Starting maintenance plan UserDB Backup Maint Plan' on 5/10/2007 5:30:03 AM
[1] Database MYDB: Check Data and Index Linkage...

    ** Execution Time: 2 hrs, 9 mins, 1 secs **

[2] Database MYDB: Database Backup...
    Destination: [\\ServerB\C$\Backup_ServerA\MYDB\MYDB_db_200705101439.BAK]

    ** Execution Time: 1 hrs, 36 mins, 6 secs **

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

End of maintenance plan UserDB Backup Maint Plan' on 5/10/2007 4:15:27 PM
SQLMAINT.EXE Process Exit Code: 0 (Success)

I'm having a math problem with all this (as well as just having the job take
too many hours). The maintenance plan starts at 5:30 AM each day and doesn't
finish until after 4:00 PM each day. The log here shows that the integrity
check took just over 2 hours. The Backup, just over an hour and a half. By
my calculation, that's just under 4 hours, yet the entire job runs nearly 11
hours. I've taken the file deletes out and everything I can to shorten the
time, however this job just runs forever. How are these times being
calculated? What is really happening?
Although the backup says it only takes an hour and a half, why is it not
until after 2 PM in the afternoon do I start to see the .BAK file growing on
ServerB? I understand that this can take a while, as the database is over
100 GB... but I need to be able to do a full backup in less than 11 hours....
then what, even thinking about a restore would be out of the question.
The other mystery about this is, when I initiate the exact same Maint Plan
in the afternoon hours, it runs to completion in 4 hours as it should. The
5:30 AM scheduled plan takes 11+ hours.
How do I troubleshoot this? What can I look for? Any suggestions?