Results 1 to 7 of 7
  1. #1
    Member
    Join Date
    Aug 2009
    Posts
    29
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default ANR2578W - missed its scheduled start up window

    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.JPGservice.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. #2
    Member
    Join Date
    Sep 2006
    Location
    India
    Posts
    340
    Thanks
    0
    Thanked 7 Times in 7 Posts

    Default

    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
    Hema

  3. #3
    Member
    Join Date
    Aug 2009
    Posts
    29
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Quote Originally Posted by Hema View Post
    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
    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.

  4. #4
    Moderator moon-buddy's Avatar
    Join Date
    Aug 2005
    Location
    Somewhere in the US
    Posts
    5,967
    Thanks
    4
    Thanked 236 Times in 231 Posts

    Default

    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.
    Ed

  5. #5
    Senior Member
    Join Date
    Nov 2009
    Location
    India
    Posts
    316
    Thanks
    2
    Thanked 19 Times in 19 Posts

    Default

    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.

  6. #6
    Member
    Join Date
    Jan 2006
    Location
    Almaty, Kazakhstan!
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Add this line to your dsm.opt:
    managedservices schedule

    Guess it should help!

  7. #7
    Newcomer
    Join Date
    Sep 2012
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Was there a fix to this?

Similar Threads

  1. Missed its scheduled start up window
    By LarryB in forum TSM Client
    Replies: 11
    Last Post: 07-20-2009, 05:43 PM
  2. Scheduled backup missed!
    By kyle007 in forum Backup / Archive Discussion
    Replies: 2
    Last Post: 04-10-2009, 04:29 AM
  3. Administrative scheduled missed
    By samuel44 in forum Scripting
    Replies: 5
    Last Post: 05-06-2008, 11:44 AM
  4. NODE has missed its scheduled startup window
    By gardenia in forum Backup / Archive Discussion
    Replies: 8
    Last Post: 11-01-2007, 02:54 AM
  5. Scheduled Backup Window inaccurate?
    By michellest in forum Backup / Archive Discussion
    Replies: 2
    Last Post: 05-03-2006, 06:11 PM

Posting Permissions

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