Results 1 to 10 of 10
  1. #1
    Join Date
    Feb 2004
    Posts
    52

    Question Unanswered: 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 you

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Kind 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.

  3. #3
    Join Date
    Dec 2002
    Location
    Sunny Florida
    Posts
    121
    If tape is it running at the same time on the same machine and same drive?

  4. #4
    Join Date
    Feb 2004
    Posts
    52
    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

  5. #5
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    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?

  6. #6
    Join Date
    Feb 2004
    Posts
    52
    NO, I do the Optimization and Integrity checks on separate jobs.

  7. #7
    Join Date
    Dec 2002
    Location
    Sunny Florida
    Posts
    121
    How long does it take to copy the backup file across the network?

  8. #8
    Join Date
    Dec 2002
    Location
    Sunny Florida
    Posts
    121
    Quote Originally Posted by MCrowley
    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?
    Last edited by DBA-ONE; 12-16-04 at 14:49.

  9. #9
    Join Date
    Dec 2004
    Location
    CA, USA
    Posts
    63

    try local

    Can you try a local backup to at least eliminate the network variable?

  10. #10
    Join Date
    Apr 2004
    Location
    Kansas City, MO
    Posts
    734
    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.
    MeanOldDBA
    derrickleggett@hotmail.com
    When life gives you a lemon, fire the DBA.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •