1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

TDP for SQL automatic inactivation too slow

Discussion in 'Backup / Archive Discussion' started by blew, Jul 31, 2017.

  1. blew

    blew ADSM.ORG Member

    Joined:
    Jul 27, 2009
    Messages:
    14
    Likes Received:
    2
    Occupation:
    System Engineer - Backup system administrator
    Location:
    Rome
    Hi,
    I've an SQL instance with 330 DBs (11TB) and we backups logs every hour. After full backup the automatic inactivation process take long time (even 15 hours!) to end.
    Have you experience with SQL instances with more than 200 DBs? Is it a normal situation?
    We backup many smaller instances with the same strategies and inactivation process does not take more than some minutes.

    TSM 7.1.6 on linux RedHat 6
    TDP for SQL 7.1.2 on Windows 2008 R2
    TSM api 7.1.6

    any suggestion is appreciated
     
  2.  
  3. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,827
    Likes Received:
    358
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Are you using TSM to schedule the backups? If so, can you split the backups into multiple node associations wherein one node holds only 50 DB instances? This should speed things up.

    Alternatively, use SQL agent to manager the backup rather than using TSM scheduler.
     

Share This Page