BACKUP job takes too long...

The database is about 5 Gb and the transaction log is about 13 M
and it takes 11 hours to do a full back up.
I am not sure why it takes that long? Is there any thing I can check?
IT is SQL v7.
Thank youKind of hard to tell. How are you doing the backup? Is it to tape, or to disk? If it is to disk, are you backing up the database to the same physical disk as the database is on? Also, what sort of activity (mostly read, or mostly write, and how much writing?) is going on in the database, while you are backing it up? If you are backing up to disk, is your Virus Scan program going nuts?

These are just a few of the problems you might be seeing. Like I say. Kind of hard to tell.|||If tape is it running at the same time on the same machine and same drive?|||Sorry. I did not give enough details.

I have a DB maintenance plan to do back up each night when there is no
activities on the server. The back up file is written to disk (another server).

I did not check to see if the Virus Scan program going nuts or not.
But it is a good point.

Thank you|||Going across the network tends to add a bit of time to the backups, but you are right, 11 hours is a tad excessive. The maintenance plan does not maintain indexes by any chance, does it?|||NO, I do the Optimization and Integrity checks on separate jobs.|||How long does it take to copy the backup file across the network?|||Going across the network tends to add a bit of time to the backups, but you are right, 11 hours is a tad excessive. The maintenance plan does not maintain indexes by any chance, does it?

Because they are separate jobs doesn't necessarily mean they are not over lapping. Are you sure they are scheduled far enough apart? Do these just run on say Sunday when a backup would not e running?|||Can you try a local backup to at least eliminate the network variable?|||Looking at your performance monitor countes should answer this question for you. Look at the Network Interface counters on both servers. See if you see a large Outbound or Inbound Queue length on either server. On the source server, see what the disk read queue length is. On the destination server, see what the disk write queue lenth is during this time.