1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link 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 message will disappear after you have made at least 12 posts. Thank you for your cooperation.

ANR2578W - missed its scheduled start up window

Discussion in 'Microsoft SQL Server' started by jojo72, Apr 13, 2012.

  1. jojo72

    jojo72 New Member

    Joined:
    Aug 13, 2009
    Messages:
    29
    Likes Received:
    0
    HI!

    I got the report by following:

    2012-04-13 00:10 ANR2578W Schedule SQL_LOGS in domain MSSQL for node DB01_MSSQL has missed its scheduled start up window.
    2012-04-13 01:00 ANR2578W Schedule SQL_FULL in domain MSSQL for node DB01_MSSQL has missed its scheduled start up window.

    I have installed the agent Dataprotection for SQL server ver 5.5.5.1 (64 bit) at win2008server. TSM server is 5.5.1.0.

    I have tested manually backup at DP SQL Agent without problem.

    This node DB01_MSSQL is already assocated to both SQL_FULL and SQL_LOGS.

    tsm: BACKUP01_SERVER1>q assoc
    Session established with server BACKUP01_SERVER1: Windows
    Server Version 5, Release 5, Level 1.0
    Server date/time: 04/13/2012 09:06:55 Last access: 04/13/2012 08:29:29

    Policy Domain Name: MSSQL
    Schedule Name: SQL_FULL
    Associated Nodes: CSS-DB01_MSSQL DB-WIN-01_MSSQL DB01_MSSQL SCCM01_MSSQL

    Policy Domain Name: MSSQL
    Schedule Name: SQL_LOGS
    Associated Nodes: CSS-DB01_MSSQL DB-WIN-01_MSSQL DB01_MSSQL SCCM01_MSSQL

    Here is the schedule plan:

    tsm: BACKUP01_SERVER1>q sche mssql

    Domain * Schedule Name Action Start Date/Time Duration Period Day
    ------------ - ---------------- ------ -------------------- -------- ------ ---
    MSSQL SQL_FULL CMD 11/07/2008 21:00:00 4 H 1 D WD
    MSSQL SQL_LOGS CMD 11/07/2008 00:00:00 10 M 4 H Any

    Here is nodelist:

    tsm: BACKUP01_SERVER1>q node

    Node Name Platform Policy Domain Days Since Days Since Locked?
    Name Last Acce- Password
    ss Set
    ------------------------- -------- -------------- ---------- ---------- -------
    DB01 WinNT STANDARD <1 14 No
    DB01_MSSQL TDP MSS- MSSQL <1 14 No
    QL Win-
    64


    The service TSM MSSQL scheduler was tried to restart serveral times at client and still no result. serverinfo.JPG service.JPG

    The dsm.opt file:
    NODename db01_mssql
    CLUSTERnode no
    COMPRESSIon Off
    PASSWORDAccess Generate
    COMMMethod TCPip
    TCPPort 1500
    TCPServeraddress 10.10.10.172
    TCPWindowsize 63
    TCPBuffSize 32
    SCHEDMODE Polling

    schedlogname dsmsched_mssql.log
    errorlogname dsmerr_mssql.log

    schedlogRetention 14,d
    errorlogRetention 14,d

    INCLUDE "\...\meta\...\*" SqlDbMeta
    INCLUDE "\...\data\...\*" SqlDbData

    INCLUDE "\...\meta\...\log*" SqlLogMeta
    INCLUDE "\...\data\...\log*" SqlLogData

    I don't find any interest information at error logs (I can send the logs if needed).

    The batch-files at client is still there sqlfull.cmd and sqllog.cmd at c:\ directory.

    I need help, any ideas please?

    JOJO.
     
  2.  
  3. Hema

    Hema Member

    Joined:
    Sep 21, 2006
    Messages:
    340
    Likes Received:
    9
    Occupation:
    TSM Backup Consultant
    Location:
    India
    1/ Were you not able to start the TDP Scheduler service? what is the error you see when you attempt?
    2/ Did you see any api error related logs? check the windows event also
     
  4. jojo72

    jojo72 New Member

    Joined:
    Aug 13, 2009
    Messages:
    29
    Likes Received:
    0
    1: I have restarted TDP Scheduler service, og still going. There is appearing no error, and the scheduled job don't still start.

    2: No - i didn't find any error related to this.
     
  5. moon-buddy

    moon-buddy Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,072
    Likes Received:
    269
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    I am guessing that this is the only server/node that is not working.

    Is the node's normal backup running (for the OS and FS)? If this is not, correct this first

    I am further assuming that the TDP for SQL was installed correctly. Delete the Scheduler service for TDP and reinstall. If this still does not work, reinstall the TDP for SQL.
     
  6. tariq.kaifi

    tariq.kaifi Member

    Joined:
    Nov 1, 2009
    Messages:
    316
    Likes Received:
    22
    Location:
    India
    You can also see if there is ANR2716E in TSM actlog and notice the address TSM schedule prompter is trying to contact. Is that address correct?

    If incorrect, then this could just be the issue of wrong reverse DNS entries.
     
  7. i2r

    i2r New Member

    Joined:
    Jan 16, 2006
    Messages:
    25
    Likes Received:
    0
    Occupation:
    TSM support for our customerz!
    Location:
    Almaty, Kazakhstan!
    Add this line to your dsm.opt:
    managedservices schedule

    Guess it should help!
     
  8. MistaCee

    MistaCee New Member

    Joined:
    Sep 13, 2012
    Messages:
    1
    Likes Received:
    0
    Was there a fix to this?
     

Share This Page