Results 1 to 14 of 14
  1. #1
    Join Date
    Jul 2003
    Posts
    24

    Unanswered: Veritas Backup Very Slow

    Hi,

    The last five days, the SQL Server Production backups to tape have been incredibly slow. Actually, they don't complete because they have been going on for 60 hours. Everything on the servers (clustered production environment) seems fine. Nothing untoward unusual. Any ideas what could be causing it? We're thinking of rebooting tonight.

    Any help would be appreciated.

    Maria

  2. #2
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    Well, at least open the Task Manager on the box and see who is eating up CPU.

  3. #3
    Join Date
    Jul 2003
    Posts
    24
    Thanks for the response, but that's already been done with all the other initial trouble-shooting. Any other ideas?

  4. #4
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    Dump to disk then copy to tape?

    Is the tape drive physically attached to the machine, or is it on the network?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  5. #5
    Join Date
    Jul 2003
    Posts
    24
    Originally posted by Brett Kaiser
    Dump to disk then copy to tape?

    Is the tape drive physically attached to the machine, or is it on the network?
    Yes we do a complete backup to disk and then we do the copy to tape. The drive is attached to the network.

  6. #6
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    So you r not backing up to tape...your backing up to disk...

    How big is the db?

    NOTHING should take 60 hours....

    Have you checked the error logs?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  7. #7
    Join Date
    Jul 2003
    Posts
    24
    We back up to disk and then nightly, run a job which backs up to tape. Nothing else has changed.

  8. #8
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    Well, which is the problem...the dump or the copy..

    Have you run out of room on the HD?

    How many dumps do you leave there?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  9. #9
    Join Date
    Jul 2003
    Posts
    24
    The problem is with the Veritas Backup Exec portion of our backup strategy. Nightly, we backup to disk first, and then, we backup to tape. Two separate parts. The disk portion is not posing any issues. The backup to tape is what is concerning us. It is taking an enormous amount of time to complete and there does not seem to be anything else wrong or out of the ordinary.

  10. #10
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    Has your system administrator guy played recently with OU's and GP's? I've seen that cause a lot of headache and paradoxic situations, especially when while playing he/she didn't bother to document or at least remember the changes that had been made.

  11. #11
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    Ok, why are you dumping to disk AND dumping to tape?

    And across the network?

    I'm sorry, I've never used veritas, but I don't understand your maint philoshophy...
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  12. #12
    Join Date
    Jul 2003
    Posts
    24
    Originally posted by rdjabarov
    Has your system administrator guy played recently with OU's and GP's? I've seen that cause a lot of headache and paradoxic situations, especially when while playing he/she didn't bother to document or at least remember the changes that had been made.
    He says that he has not. What kind of issues do you feel that could cause?

  13. #13
    Join Date
    Jul 2003
    Posts
    24
    Originally posted by Brett Kaiser
    Ok, why are you dumping to disk AND dumping to tape?

    And across the network?

    I'm sorry, I've never used veritas, but I don't understand your maint philoshophy...
    We use veritas software to copy to tape and send it off-site. Disk backups are not maintained permanently, only for 24 to 48 hours depending on the server.

  14. #14
    Join Date
    Nov 2009
    Posts
    1

    Maybe you should consider some snapshotting solution

    Hi Thomadma,

    I am not sure how this will make you feel, but you might need to consider some storage snapshotting solution that can integrate with your backup software to avoid the long backup window. I am not sure if Veritas is capable of doing this. Though we had tried IBM Tivoli FlashCopy Manager which integrate with IBM Tivoli Storage Manager & DS5000 in our environment. It has been amazing for us as it dropped our backup windows to 30 seconds from 20 hours. In addition, we started being able to restore a 300 GB Database in about 2 minutes instead of 6 hours which is great for us. I have followed the following guide posted by TSMGuru while doing our testing & thought I will share it with you as it might be useful to find out about this idea & how you might be able match it within your own environment:

    IBM Tivoli Storage FlashCopy Manager Tutorial


    I hope that help some one, & enjoy,
    digg1980
    Linux 2 Aix unix Blog

Posting Permissions

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