Scheduled bakcup jobs do not execute. - Veritas Net Backup

This is a discussion on Scheduled bakcup jobs do not execute. - Veritas Net Backup ; Hi ~~ Sometimes, netbakcup's scheduled backup jobs do not execute. I don't know this reason. backup policy, schedule, bakcup windows are all normal condition. But any logs are not logged and cannot see any activities in Activity Mornitor tab. And ...

+ Reply to Thread
Results 1 to 12 of 12

Thread: Scheduled bakcup jobs do not execute.

  1. Scheduled bakcup jobs do not execute.



    Hi ~~
    Sometimes, netbakcup's scheduled backup jobs do not execute.

    I don't know this reason.

    backup policy, schedule, bakcup windows are all normal condition.

    But any logs are not logged and cannot see any activities in Activity Mornitor
    tab.

    And cannot see any logs because scheduled jobs were not executed.

    I wonder that scheduled jobs were not executed same this case.

    Please give me a hands.. if you have solutions or case.

    Thanks in advance.




  2. Re: Scheduled bakcup jobs do not execute.

    The best place to look to find out why a job failed to run is in the
    bpsched log on the master. You can search the log for the client name
    or the policy name and it should spell out exactly why the job was not
    run.

    Jeff


    On 27 Apr 2005 21:53:58 -0500, "chalse kim" wrote:

    >
    >
    >Hi ~~
    >Sometimes, netbakcup's scheduled backup jobs do not execute.
    >
    >I don't know this reason.
    >
    >backup policy, schedule, bakcup windows are all normal condition.
    >
    >But any logs are not logged and cannot see any activities in Activity Mornitor
    >tab.
    >
    >And cannot see any logs because scheduled jobs were not executed.
    >
    >I wonder that scheduled jobs were not executed same this case.
    >
    >Please give me a hands.. if you have solutions or case.
    >
    >Thanks in advance.
    >
    >



  3. Re: Scheduled bakcup jobs do not execute.

    Hi,

    I have the same problem... I try to find errors on bpsched log file but I
    can't find error about skipped clients
    or the reasons for the skipped backup job.
    Instead I found many rows like this:

    21:02:22.472 [11128.10976] <8> get_failure_count: cannot list C:\Program
    Files\VERITAS\NetBackup\db\failure_history: No error (0)

    The jobs not executed are those with full backup policy.
    The schedules for all my policy are:
    Name | Type | Retention | Frequency
    -------------------------------------------
    year | Full | infinity | 54 weeks
    month | Full | 6 months | 4 weeks
    week | Full | 3 weeks | 1 week
    day | Diff. Incr. | 2 weeks | 1 Day

    Differential backup on: Mon, Tue, Wed, Thu
    Full backup on: Fri

    Help me please!

    "Jeff Redington" ha scritto nel messaggio
    news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    > The best place to look to find out why a job failed to run is in the
    > bpsched log on the master. You can search the log for the client name
    > or the policy name and it should spell out exactly why the job was not
    > run.
    >
    > Jeff
    >
    >
    > On 27 Apr 2005 21:53:58 -0500, "chalse kim" wrote:
    >
    >>
    >>
    >>Hi ~~
    >>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>
    >>I don't know this reason.
    >>
    >>backup policy, schedule, bakcup windows are all normal condition.
    >>
    >>But any logs are not logged and cannot see any activities in Activity
    >>Mornitor
    >>tab.
    >>
    >>And cannot see any logs because scheduled jobs were not executed.
    >>
    >>I wonder that scheduled jobs were not executed same this case.
    >>
    >>Please give me a hands.. if you have solutions or case.
    >>
    >>Thanks in advance.
    >>
    >>

    >




  4. Re: Scheduled bakcup jobs do not execute.

    Don't look for an error message in the bpsched. Look for the name of
    the policy and it should explain when you find it why it chose not to
    run it. If the bpsched thinks there was a good reason not to run the
    policy it wont list that as an error in the logs.

    Jeff

    On Mon, 9 May 2005 12:05:59 +0200, "Massimo Dalla Giustina"
    wrote:

    >Hi,
    >
    >I have the same problem... I try to find errors on bpsched log file but I
    >can't find error about skipped clients
    >or the reasons for the skipped backup job.
    >Instead I found many rows like this:
    >
    >21:02:22.472 [11128.10976] <8> get_failure_count: cannot list C:\Program
    >Files\VERITAS\NetBackup\db\failure_history: No error (0)
    >
    >The jobs not executed are those with full backup policy.
    >The schedules for all my policy are:
    >Name | Type | Retention | Frequency
    >-------------------------------------------
    >year | Full | infinity | 54 weeks
    >month | Full | 6 months | 4 weeks
    >week | Full | 3 weeks | 1 week
    >day | Diff. Incr. | 2 weeks | 1 Day
    >
    >Differential backup on: Mon, Tue, Wed, Thu
    >Full backup on: Fri
    >
    >Help me please!
    >
    >"Jeff Redington" ha scritto nel messaggio
    >news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    >> The best place to look to find out why a job failed to run is in the
    >> bpsched log on the master. You can search the log for the client name
    >> or the policy name and it should spell out exactly why the job was not
    >> run.
    >>
    >> Jeff
    >>
    >>
    >> On 27 Apr 2005 21:53:58 -0500, "chalse kim" wrote:
    >>
    >>>
    >>>
    >>>Hi ~~
    >>>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>>
    >>>I don't know this reason.
    >>>
    >>>backup policy, schedule, bakcup windows are all normal condition.
    >>>
    >>>But any logs are not logged and cannot see any activities in Activity
    >>>Mornitor
    >>>tab.
    >>>
    >>>And cannot see any logs because scheduled jobs were not executed.
    >>>
    >>>I wonder that scheduled jobs were not executed same this case.
    >>>
    >>>Please give me a hands.. if you have solutions or case.
    >>>
    >>>Thanks in advance.
    >>>
    >>>

    >>

    >



  5. Re: Scheduled bakcup jobs do not execute.

    Thanks Jeff,

    In fact I'm look for the reason not for errors.... but I can't find it.
    If you look at the logs at the bottom, you can find that server1, server2
    and server3 are not listed in any retention level worklists.
    I notice also that the sequence:

    <2> read_schedinfo: No specific include dates entered
    <2> read_schedinfo: No days of week entered
    <2> read_schedinfo: No specific exclude dates entered

    is not repeated fo server1, server2 and server3.
    Is this the reason?
    If so, what can I do?

    Here the logs:

    21:02:18.175 [11128.10976] <2> merge_partials: Merging changes for server1
    server1
    21:02:18.315 [11128.10976] <2> merge_partials: Merging changes for server2
    server2
    21:02:18.409 [11128.10976] <2> merge_partials: Merging changes for server3
    server3
    21:02:18.487 [11128.10976] <2> merge_partials: Merging changes for server4
    server4
    21:02:18.565 [11128.10976] <2> read_schedinfo: No specific include dates
    entered
    21:02:18.565 [11128.10976] <2> read_schedinfo: No days of week entered
    21:02:18.565 [11128.10976] <2> read_schedinfo: No specific exclude dates
    entered
    ......
    21:02:18.706 [11128.10976] <2> merge_partials: Merging changes for server5
    server5
    21:02:18.847 [11128.10976] <2> read_schedinfo: No specific include dates
    entered
    21:02:18.847 [11128.10976] <2> read_schedinfo: No days of week entered
    21:02:18.847 [11128.10976] <2> read_schedinfo: No specific exclude dates
    entered
    ......
    21:02:19.190 [11128.10976] <2> merge_partials: Merging changes for server6
    server6
    21:02:20.128 [11128.10976] <2> read_schedinfo: No specific include dates
    entered
    21:02:20.128 [11128.10976] <2> read_schedinfo: No days of week entered
    21:02:20.128 [11128.10976] <2> read_schedinfo: No specific exclude dates
    entered
    .......
    21:02:21.331 [11128.10976] <2> merge_partials: Merging changes for server7
    server7
    21:02:21.472 [11128.10976] <2> read_schedinfo: No specific include dates
    entered
    21:02:21.472 [11128.10976] <2> read_schedinfo: No days of week entered
    21:02:21.472 [11128.10976] <2> read_schedinfo: No specific exclude dates
    entered
    .......
    21:02:21.597 [11128.10976] <2> merge_partials: Merging changes for server8
    server8
    21:02:21.675 [11128.10976] <2> read_schedinfo: No specific include dates
    entered
    21:02:21.675 [11128.10976] <2> read_schedinfo: No days of week entered
    21:02:21.675 [11128.10976] <2> read_schedinfo: No specific exclude dates
    entered
    ......
    21:02:21.785 [11128.10976] <2> merge_partials: Merging changes for server9
    server9
    21:02:21.941 [11128.10976] <2> read_schedinfo: No specific include dates
    entered
    21:02:21.941 [11128.10976] <2> read_schedinfo: No days of week entered
    21:02:21.941 [11128.10976] <2> read_schedinfo: No specific exclude dates
    entered
    .......
    21:02:22.082 [11128.10976] <2> merge_partials: Merging changes for server10
    server10
    21:02:22.300 [11128.10976] <2> read_schedinfo: No specific include dates
    entered
    21:02:22.300 [11128.10976] <2> read_schedinfo: No days of week entered
    21:02:22.300 [11128.10976] <2> read_schedinfo: No specific exclude dates
    entered
    .......
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 24 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 23 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 22 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 21 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 20 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 19 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 18 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 17 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 16 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 15 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 14 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 13 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 12 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 11 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 10 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 9 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 8 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 7 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 6 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    Mensile (FULL) part 15
    21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7 sched:
    Mensile (FULL) part 1
    21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7 sched:
    Mensile (FULL) part 2
    21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8 sched:
    Mensile (FULL) part 1
    21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8 sched:
    Mensile (FULL) part 2
    21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9 sched:
    Mensile (FULL) part 1
    21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9 sched:
    Mensile (FULL) part 2
    21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    sched: Mensile (FULL) part 1
    21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    sched: Mensile (FULL) part 2
    21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    sched: Mensile (FULL) part 3
    21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    sched: Mensile (FULL) part 4
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 5 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 4 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 3 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 2 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    Settimanale (FULL) part 14
    21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4 sched:
    Settimanale (FULL) part 1
    21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4 sched:
    Settimanale (FULL) part 2
    21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    Settimanale (FULL) part 1
    21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    Settimanale (FULL) part 2
    21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    Settimanale (FULL) part 3
    21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    Settimanale (FULL) part 4
    21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    Settimanale (FULL) part 5
    21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    Settimanale (FULL) part 8
    21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    Settimanale (FULL) part 9
    21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    Settimanale (FULL) part 10
    21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    Settimanale (FULL) part 11
    21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    Settimanale (FULL) part 12
    21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    Settimanale (FULL) part 13
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 1 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 0 WORKLIST
    21:02:22.488 [11128.10976] <2> ?: --------------------------
    21:02:22.519 [11356.10212] <2> bpsched: INITIATING (verbose=0) ...



    "Jeff Redington" ha scritto nel messaggio
    news:uuev71d9jl4qvunqcksjf64397ub9jik0f@4ax.com...
    > Don't look for an error message in the bpsched. Look for the name of
    > the policy and it should explain when you find it why it chose not to
    > run it. If the bpsched thinks there was a good reason not to run the
    > policy it wont list that as an error in the logs.
    >
    > Jeff
    >
    > On Mon, 9 May 2005 12:05:59 +0200, "Massimo Dalla Giustina"
    > wrote:
    >
    >>Hi,
    >>
    >>I have the same problem... I try to find errors on bpsched log file but I
    >>can't find error about skipped clients
    >>or the reasons for the skipped backup job.
    >>Instead I found many rows like this:
    >>
    >>21:02:22.472 [11128.10976] <8> get_failure_count: cannot list C:\Program
    >>Files\VERITAS\NetBackup\db\failure_history: No error (0)
    >>
    >>The jobs not executed are those with full backup policy.
    >>The schedules for all my policy are:
    >>Name | Type | Retention | Frequency
    >>-------------------------------------------
    >>year | Full | infinity | 54 weeks
    >>month | Full | 6 months | 4 weeks
    >>week | Full | 3 weeks | 1 week
    >>day | Diff. Incr. | 2 weeks | 1 Day
    >>
    >>Differential backup on: Mon, Tue, Wed, Thu
    >>Full backup on: Fri
    >>
    >>Help me please!
    >>
    >>"Jeff Redington" ha scritto nel messaggio
    >>news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    >>> The best place to look to find out why a job failed to run is in the
    >>> bpsched log on the master. You can search the log for the client name
    >>> or the policy name and it should spell out exactly why the job was not
    >>> run.
    >>>
    >>> Jeff
    >>>
    >>>
    >>> On 27 Apr 2005 21:53:58 -0500, "chalse kim" wrote:
    >>>
    >>>>
    >>>>
    >>>>Hi ~~
    >>>>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>>>
    >>>>I don't know this reason.
    >>>>
    >>>>backup policy, schedule, bakcup windows are all normal condition.
    >>>>
    >>>>But any logs are not logged and cannot see any activities in Activity
    >>>>Mornitor
    >>>>tab.
    >>>>
    >>>>And cannot see any logs because scheduled jobs were not executed.
    >>>>
    >>>>I wonder that scheduled jobs were not executed same this case.
    >>>>
    >>>>Please give me a hands.. if you have solutions or case.
    >>>>
    >>>>Thanks in advance.
    >>>>
    >>>>
    >>>

    >>

    >




  6. Re: Scheduled bakcup jobs do not execute.

    Are those the only references to the servers or policies for those
    backups? I am expecting to see it perform the worklist build around
    the time the job was supposed to start and then it should say
    something like skipping backup due to ... or backup not needed because
    it has already run. There should be a message like that. Follow the
    bpsched back in time to 1-2 hours before the job should have kicked
    off and see if there is anything else you see regarding that client or
    policy.

    Jeff

    On Tue, 10 May 2005 15:56:48 +0200, "Massimo Dalla Giustina"
    wrote:

    >Thanks Jeff,
    >
    >In fact I'm look for the reason not for errors.... but I can't find it.
    >If you look at the logs at the bottom, you can find that server1, server2
    >and server3 are not listed in any retention level worklists.
    >I notice also that the sequence:
    >
    ><2> read_schedinfo: No specific include dates entered
    ><2> read_schedinfo: No days of week entered
    ><2> read_schedinfo: No specific exclude dates entered
    >
    >is not repeated fo server1, server2 and server3.
    >Is this the reason?
    >If so, what can I do?
    >
    >Here the logs:
    >
    >21:02:18.175 [11128.10976] <2> merge_partials: Merging changes for server1
    >server1
    >21:02:18.315 [11128.10976] <2> merge_partials: Merging changes for server2
    >server2
    >21:02:18.409 [11128.10976] <2> merge_partials: Merging changes for server3
    >server3
    >21:02:18.487 [11128.10976] <2> merge_partials: Merging changes for server4
    >server4
    >21:02:18.565 [11128.10976] <2> read_schedinfo: No specific include dates
    >entered
    >21:02:18.565 [11128.10976] <2> read_schedinfo: No days of week entered
    >21:02:18.565 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >entered
    >.....
    >21:02:18.706 [11128.10976] <2> merge_partials: Merging changes for server5
    >server5
    >21:02:18.847 [11128.10976] <2> read_schedinfo: No specific include dates
    >entered
    >21:02:18.847 [11128.10976] <2> read_schedinfo: No days of week entered
    >21:02:18.847 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >entered
    >.....
    >21:02:19.190 [11128.10976] <2> merge_partials: Merging changes for server6
    >server6
    >21:02:20.128 [11128.10976] <2> read_schedinfo: No specific include dates
    >entered
    >21:02:20.128 [11128.10976] <2> read_schedinfo: No days of week entered
    >21:02:20.128 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >entered
    >......
    >21:02:21.331 [11128.10976] <2> merge_partials: Merging changes for server7
    >server7
    >21:02:21.472 [11128.10976] <2> read_schedinfo: No specific include dates
    >entered
    >21:02:21.472 [11128.10976] <2> read_schedinfo: No days of week entered
    >21:02:21.472 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >entered
    >......
    >21:02:21.597 [11128.10976] <2> merge_partials: Merging changes for server8
    >server8
    >21:02:21.675 [11128.10976] <2> read_schedinfo: No specific include dates
    >entered
    >21:02:21.675 [11128.10976] <2> read_schedinfo: No days of week entered
    >21:02:21.675 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >entered
    >.....
    >21:02:21.785 [11128.10976] <2> merge_partials: Merging changes for server9
    >server9
    >21:02:21.941 [11128.10976] <2> read_schedinfo: No specific include dates
    >entered
    >21:02:21.941 [11128.10976] <2> read_schedinfo: No days of week entered
    >21:02:21.941 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >entered
    >......
    >21:02:22.082 [11128.10976] <2> merge_partials: Merging changes for server10
    >server10
    >21:02:22.300 [11128.10976] <2> read_schedinfo: No specific include dates
    >entered
    >21:02:22.300 [11128.10976] <2> read_schedinfo: No days of week entered
    >21:02:22.300 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >entered
    >......
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 24 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 23 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 22 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 21 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 20 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 19 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 18 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 17 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 16 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 15 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 14 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 13 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 12 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 11 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 10 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 9 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 8 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 7 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 6 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    >Mensile (FULL) part 15
    >21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7 sched:
    >Mensile (FULL) part 1
    >21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7 sched:
    >Mensile (FULL) part 2
    >21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8 sched:
    >Mensile (FULL) part 1
    >21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8 sched:
    >Mensile (FULL) part 2
    >21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9 sched:
    >Mensile (FULL) part 1
    >21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9 sched:
    >Mensile (FULL) part 2
    >21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >sched: Mensile (FULL) part 1
    >21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >sched: Mensile (FULL) part 2
    >21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >sched: Mensile (FULL) part 3
    >21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >sched: Mensile (FULL) part 4
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 5 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 4 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 3 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 2 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    >Settimanale (FULL) part 14
    >21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4 sched:
    >Settimanale (FULL) part 1
    >21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4 sched:
    >Settimanale (FULL) part 2
    >21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    >Settimanale (FULL) part 1
    >21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    >Settimanale (FULL) part 2
    >21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    >Settimanale (FULL) part 3
    >21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    >Settimanale (FULL) part 4
    >21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5 sched:
    >Settimanale (FULL) part 5
    >21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    >Settimanale (FULL) part 8
    >21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    >Settimanale (FULL) part 9
    >21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    >Settimanale (FULL) part 10
    >21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    >Settimanale (FULL) part 11
    >21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    >Settimanale (FULL) part 12
    >21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6 sched:
    >Settimanale (FULL) part 13
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 1 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 0 WORKLIST
    >21:02:22.488 [11128.10976] <2> ?: --------------------------
    >21:02:22.519 [11356.10212] <2> bpsched: INITIATING (verbose=0) ...
    >
    >
    >
    >"Jeff Redington" ha scritto nel messaggio
    >news:uuev71d9jl4qvunqcksjf64397ub9jik0f@4ax.com...
    >> Don't look for an error message in the bpsched. Look for the name of
    >> the policy and it should explain when you find it why it chose not to
    >> run it. If the bpsched thinks there was a good reason not to run the
    >> policy it wont list that as an error in the logs.
    >>
    >> Jeff
    >>
    >> On Mon, 9 May 2005 12:05:59 +0200, "Massimo Dalla Giustina"
    >> wrote:
    >>
    >>>Hi,
    >>>
    >>>I have the same problem... I try to find errors on bpsched log file but I
    >>>can't find error about skipped clients
    >>>or the reasons for the skipped backup job.
    >>>Instead I found many rows like this:
    >>>
    >>>21:02:22.472 [11128.10976] <8> get_failure_count: cannot list C:\Program
    >>>Files\VERITAS\NetBackup\db\failure_history: No error (0)
    >>>
    >>>The jobs not executed are those with full backup policy.
    >>>The schedules for all my policy are:
    >>>Name | Type | Retention | Frequency
    >>>-------------------------------------------
    >>>year | Full | infinity | 54 weeks
    >>>month | Full | 6 months | 4 weeks
    >>>week | Full | 3 weeks | 1 week
    >>>day | Diff. Incr. | 2 weeks | 1 Day
    >>>
    >>>Differential backup on: Mon, Tue, Wed, Thu
    >>>Full backup on: Fri
    >>>
    >>>Help me please!
    >>>
    >>>"Jeff Redington" ha scritto nel messaggio
    >>>news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    >>>> The best place to look to find out why a job failed to run is in the
    >>>> bpsched log on the master. You can search the log for the client name
    >>>> or the policy name and it should spell out exactly why the job was not
    >>>> run.
    >>>>
    >>>> Jeff
    >>>>
    >>>>
    >>>> On 27 Apr 2005 21:53:58 -0500, "chalse kim" wrote:
    >>>>
    >>>>>
    >>>>>
    >>>>>Hi ~~
    >>>>>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>>>>
    >>>>>I don't know this reason.
    >>>>>
    >>>>>backup policy, schedule, bakcup windows are all normal condition.
    >>>>>
    >>>>>But any logs are not logged and cannot see any activities in Activity
    >>>>>Mornitor
    >>>>>tab.
    >>>>>
    >>>>>And cannot see any logs because scheduled jobs were not executed.
    >>>>>
    >>>>>I wonder that scheduled jobs were not executed same this case.
    >>>>>
    >>>>>Please give me a hands.. if you have solutions or case.
    >>>>>
    >>>>>Thanks in advance.
    >>>>>
    >>>>>
    >>>>
    >>>

    >>

    >



  7. Re: Scheduled bakcup jobs do not execute.

    I can't find what you are indicating to me... In the attachment you can find
    the entire log file.

    I'm using Veritas NetBackup 5.0MP5 for Windows on a Win2003 server.

    "Jeff Redington" ha scritto nel messaggio
    news:j1g181ppf5fg0rk3jos1pj261ka8btj994@4ax.com...
    > Are those the only references to the servers or policies for those
    > backups? I am expecting to see it perform the worklist build around
    > the time the job was supposed to start and then it should say
    > something like skipping backup due to ... or backup not needed because
    > it has already run. There should be a message like that. Follow the
    > bpsched back in time to 1-2 hours before the job should have kicked
    > off and see if there is anything else you see regarding that client or
    > policy.
    >
    > Jeff
    >
    > On Tue, 10 May 2005 15:56:48 +0200, "Massimo Dalla Giustina"
    > wrote:
    >
    >>Thanks Jeff,
    >>
    >>In fact I'm look for the reason not for errors.... but I can't find it.
    >>If you look at the logs at the bottom, you can find that server1, server2
    >>and server3 are not listed in any retention level worklists.
    >>I notice also that the sequence:
    >>
    >><2> read_schedinfo: No specific include dates entered
    >><2> read_schedinfo: No days of week entered
    >><2> read_schedinfo: No specific exclude dates entered
    >>
    >>is not repeated fo server1, server2 and server3.
    >>Is this the reason?
    >>If so, what can I do?
    >>
    >>Here the logs:
    >>
    >>21:02:18.175 [11128.10976] <2> merge_partials: Merging changes for server1
    >>server1
    >>21:02:18.315 [11128.10976] <2> merge_partials: Merging changes for server2
    >>server2
    >>21:02:18.409 [11128.10976] <2> merge_partials: Merging changes for server3
    >>server3
    >>21:02:18.487 [11128.10976] <2> merge_partials: Merging changes for server4
    >>server4
    >>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific include dates
    >>entered
    >>21:02:18.565 [11128.10976] <2> read_schedinfo: No days of week entered
    >>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>entered
    >>.....
    >>21:02:18.706 [11128.10976] <2> merge_partials: Merging changes for server5
    >>server5
    >>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific include dates
    >>entered
    >>21:02:18.847 [11128.10976] <2> read_schedinfo: No days of week entered
    >>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>entered
    >>.....
    >>21:02:19.190 [11128.10976] <2> merge_partials: Merging changes for server6
    >>server6
    >>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific include dates
    >>entered
    >>21:02:20.128 [11128.10976] <2> read_schedinfo: No days of week entered
    >>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>entered
    >>......
    >>21:02:21.331 [11128.10976] <2> merge_partials: Merging changes for server7
    >>server7
    >>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific include dates
    >>entered
    >>21:02:21.472 [11128.10976] <2> read_schedinfo: No days of week entered
    >>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>entered
    >>......
    >>21:02:21.597 [11128.10976] <2> merge_partials: Merging changes for server8
    >>server8
    >>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific include dates
    >>entered
    >>21:02:21.675 [11128.10976] <2> read_schedinfo: No days of week entered
    >>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>entered
    >>.....
    >>21:02:21.785 [11128.10976] <2> merge_partials: Merging changes for server9
    >>server9
    >>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific include dates
    >>entered
    >>21:02:21.941 [11128.10976] <2> read_schedinfo: No days of week entered
    >>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>entered
    >>......
    >>21:02:22.082 [11128.10976] <2> merge_partials: Merging changes for
    >>server10
    >>server10
    >>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific include dates
    >>entered
    >>21:02:22.300 [11128.10976] <2> read_schedinfo: No days of week entered
    >>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>entered
    >>......
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 24 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 23 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 22 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 21 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 20 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 19 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 18 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 17 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 16 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 15 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 14 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 13 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 12 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 11 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 10 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 9 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 8 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 7 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 6 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>sched:
    >>Mensile (FULL) part 15
    >>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>sched:
    >>Mensile (FULL) part 1
    >>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>sched:
    >>Mensile (FULL) part 2
    >>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>sched:
    >>Mensile (FULL) part 1
    >>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>sched:
    >>Mensile (FULL) part 2
    >>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>sched:
    >>Mensile (FULL) part 1
    >>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>sched:
    >>Mensile (FULL) part 2
    >>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>sched: Mensile (FULL) part 1
    >>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>sched: Mensile (FULL) part 2
    >>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>sched: Mensile (FULL) part 3
    >>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>sched: Mensile (FULL) part 4
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 5 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 4 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 3 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 2 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>sched:
    >>Settimanale (FULL) part 14
    >>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>sched:
    >>Settimanale (FULL) part 1
    >>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>sched:
    >>Settimanale (FULL) part 2
    >>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>sched:
    >>Settimanale (FULL) part 1
    >>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>sched:
    >>Settimanale (FULL) part 2
    >>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>sched:
    >>Settimanale (FULL) part 3
    >>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>sched:
    >>Settimanale (FULL) part 4
    >>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>sched:
    >>Settimanale (FULL) part 5
    >>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>sched:
    >>Settimanale (FULL) part 8
    >>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>sched:
    >>Settimanale (FULL) part 9
    >>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>sched:
    >>Settimanale (FULL) part 10
    >>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>sched:
    >>Settimanale (FULL) part 11
    >>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>sched:
    >>Settimanale (FULL) part 12
    >>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>sched:
    >>Settimanale (FULL) part 13
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 1 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 0 WORKLIST
    >>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>21:02:22.519 [11356.10212] <2> bpsched: INITIATING (verbose=0) ...
    >>
    >>
    >>
    >>"Jeff Redington" ha scritto nel messaggio
    >>news:uuev71d9jl4qvunqcksjf64397ub9jik0f@4ax.com...
    >>> Don't look for an error message in the bpsched. Look for the name of
    >>> the policy and it should explain when you find it why it chose not to
    >>> run it. If the bpsched thinks there was a good reason not to run the
    >>> policy it wont list that as an error in the logs.
    >>>
    >>> Jeff
    >>>
    >>> On Mon, 9 May 2005 12:05:59 +0200, "Massimo Dalla Giustina"
    >>> wrote:
    >>>
    >>>>Hi,
    >>>>
    >>>>I have the same problem... I try to find errors on bpsched log file but
    >>>>I
    >>>>can't find error about skipped clients
    >>>>or the reasons for the skipped backup job.
    >>>>Instead I found many rows like this:
    >>>>
    >>>>21:02:22.472 [11128.10976] <8> get_failure_count: cannot list C:\Program
    >>>>Files\VERITAS\NetBackup\db\failure_history: No error (0)
    >>>>
    >>>>The jobs not executed are those with full backup policy.
    >>>>The schedules for all my policy are:
    >>>>Name | Type | Retention | Frequency
    >>>>-------------------------------------------
    >>>>year | Full | infinity | 54 weeks
    >>>>month | Full | 6 months | 4 weeks
    >>>>week | Full | 3 weeks | 1 week
    >>>>day | Diff. Incr. | 2 weeks | 1 Day
    >>>>
    >>>>Differential backup on: Mon, Tue, Wed, Thu
    >>>>Full backup on: Fri
    >>>>
    >>>>Help me please!
    >>>>
    >>>>"Jeff Redington" ha scritto nel messaggio
    >>>>news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    >>>>> The best place to look to find out why a job failed to run is in the
    >>>>> bpsched log on the master. You can search the log for the client name
    >>>>> or the policy name and it should spell out exactly why the job was not
    >>>>> run.
    >>>>>
    >>>>> Jeff
    >>>>>
    >>>>>
    >>>>> On 27 Apr 2005 21:53:58 -0500, "chalse kim" wrote:
    >>>>>
    >>>>>>
    >>>>>>
    >>>>>>Hi ~~
    >>>>>>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>>>>>
    >>>>>>I don't know this reason.
    >>>>>>
    >>>>>>backup policy, schedule, bakcup windows are all normal condition.
    >>>>>>
    >>>>>>But any logs are not logged and cannot see any activities in Activity
    >>>>>>Mornitor
    >>>>>>tab.
    >>>>>>
    >>>>>>And cannot see any logs because scheduled jobs were not executed.
    >>>>>>
    >>>>>>I wonder that scheduled jobs were not executed same this case.
    >>>>>>
    >>>>>>Please give me a hands.. if you have solutions or case.
    >>>>>>
    >>>>>>Thanks in advance.
    >>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>

    >>

    >






  8. Re: Scheduled bakcup jobs do not execute.

    After reviewing the logs I am as baffled as you. There is nothing to
    indicate why it is not running those jobs. Are they all in the same
    policy? Try creating a new policy for those 3 servers and see if it
    works. If not, try increasing the verbosity for the bpsched logs to 2
    or 3 and then send me the bpsched logs after that change.

    Jeff


    On Tue, 10 May 2005 16:56:58 +0200, "Massimo Dalla Giustina"
    wrote:

    >I can't find what you are indicating to me... In the attachment you can find
    >the entire log file.
    >
    >I'm using Veritas NetBackup 5.0MP5 for Windows on a Win2003 server.
    >
    >"Jeff Redington" ha scritto nel messaggio
    >news:j1g181ppf5fg0rk3jos1pj261ka8btj994@4ax.com...
    >> Are those the only references to the servers or policies for those
    >> backups? I am expecting to see it perform the worklist build around
    >> the time the job was supposed to start and then it should say
    >> something like skipping backup due to ... or backup not needed because
    >> it has already run. There should be a message like that. Follow the
    >> bpsched back in time to 1-2 hours before the job should have kicked
    >> off and see if there is anything else you see regarding that client or
    >> policy.
    >>
    >> Jeff
    >>
    >> On Tue, 10 May 2005 15:56:48 +0200, "Massimo Dalla Giustina"
    >> wrote:
    >>
    >>>Thanks Jeff,
    >>>
    >>>In fact I'm look for the reason not for errors.... but I can't find it.
    >>>If you look at the logs at the bottom, you can find that server1, server2
    >>>and server3 are not listed in any retention level worklists.
    >>>I notice also that the sequence:
    >>>
    >>><2> read_schedinfo: No specific include dates entered
    >>><2> read_schedinfo: No days of week entered
    >>><2> read_schedinfo: No specific exclude dates entered
    >>>
    >>>is not repeated fo server1, server2 and server3.
    >>>Is this the reason?
    >>>If so, what can I do?
    >>>
    >>>Here the logs:
    >>>
    >>>21:02:18.175 [11128.10976] <2> merge_partials: Merging changes for server1
    >>>server1
    >>>21:02:18.315 [11128.10976] <2> merge_partials: Merging changes for server2
    >>>server2
    >>>21:02:18.409 [11128.10976] <2> merge_partials: Merging changes for server3
    >>>server3
    >>>21:02:18.487 [11128.10976] <2> merge_partials: Merging changes for server4
    >>>server4
    >>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>entered
    >>>21:02:18.565 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>entered
    >>>.....
    >>>21:02:18.706 [11128.10976] <2> merge_partials: Merging changes for server5
    >>>server5
    >>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>entered
    >>>21:02:18.847 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>entered
    >>>.....
    >>>21:02:19.190 [11128.10976] <2> merge_partials: Merging changes for server6
    >>>server6
    >>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>entered
    >>>21:02:20.128 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>entered
    >>>......
    >>>21:02:21.331 [11128.10976] <2> merge_partials: Merging changes for server7
    >>>server7
    >>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>entered
    >>>21:02:21.472 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>entered
    >>>......
    >>>21:02:21.597 [11128.10976] <2> merge_partials: Merging changes for server8
    >>>server8
    >>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>entered
    >>>21:02:21.675 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>entered
    >>>.....
    >>>21:02:21.785 [11128.10976] <2> merge_partials: Merging changes for server9
    >>>server9
    >>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>entered
    >>>21:02:21.941 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>entered
    >>>......
    >>>21:02:22.082 [11128.10976] <2> merge_partials: Merging changes for
    >>>server10
    >>>server10
    >>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>entered
    >>>21:02:22.300 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>entered
    >>>......
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 24 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 23 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 22 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 21 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 20 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 19 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 18 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 17 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 16 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 15 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 14 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 13 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 12 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 11 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 10 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 9 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 8 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 7 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 6 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>sched:
    >>>Mensile (FULL) part 15
    >>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>sched:
    >>>Mensile (FULL) part 1
    >>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>sched:
    >>>Mensile (FULL) part 2
    >>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>sched:
    >>>Mensile (FULL) part 1
    >>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>sched:
    >>>Mensile (FULL) part 2
    >>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>sched:
    >>>Mensile (FULL) part 1
    >>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>sched:
    >>>Mensile (FULL) part 2
    >>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>sched: Mensile (FULL) part 1
    >>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>sched: Mensile (FULL) part 2
    >>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>sched: Mensile (FULL) part 3
    >>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>sched: Mensile (FULL) part 4
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 5 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 4 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 3 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 2 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>sched:
    >>>Settimanale (FULL) part 14
    >>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>sched:
    >>>Settimanale (FULL) part 1
    >>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>sched:
    >>>Settimanale (FULL) part 2
    >>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>sched:
    >>>Settimanale (FULL) part 1
    >>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>sched:
    >>>Settimanale (FULL) part 2
    >>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>sched:
    >>>Settimanale (FULL) part 3
    >>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>sched:
    >>>Settimanale (FULL) part 4
    >>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>sched:
    >>>Settimanale (FULL) part 5
    >>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>sched:
    >>>Settimanale (FULL) part 8
    >>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>sched:
    >>>Settimanale (FULL) part 9
    >>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>sched:
    >>>Settimanale (FULL) part 10
    >>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>sched:
    >>>Settimanale (FULL) part 11
    >>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>sched:
    >>>Settimanale (FULL) part 12
    >>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>sched:
    >>>Settimanale (FULL) part 13
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 1 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 0 WORKLIST
    >>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>21:02:22.519 [11356.10212] <2> bpsched: INITIATING (verbose=0) ...
    >>>
    >>>
    >>>
    >>>"Jeff Redington" ha scritto nel messaggio
    >>>news:uuev71d9jl4qvunqcksjf64397ub9jik0f@4ax.com...
    >>>> Don't look for an error message in the bpsched. Look for the name of
    >>>> the policy and it should explain when you find it why it chose not to
    >>>> run it. If the bpsched thinks there was a good reason not to run the
    >>>> policy it wont list that as an error in the logs.
    >>>>
    >>>> Jeff
    >>>>
    >>>> On Mon, 9 May 2005 12:05:59 +0200, "Massimo Dalla Giustina"
    >>>> wrote:
    >>>>
    >>>>>Hi,
    >>>>>
    >>>>>I have the same problem... I try to find errors on bpsched log file but
    >>>>>I
    >>>>>can't find error about skipped clients
    >>>>>or the reasons for the skipped backup job.
    >>>>>Instead I found many rows like this:
    >>>>>
    >>>>>21:02:22.472 [11128.10976] <8> get_failure_count: cannot list C:\Program
    >>>>>Files\VERITAS\NetBackup\db\failure_history: No error (0)
    >>>>>
    >>>>>The jobs not executed are those with full backup policy.
    >>>>>The schedules for all my policy are:
    >>>>>Name | Type | Retention | Frequency
    >>>>>-------------------------------------------
    >>>>>year | Full | infinity | 54 weeks
    >>>>>month | Full | 6 months | 4 weeks
    >>>>>week | Full | 3 weeks | 1 week
    >>>>>day | Diff. Incr. | 2 weeks | 1 Day
    >>>>>
    >>>>>Differential backup on: Mon, Tue, Wed, Thu
    >>>>>Full backup on: Fri
    >>>>>
    >>>>>Help me please!
    >>>>>
    >>>>>"Jeff Redington" ha scritto nel messaggio
    >>>>>news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    >>>>>> The best place to look to find out why a job failed to run is in the
    >>>>>> bpsched log on the master. You can search the log for the client name
    >>>>>> or the policy name and it should spell out exactly why the job was not
    >>>>>> run.
    >>>>>>
    >>>>>> Jeff
    >>>>>>
    >>>>>>
    >>>>>> On 27 Apr 2005 21:53:58 -0500, "chalse kim" wrote:
    >>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>Hi ~~
    >>>>>>>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>>>>>>
    >>>>>>>I don't know this reason.
    >>>>>>>
    >>>>>>>backup policy, schedule, bakcup windows are all normal condition.
    >>>>>>>
    >>>>>>>But any logs are not logged and cannot see any activities in Activity
    >>>>>>>Mornitor
    >>>>>>>tab.
    >>>>>>>
    >>>>>>>And cannot see any logs because scheduled jobs were not executed.
    >>>>>>>
    >>>>>>>I wonder that scheduled jobs were not executed same this case.
    >>>>>>>
    >>>>>>>Please give me a hands.. if you have solutions or case.
    >>>>>>>
    >>>>>>>Thanks in advance.
    >>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>

    >>

    >



  9. Re: Scheduled bakcup jobs do not execute.

    Ok Jeff,

    Another interesting thing is that the skipped full backups occur randomly.
    In the past weeks, other servers than server1,2,3 have skipped full backup.
    I created a policy for each server so I have actually 11 policies...

    However, I'll try with level 3

    Thanks Jeff, I will post the logs on next monday

    "Jeff Redington" ha scritto nel messaggio
    news:8fo6815t9beu7n4fs34aig44ob4d9d7fuq@4ax.com...
    > After reviewing the logs I am as baffled as you. There is nothing to
    > indicate why it is not running those jobs. Are they all in the same
    > policy? Try creating a new policy for those 3 servers and see if it
    > works. If not, try increasing the verbosity for the bpsched logs to 2
    > or 3 and then send me the bpsched logs after that change.
    >
    > Jeff
    >
    >
    > On Tue, 10 May 2005 16:56:58 +0200, "Massimo Dalla Giustina"
    > wrote:
    >
    >>I can't find what you are indicating to me... In the attachment you can
    >>find
    >>the entire log file.
    >>
    >>I'm using Veritas NetBackup 5.0MP5 for Windows on a Win2003 server.
    >>
    >>"Jeff Redington" ha scritto nel messaggio
    >>news:j1g181ppf5fg0rk3jos1pj261ka8btj994@4ax.com...
    >>> Are those the only references to the servers or policies for those
    >>> backups? I am expecting to see it perform the worklist build around
    >>> the time the job was supposed to start and then it should say
    >>> something like skipping backup due to ... or backup not needed because
    >>> it has already run. There should be a message like that. Follow the
    >>> bpsched back in time to 1-2 hours before the job should have kicked
    >>> off and see if there is anything else you see regarding that client or
    >>> policy.
    >>>
    >>> Jeff
    >>>
    >>> On Tue, 10 May 2005 15:56:48 +0200, "Massimo Dalla Giustina"
    >>> wrote:
    >>>
    >>>>Thanks Jeff,
    >>>>
    >>>>In fact I'm look for the reason not for errors.... but I can't find it.
    >>>>If you look at the logs at the bottom, you can find that server1,
    >>>>server2
    >>>>and server3 are not listed in any retention level worklists.
    >>>>I notice also that the sequence:
    >>>>
    >>>><2> read_schedinfo: No specific include dates entered
    >>>><2> read_schedinfo: No days of week entered
    >>>><2> read_schedinfo: No specific exclude dates entered
    >>>>
    >>>>is not repeated fo server1, server2 and server3.
    >>>>Is this the reason?
    >>>>If so, what can I do?
    >>>>
    >>>>Here the logs:
    >>>>
    >>>>21:02:18.175 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server1
    >>>>server1
    >>>>21:02:18.315 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server2
    >>>>server2
    >>>>21:02:18.409 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server3
    >>>>server3
    >>>>21:02:18.487 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server4
    >>>>server4
    >>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>>entered
    >>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>>entered
    >>>>.....
    >>>>21:02:18.706 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server5
    >>>>server5
    >>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>>entered
    >>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>>entered
    >>>>.....
    >>>>21:02:19.190 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server6
    >>>>server6
    >>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>>entered
    >>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>>entered
    >>>>......
    >>>>21:02:21.331 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server7
    >>>>server7
    >>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>>entered
    >>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>>entered
    >>>>......
    >>>>21:02:21.597 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server8
    >>>>server8
    >>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>>entered
    >>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>>entered
    >>>>.....
    >>>>21:02:21.785 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server9
    >>>>server9
    >>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>>entered
    >>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>>entered
    >>>>......
    >>>>21:02:22.082 [11128.10976] <2> merge_partials: Merging changes for
    >>>>server10
    >>>>server10
    >>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific include dates
    >>>>entered
    >>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific exclude dates
    >>>>entered
    >>>>......
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 24 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 23 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 22 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 21 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 20 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 19 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 18 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 17 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 16 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 15 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 14 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 13 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 12 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 11 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 10 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 9 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 8 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 7 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 6 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>sched:
    >>>>Mensile (FULL) part 15
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>>sched:
    >>>>Mensile (FULL) part 1
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>>sched:
    >>>>Mensile (FULL) part 2
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>>sched:
    >>>>Mensile (FULL) part 1
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>>sched:
    >>>>Mensile (FULL) part 2
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>>sched:
    >>>>Mensile (FULL) part 1
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>>sched:
    >>>>Mensile (FULL) part 2
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>sched: Mensile (FULL) part 1
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>sched: Mensile (FULL) part 2
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>sched: Mensile (FULL) part 3
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>sched: Mensile (FULL) part 4
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 5 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 4 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 3 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 2 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>sched:
    >>>>Settimanale (FULL) part 14
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>>sched:
    >>>>Settimanale (FULL) part 1
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>>sched:
    >>>>Settimanale (FULL) part 2
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>sched:
    >>>>Settimanale (FULL) part 1
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>sched:
    >>>>Settimanale (FULL) part 2
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>sched:
    >>>>Settimanale (FULL) part 3
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>sched:
    >>>>Settimanale (FULL) part 4
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>sched:
    >>>>Settimanale (FULL) part 5
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>sched:
    >>>>Settimanale (FULL) part 8
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>sched:
    >>>>Settimanale (FULL) part 9
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>sched:
    >>>>Settimanale (FULL) part 10
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>sched:
    >>>>Settimanale (FULL) part 11
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>sched:
    >>>>Settimanale (FULL) part 12
    >>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>sched:
    >>>>Settimanale (FULL) part 13
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 1 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 0 WORKLIST
    >>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>21:02:22.519 [11356.10212] <2> bpsched: INITIATING (verbose=0) ...
    >>>>
    >>>>
    >>>>
    >>>>"Jeff Redington" ha scritto nel messaggio
    >>>>news:uuev71d9jl4qvunqcksjf64397ub9jik0f@4ax.com...
    >>>>> Don't look for an error message in the bpsched. Look for the name of
    >>>>> the policy and it should explain when you find it why it chose not to
    >>>>> run it. If the bpsched thinks there was a good reason not to run the
    >>>>> policy it wont list that as an error in the logs.
    >>>>>
    >>>>> Jeff
    >>>>>
    >>>>> On Mon, 9 May 2005 12:05:59 +0200, "Massimo Dalla Giustina"
    >>>>> wrote:
    >>>>>
    >>>>>>Hi,
    >>>>>>
    >>>>>>I have the same problem... I try to find errors on bpsched log file
    >>>>>>but
    >>>>>>I
    >>>>>>can't find error about skipped clients
    >>>>>>or the reasons for the skipped backup job.
    >>>>>>Instead I found many rows like this:
    >>>>>>
    >>>>>>21:02:22.472 [11128.10976] <8> get_failure_count: cannot list
    >>>>>>C:\Program
    >>>>>>Files\VERITAS\NetBackup\db\failure_history: No error (0)
    >>>>>>
    >>>>>>The jobs not executed are those with full backup policy.
    >>>>>>The schedules for all my policy are:
    >>>>>>Name | Type | Retention | Frequency
    >>>>>>-------------------------------------------
    >>>>>>year | Full | infinity | 54 weeks
    >>>>>>month | Full | 6 months | 4 weeks
    >>>>>>week | Full | 3 weeks | 1 week
    >>>>>>day | Diff. Incr. | 2 weeks | 1 Day
    >>>>>>
    >>>>>>Differential backup on: Mon, Tue, Wed, Thu
    >>>>>>Full backup on: Fri
    >>>>>>
    >>>>>>Help me please!
    >>>>>>
    >>>>>>"Jeff Redington" ha scritto nel messaggio
    >>>>>>news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    >>>>>>> The best place to look to find out why a job failed to run is in the
    >>>>>>> bpsched log on the master. You can search the log for the client
    >>>>>>> name
    >>>>>>> or the policy name and it should spell out exactly why the job was
    >>>>>>> not
    >>>>>>> run.
    >>>>>>>
    >>>>>>> Jeff
    >>>>>>>
    >>>>>>>
    >>>>>>> On 27 Apr 2005 21:53:58 -0500, "chalse kim"
    >>>>>>> wrote:
    >>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>Hi ~~
    >>>>>>>>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>>>>>>>
    >>>>>>>>I don't know this reason.
    >>>>>>>>
    >>>>>>>>backup policy, schedule, bakcup windows are all normal condition.
    >>>>>>>>
    >>>>>>>>But any logs are not logged and cannot see any activities in
    >>>>>>>>Activity
    >>>>>>>>Mornitor
    >>>>>>>>tab.
    >>>>>>>>
    >>>>>>>>And cannot see any logs because scheduled jobs were not executed.
    >>>>>>>>
    >>>>>>>>I wonder that scheduled jobs were not executed same this case.
    >>>>>>>>
    >>>>>>>>Please give me a hands.. if you have solutions or case.
    >>>>>>>>
    >>>>>>>>Thanks in advance.
    >>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>

    >>

    >




  10. Re: Scheduled bakcup jobs do not execute.

    Hi Jeff,

    I'm here again!

    On last friday/saturday, others interesting things are happened...
    The policies that skipped backup the past week, this time have executed it.
    An other policy (on server_B) this time has skipped its schedule backup.
    The strange thing is that server_A policy is identical to the server_B
    policy (each started at 6th November),
    but server_A policy has passed the last scheduled backup as you can see on
    the logs....
    The only difference from the server_A policy to the server_B policy is that
    server_A starts at 09.00pm and server_B starts at 11:00pm.

    But by analyzing the logs I found that server_B policy has skipped weekly
    backup because they are not passed seven days from the last weekly backup.
    The reason is that sometimes, for the same policy, the full backup happens
    on the friday or in the saturday night.
    If you don't have any idea to solve this problem, I think that the better
    thing to do is to start all backup policies at friday midnight so they will
    start and complete on saturday.

    Thanks Jeff

    I used log level 3 and I found some
    "Massimo Dalla Giustina" ha scritto nel messaggio
    news:4283859d@ROSASTDMZ05....
    > Ok Jeff,
    >
    > Another interesting thing is that the skipped full backups occur randomly.
    > In the past weeks, other servers than server1,2,3 have skipped full
    > backup.
    > I created a policy for each server so I have actually 11 policies...
    >
    > However, I'll try with level 3
    >
    > Thanks Jeff, I will post the logs on next monday
    >
    > "Jeff Redington" ha scritto nel messaggio
    > news:8fo6815t9beu7n4fs34aig44ob4d9d7fuq@4ax.com...
    >> After reviewing the logs I am as baffled as you. There is nothing to
    >> indicate why it is not running those jobs. Are they all in the same
    >> policy? Try creating a new policy for those 3 servers and see if it
    >> works. If not, try increasing the verbosity for the bpsched logs to 2
    >> or 3 and then send me the bpsched logs after that change.
    >>
    >> Jeff
    >>
    >>
    >> On Tue, 10 May 2005 16:56:58 +0200, "Massimo Dalla Giustina"
    >> wrote:
    >>
    >>>I can't find what you are indicating to me... In the attachment you can
    >>>find
    >>>the entire log file.
    >>>
    >>>I'm using Veritas NetBackup 5.0MP5 for Windows on a Win2003 server.
    >>>
    >>>"Jeff Redington" ha scritto nel messaggio
    >>>news:j1g181ppf5fg0rk3jos1pj261ka8btj994@4ax.com...
    >>>> Are those the only references to the servers or policies for those
    >>>> backups? I am expecting to see it perform the worklist build around
    >>>> the time the job was supposed to start and then it should say
    >>>> something like skipping backup due to ... or backup not needed because
    >>>> it has already run. There should be a message like that. Follow the
    >>>> bpsched back in time to 1-2 hours before the job should have kicked
    >>>> off and see if there is anything else you see regarding that client or
    >>>> policy.
    >>>>
    >>>> Jeff
    >>>>
    >>>> On Tue, 10 May 2005 15:56:48 +0200, "Massimo Dalla Giustina"
    >>>> wrote:
    >>>>
    >>>>>Thanks Jeff,
    >>>>>
    >>>>>In fact I'm look for the reason not for errors.... but I can't find it.
    >>>>>If you look at the logs at the bottom, you can find that server1,
    >>>>>server2
    >>>>>and server3 are not listed in any retention level worklists.
    >>>>>I notice also that the sequence:
    >>>>>
    >>>>><2> read_schedinfo: No specific include dates entered
    >>>>><2> read_schedinfo: No days of week entered
    >>>>><2> read_schedinfo: No specific exclude dates entered
    >>>>>
    >>>>>is not repeated fo server1, server2 and server3.
    >>>>>Is this the reason?
    >>>>>If so, what can I do?
    >>>>>
    >>>>>Here the logs:
    >>>>>
    >>>>>21:02:18.175 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server1
    >>>>>server1
    >>>>>21:02:18.315 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server2
    >>>>>server2
    >>>>>21:02:18.409 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server3
    >>>>>server3
    >>>>>21:02:18.487 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server4
    >>>>>server4
    >>>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>dates
    >>>>>entered
    >>>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>dates
    >>>>>entered
    >>>>>.....
    >>>>>21:02:18.706 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server5
    >>>>>server5
    >>>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>dates
    >>>>>entered
    >>>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>dates
    >>>>>entered
    >>>>>.....
    >>>>>21:02:19.190 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server6
    >>>>>server6
    >>>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>dates
    >>>>>entered
    >>>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>dates
    >>>>>entered
    >>>>>......
    >>>>>21:02:21.331 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server7
    >>>>>server7
    >>>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>dates
    >>>>>entered
    >>>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>dates
    >>>>>entered
    >>>>>......
    >>>>>21:02:21.597 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server8
    >>>>>server8
    >>>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>dates
    >>>>>entered
    >>>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>dates
    >>>>>entered
    >>>>>.....
    >>>>>21:02:21.785 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server9
    >>>>>server9
    >>>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>dates
    >>>>>entered
    >>>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>dates
    >>>>>entered
    >>>>>......
    >>>>>21:02:22.082 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>server10
    >>>>>server10
    >>>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>dates
    >>>>>entered
    >>>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>dates
    >>>>>entered
    >>>>>......
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 24 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 23 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 22 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 21 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 20 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 19 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 18 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 17 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 16 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 15 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 14 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 13 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 12 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 11 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 10 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 9 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 8 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 7 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 6 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>sched:
    >>>>>Mensile (FULL) part 15
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>>>sched:
    >>>>>Mensile (FULL) part 1
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>>>sched:
    >>>>>Mensile (FULL) part 2
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>>>sched:
    >>>>>Mensile (FULL) part 1
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>>>sched:
    >>>>>Mensile (FULL) part 2
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>>>sched:
    >>>>>Mensile (FULL) part 1
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>>>sched:
    >>>>>Mensile (FULL) part 2
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>sched: Mensile (FULL) part 1
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>sched: Mensile (FULL) part 2
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>sched: Mensile (FULL) part 3
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>sched: Mensile (FULL) part 4
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 5 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 4 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 3 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 2 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>sched:
    >>>>>Settimanale (FULL) part 14
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>>>sched:
    >>>>>Settimanale (FULL) part 1
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>>>sched:
    >>>>>Settimanale (FULL) part 2
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>sched:
    >>>>>Settimanale (FULL) part 1
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>sched:
    >>>>>Settimanale (FULL) part 2
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>sched:
    >>>>>Settimanale (FULL) part 3
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>sched:
    >>>>>Settimanale (FULL) part 4
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>sched:
    >>>>>Settimanale (FULL) part 5
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>sched:
    >>>>>Settimanale (FULL) part 8
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>sched:
    >>>>>Settimanale (FULL) part 9
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>sched:
    >>>>>Settimanale (FULL) part 10
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>sched:
    >>>>>Settimanale (FULL) part 11
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>sched:
    >>>>>Settimanale (FULL) part 12
    >>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>sched:
    >>>>>Settimanale (FULL) part 13
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 1 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 0 WORKLIST
    >>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>21:02:22.519 [11356.10212] <2> bpsched: INITIATING (verbose=0) ...
    >>>>>
    >>>>>
    >>>>>
    >>>>>"Jeff Redington" ha scritto nel messaggio
    >>>>>news:uuev71d9jl4qvunqcksjf64397ub9jik0f@4ax.com...
    >>>>>> Don't look for an error message in the bpsched. Look for the name of
    >>>>>> the policy and it should explain when you find it why it chose not to
    >>>>>> run it. If the bpsched thinks there was a good reason not to run the
    >>>>>> policy it wont list that as an error in the logs.
    >>>>>>
    >>>>>> Jeff
    >>>>>>
    >>>>>> On Mon, 9 May 2005 12:05:59 +0200, "Massimo Dalla Giustina"
    >>>>>> wrote:
    >>>>>>
    >>>>>>>Hi,
    >>>>>>>
    >>>>>>>I have the same problem... I try to find errors on bpsched log file
    >>>>>>>but
    >>>>>>>I
    >>>>>>>can't find error about skipped clients
    >>>>>>>or the reasons for the skipped backup job.
    >>>>>>>Instead I found many rows like this:
    >>>>>>>
    >>>>>>>21:02:22.472 [11128.10976] <8> get_failure_count: cannot list
    >>>>>>>C:\Program
    >>>>>>>Files\VERITAS\NetBackup\db\failure_history: No error (0)
    >>>>>>>
    >>>>>>>The jobs not executed are those with full backup policy.
    >>>>>>>The schedules for all my policy are:
    >>>>>>>Name | Type | Retention | Frequency
    >>>>>>>-------------------------------------------
    >>>>>>>year | Full | infinity | 54 weeks
    >>>>>>>month | Full | 6 months | 4 weeks
    >>>>>>>week | Full | 3 weeks | 1 week
    >>>>>>>day | Diff. Incr. | 2 weeks | 1 Day
    >>>>>>>
    >>>>>>>Differential backup on: Mon, Tue, Wed, Thu
    >>>>>>>Full backup on: Fri
    >>>>>>>
    >>>>>>>Help me please!
    >>>>>>>
    >>>>>>>"Jeff Redington" ha scritto nel messaggio
    >>>>>>>news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    >>>>>>>> The best place to look to find out why a job failed to run is in
    >>>>>>>> the
    >>>>>>>> bpsched log on the master. You can search the log for the client
    >>>>>>>> name
    >>>>>>>> or the policy name and it should spell out exactly why the job was
    >>>>>>>> not
    >>>>>>>> run.
    >>>>>>>>
    >>>>>>>> Jeff
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> On 27 Apr 2005 21:53:58 -0500, "chalse kim"
    >>>>>>>> wrote:
    >>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>Hi ~~
    >>>>>>>>>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>>>>>>>>
    >>>>>>>>>I don't know this reason.
    >>>>>>>>>
    >>>>>>>>>backup policy, schedule, bakcup windows are all normal condition.
    >>>>>>>>>
    >>>>>>>>>But any logs are not logged and cannot see any activities in
    >>>>>>>>>Activity
    >>>>>>>>>Mornitor
    >>>>>>>>>tab.
    >>>>>>>>>
    >>>>>>>>>And cannot see any logs because scheduled jobs were not executed.
    >>>>>>>>>
    >>>>>>>>>I wonder that scheduled jobs were not executed same this case.
    >>>>>>>>>
    >>>>>>>>>Please give me a hands.. if you have solutions or case.
    >>>>>>>>>
    >>>>>>>>>Thanks in advance.
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>

    >>

    >
    >






  11. Re: Scheduled bakcup jobs do not execute.

    Based on what you describe set the frequency of the jobs to 4 or 5
    days. By only having your window open on the weekend and the frequency
    set to 4 or 5 (I would recommend 4), it will definitely need to run on
    the following weekend no matter when it ran the previous weekend.

    Jeff

    On Mon, 16 May 2005 11:43:34 +0200, "Massimo Dalla Giustina"
    wrote:

    >Hi Jeff,
    >
    >I'm here again!
    >
    >On last friday/saturday, others interesting things are happened...
    >The policies that skipped backup the past week, this time have executed it.
    >An other policy (on server_B) this time has skipped its schedule backup.
    >The strange thing is that server_A policy is identical to the server_B
    >policy (each started at 6th November),
    >but server_A policy has passed the last scheduled backup as you can see on
    >the logs....
    >The only difference from the server_A policy to the server_B policy is that
    >server_A starts at 09.00pm and server_B starts at 11:00pm.
    >
    >But by analyzing the logs I found that server_B policy has skipped weekly
    >backup because they are not passed seven days from the last weekly backup.
    >The reason is that sometimes, for the same policy, the full backup happens
    >on the friday or in the saturday night.
    >If you don't have any idea to solve this problem, I think that the better
    >thing to do is to start all backup policies at friday midnight so they will
    >start and complete on saturday.
    >
    >Thanks Jeff
    >
    >I used log level 3 and I found some
    >"Massimo Dalla Giustina" ha scritto nel messaggio
    >news:4283859d@ROSASTDMZ05....
    >> Ok Jeff,
    >>
    >> Another interesting thing is that the skipped full backups occur randomly.
    >> In the past weeks, other servers than server1,2,3 have skipped full
    >> backup.
    >> I created a policy for each server so I have actually 11 policies...
    >>
    >> However, I'll try with level 3
    >>
    >> Thanks Jeff, I will post the logs on next monday
    >>
    >> "Jeff Redington" ha scritto nel messaggio
    >> news:8fo6815t9beu7n4fs34aig44ob4d9d7fuq@4ax.com...
    >>> After reviewing the logs I am as baffled as you. There is nothing to
    >>> indicate why it is not running those jobs. Are they all in the same
    >>> policy? Try creating a new policy for those 3 servers and see if it
    >>> works. If not, try increasing the verbosity for the bpsched logs to 2
    >>> or 3 and then send me the bpsched logs after that change.
    >>>
    >>> Jeff
    >>>
    >>>
    >>> On Tue, 10 May 2005 16:56:58 +0200, "Massimo Dalla Giustina"
    >>> wrote:
    >>>
    >>>>I can't find what you are indicating to me... In the attachment you can
    >>>>find
    >>>>the entire log file.
    >>>>
    >>>>I'm using Veritas NetBackup 5.0MP5 for Windows on a Win2003 server.
    >>>>
    >>>>"Jeff Redington" ha scritto nel messaggio
    >>>>news:j1g181ppf5fg0rk3jos1pj261ka8btj994@4ax.com...
    >>>>> Are those the only references to the servers or policies for those
    >>>>> backups? I am expecting to see it perform the worklist build around
    >>>>> the time the job was supposed to start and then it should say
    >>>>> something like skipping backup due to ... or backup not needed because
    >>>>> it has already run. There should be a message like that. Follow the
    >>>>> bpsched back in time to 1-2 hours before the job should have kicked
    >>>>> off and see if there is anything else you see regarding that client or
    >>>>> policy.
    >>>>>
    >>>>> Jeff
    >>>>>
    >>>>> On Tue, 10 May 2005 15:56:48 +0200, "Massimo Dalla Giustina"
    >>>>> wrote:
    >>>>>
    >>>>>>Thanks Jeff,
    >>>>>>
    >>>>>>In fact I'm look for the reason not for errors.... but I can't find it.
    >>>>>>If you look at the logs at the bottom, you can find that server1,
    >>>>>>server2
    >>>>>>and server3 are not listed in any retention level worklists.
    >>>>>>I notice also that the sequence:
    >>>>>>
    >>>>>><2> read_schedinfo: No specific include dates entered
    >>>>>><2> read_schedinfo: No days of week entered
    >>>>>><2> read_schedinfo: No specific exclude dates entered
    >>>>>>
    >>>>>>is not repeated fo server1, server2 and server3.
    >>>>>>Is this the reason?
    >>>>>>If so, what can I do?
    >>>>>>
    >>>>>>Here the logs:
    >>>>>>
    >>>>>>21:02:18.175 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server1
    >>>>>>server1
    >>>>>>21:02:18.315 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server2
    >>>>>>server2
    >>>>>>21:02:18.409 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server3
    >>>>>>server3
    >>>>>>21:02:18.487 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server4
    >>>>>>server4
    >>>>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>dates
    >>>>>>entered
    >>>>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>dates
    >>>>>>entered
    >>>>>>.....
    >>>>>>21:02:18.706 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server5
    >>>>>>server5
    >>>>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>dates
    >>>>>>entered
    >>>>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>dates
    >>>>>>entered
    >>>>>>.....
    >>>>>>21:02:19.190 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server6
    >>>>>>server6
    >>>>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>dates
    >>>>>>entered
    >>>>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>dates
    >>>>>>entered
    >>>>>>......
    >>>>>>21:02:21.331 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server7
    >>>>>>server7
    >>>>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>dates
    >>>>>>entered
    >>>>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>dates
    >>>>>>entered
    >>>>>>......
    >>>>>>21:02:21.597 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server8
    >>>>>>server8
    >>>>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>dates
    >>>>>>entered
    >>>>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>dates
    >>>>>>entered
    >>>>>>.....
    >>>>>>21:02:21.785 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server9
    >>>>>>server9
    >>>>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>dates
    >>>>>>entered
    >>>>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>dates
    >>>>>>entered
    >>>>>>......
    >>>>>>21:02:22.082 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>server10
    >>>>>>server10
    >>>>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>dates
    >>>>>>entered
    >>>>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No days of week entered
    >>>>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>dates
    >>>>>>entered
    >>>>>>......
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 24 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 23 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 22 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 21 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 20 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 19 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 18 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 17 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 16 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 15 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 14 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 13 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 12 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 11 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 10 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 9 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 8 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 7 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 6 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>sched:
    >>>>>>Mensile (FULL) part 15
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>>>>sched:
    >>>>>>Mensile (FULL) part 1
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>>>>sched:
    >>>>>>Mensile (FULL) part 2
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>>>>sched:
    >>>>>>Mensile (FULL) part 1
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>>>>sched:
    >>>>>>Mensile (FULL) part 2
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>>>>sched:
    >>>>>>Mensile (FULL) part 1
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>>>>sched:
    >>>>>>Mensile (FULL) part 2
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>>sched: Mensile (FULL) part 1
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>>sched: Mensile (FULL) part 2
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>>sched: Mensile (FULL) part 3
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>>sched: Mensile (FULL) part 4
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 5 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 4 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 3 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 2 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 14
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 1
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 2
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 1
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 2
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 3
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 4
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 5
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 8
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 9
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 10
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 11
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 12
    >>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>sched:
    >>>>>>Settimanale (FULL) part 13
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 1 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 0 WORKLIST
    >>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>21:02:22.519 [11356.10212] <2> bpsched: INITIATING (verbose=0) ...
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>"Jeff Redington" ha scritto nel messaggio
    >>>>>>news:uuev71d9jl4qvunqcksjf64397ub9jik0f@4ax.com...
    >>>>>>> Don't look for an error message in the bpsched. Look for the name of
    >>>>>>> the policy and it should explain when you find it why it chose not to
    >>>>>>> run it. If the bpsched thinks there was a good reason not to run the
    >>>>>>> policy it wont list that as an error in the logs.
    >>>>>>>
    >>>>>>> Jeff
    >>>>>>>
    >>>>>>> On Mon, 9 May 2005 12:05:59 +0200, "Massimo Dalla Giustina"
    >>>>>>> wrote:
    >>>>>>>
    >>>>>>>>Hi,
    >>>>>>>>
    >>>>>>>>I have the same problem... I try to find errors on bpsched log file
    >>>>>>>>but
    >>>>>>>>I
    >>>>>>>>can't find error about skipped clients
    >>>>>>>>or the reasons for the skipped backup job.
    >>>>>>>>Instead I found many rows like this:
    >>>>>>>>
    >>>>>>>>21:02:22.472 [11128.10976] <8> get_failure_count: cannot list
    >>>>>>>>C:\Program
    >>>>>>>>Files\VERITAS\NetBackup\db\failure_history: No error (0)
    >>>>>>>>
    >>>>>>>>The jobs not executed are those with full backup policy.
    >>>>>>>>The schedules for all my policy are:
    >>>>>>>>Name | Type | Retention | Frequency
    >>>>>>>>-------------------------------------------
    >>>>>>>>year | Full | infinity | 54 weeks
    >>>>>>>>month | Full | 6 months | 4 weeks
    >>>>>>>>week | Full | 3 weeks | 1 week
    >>>>>>>>day | Diff. Incr. | 2 weeks | 1 Day
    >>>>>>>>
    >>>>>>>>Differential backup on: Mon, Tue, Wed, Thu
    >>>>>>>>Full backup on: Fri
    >>>>>>>>
    >>>>>>>>Help me please!
    >>>>>>>>
    >>>>>>>>"Jeff Redington" ha scritto nel messaggio
    >>>>>>>>news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    >>>>>>>>> The best place to look to find out why a job failed to run is in
    >>>>>>>>> the
    >>>>>>>>> bpsched log on the master. You can search the log for the client
    >>>>>>>>> name
    >>>>>>>>> or the policy name and it should spell out exactly why the job was
    >>>>>>>>> not
    >>>>>>>>> run.
    >>>>>>>>>
    >>>>>>>>> Jeff
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> On 27 Apr 2005 21:53:58 -0500, "chalse kim"
    >>>>>>>>> wrote:
    >>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>Hi ~~
    >>>>>>>>>>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>>>>>>>>>
    >>>>>>>>>>I don't know this reason.
    >>>>>>>>>>
    >>>>>>>>>>backup policy, schedule, bakcup windows are all normal condition.
    >>>>>>>>>>
    >>>>>>>>>>But any logs are not logged and cannot see any activities in
    >>>>>>>>>>Activity
    >>>>>>>>>>Mornitor
    >>>>>>>>>>tab.
    >>>>>>>>>>
    >>>>>>>>>>And cannot see any logs because scheduled jobs were not executed.
    >>>>>>>>>>
    >>>>>>>>>>I wonder that scheduled jobs were not executed same this case.
    >>>>>>>>>>
    >>>>>>>>>>Please give me a hands.. if you have solutions or case.
    >>>>>>>>>>
    >>>>>>>>>>Thanks in advance.
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>

    >>
    >>

    >



  12. Re: Scheduled bakcup jobs do not execute.

    Ok Jeff,

    I solved the problem.... Thank you very much.

    Bye


    "Jeff Redington" ha scritto nel messaggio
    news:irfm81pl877iql23lfhog02m8ajkkm5bvb@4ax.com...
    > Based on what you describe set the frequency of the jobs to 4 or 5
    > days. By only having your window open on the weekend and the frequency
    > set to 4 or 5 (I would recommend 4), it will definitely need to run on
    > the following weekend no matter when it ran the previous weekend.
    >
    > Jeff
    >
    > On Mon, 16 May 2005 11:43:34 +0200, "Massimo Dalla Giustina"
    > wrote:
    >
    >>Hi Jeff,
    >>
    >>I'm here again!
    >>
    >>On last friday/saturday, others interesting things are happened...
    >>The policies that skipped backup the past week, this time have executed
    >>it.
    >>An other policy (on server_B) this time has skipped its schedule backup.
    >>The strange thing is that server_A policy is identical to the server_B
    >>policy (each started at 6th November),
    >>but server_A policy has passed the last scheduled backup as you can see on
    >>the logs....
    >>The only difference from the server_A policy to the server_B policy is
    >>that
    >>server_A starts at 09.00pm and server_B starts at 11:00pm.
    >>
    >>But by analyzing the logs I found that server_B policy has skipped weekly
    >>backup because they are not passed seven days from the last weekly backup.
    >>The reason is that sometimes, for the same policy, the full backup happens
    >>on the friday or in the saturday night.
    >>If you don't have any idea to solve this problem, I think that the better
    >>thing to do is to start all backup policies at friday midnight so they
    >>will
    >>start and complete on saturday.
    >>
    >>Thanks Jeff
    >>
    >>I used log level 3 and I found some
    >>"Massimo Dalla Giustina" ha scritto nel messaggio
    >>news:4283859d@ROSASTDMZ05....
    >>> Ok Jeff,
    >>>
    >>> Another interesting thing is that the skipped full backups occur
    >>> randomly.
    >>> In the past weeks, other servers than server1,2,3 have skipped full
    >>> backup.
    >>> I created a policy for each server so I have actually 11 policies...
    >>>
    >>> However, I'll try with level 3
    >>>
    >>> Thanks Jeff, I will post the logs on next monday
    >>>
    >>> "Jeff Redington" ha scritto nel messaggio
    >>> news:8fo6815t9beu7n4fs34aig44ob4d9d7fuq@4ax.com...
    >>>> After reviewing the logs I am as baffled as you. There is nothing to
    >>>> indicate why it is not running those jobs. Are they all in the same
    >>>> policy? Try creating a new policy for those 3 servers and see if it
    >>>> works. If not, try increasing the verbosity for the bpsched logs to 2
    >>>> or 3 and then send me the bpsched logs after that change.
    >>>>
    >>>> Jeff
    >>>>
    >>>>
    >>>> On Tue, 10 May 2005 16:56:58 +0200, "Massimo Dalla Giustina"
    >>>> wrote:
    >>>>
    >>>>>I can't find what you are indicating to me... In the attachment you can
    >>>>>find
    >>>>>the entire log file.
    >>>>>
    >>>>>I'm using Veritas NetBackup 5.0MP5 for Windows on a Win2003 server.
    >>>>>
    >>>>>"Jeff Redington" ha scritto nel messaggio
    >>>>>news:j1g181ppf5fg0rk3jos1pj261ka8btj994@4ax.com...
    >>>>>> Are those the only references to the servers or policies for those
    >>>>>> backups? I am expecting to see it perform the worklist build around
    >>>>>> the time the job was supposed to start and then it should say
    >>>>>> something like skipping backup due to ... or backup not needed
    >>>>>> because
    >>>>>> it has already run. There should be a message like that. Follow the
    >>>>>> bpsched back in time to 1-2 hours before the job should have kicked
    >>>>>> off and see if there is anything else you see regarding that client
    >>>>>> or
    >>>>>> policy.
    >>>>>>
    >>>>>> Jeff
    >>>>>>
    >>>>>> On Tue, 10 May 2005 15:56:48 +0200, "Massimo Dalla Giustina"
    >>>>>> wrote:
    >>>>>>
    >>>>>>>Thanks Jeff,
    >>>>>>>
    >>>>>>>In fact I'm look for the reason not for errors.... but I can't find
    >>>>>>>it.
    >>>>>>>If you look at the logs at the bottom, you can find that server1,
    >>>>>>>server2
    >>>>>>>and server3 are not listed in any retention level worklists.
    >>>>>>>I notice also that the sequence:
    >>>>>>>
    >>>>>>><2> read_schedinfo: No specific include dates entered
    >>>>>>><2> read_schedinfo: No days of week entered
    >>>>>>><2> read_schedinfo: No specific exclude dates entered
    >>>>>>>
    >>>>>>>is not repeated fo server1, server2 and server3.
    >>>>>>>Is this the reason?
    >>>>>>>If so, what can I do?
    >>>>>>>
    >>>>>>>Here the logs:
    >>>>>>>
    >>>>>>>21:02:18.175 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server1
    >>>>>>>server1
    >>>>>>>21:02:18.315 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server2
    >>>>>>>server2
    >>>>>>>21:02:18.409 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server3
    >>>>>>>server3
    >>>>>>>21:02:18.487 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server4
    >>>>>>>server4
    >>>>>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No days of week
    >>>>>>>entered
    >>>>>>>21:02:18.565 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>.....
    >>>>>>>21:02:18.706 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server5
    >>>>>>>server5
    >>>>>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No days of week
    >>>>>>>entered
    >>>>>>>21:02:18.847 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>.....
    >>>>>>>21:02:19.190 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server6
    >>>>>>>server6
    >>>>>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No days of week
    >>>>>>>entered
    >>>>>>>21:02:20.128 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>......
    >>>>>>>21:02:21.331 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server7
    >>>>>>>server7
    >>>>>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No days of week
    >>>>>>>entered
    >>>>>>>21:02:21.472 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>......
    >>>>>>>21:02:21.597 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server8
    >>>>>>>server8
    >>>>>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No days of week
    >>>>>>>entered
    >>>>>>>21:02:21.675 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>.....
    >>>>>>>21:02:21.785 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server9
    >>>>>>>server9
    >>>>>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No days of week
    >>>>>>>entered
    >>>>>>>21:02:21.941 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>......
    >>>>>>>21:02:22.082 [11128.10976] <2> merge_partials: Merging changes for
    >>>>>>>server10
    >>>>>>>server10
    >>>>>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific include
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No days of week
    >>>>>>>entered
    >>>>>>>21:02:22.300 [11128.10976] <2> read_schedinfo: No specific exclude
    >>>>>>>dates
    >>>>>>>entered
    >>>>>>>......
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 24 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 23 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 22 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 21 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 20 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 19 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 18 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 17 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 16 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 15 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 14 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 13 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 12 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 11 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 10 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 9 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 8 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 7 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 6 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>>sched:
    >>>>>>>Mensile (FULL) part 15
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>>>>>sched:
    >>>>>>>Mensile (FULL) part 1
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server7 class: server7
    >>>>>>>sched:
    >>>>>>>Mensile (FULL) part 2
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>>>>>sched:
    >>>>>>>Mensile (FULL) part 1
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server8 class: server8
    >>>>>>>sched:
    >>>>>>>Mensile (FULL) part 2
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>>>>>sched:
    >>>>>>>Mensile (FULL) part 1
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server9 class: server9
    >>>>>>>sched:
    >>>>>>>Mensile (FULL) part 2
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>>>sched: Mensile (FULL) part 1
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>>>sched: Mensile (FULL) part 2
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>>>sched: Mensile (FULL) part 3
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server10 class: server10
    >>>>>>>sched: Mensile (FULL) part 4
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 5 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 4 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 3 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 2 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 14
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 1
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server4 class: server4
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 2
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 1
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 2
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 3
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 4
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server5 class: server5
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 5
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 8
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 9
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 10
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 11
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 12
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: client: server6 class: server6
    >>>>>>>sched:
    >>>>>>>Settimanale (FULL) part 13
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 1 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: RETENTION LEVEL 0 WORKLIST
    >>>>>>>21:02:22.488 [11128.10976] <2> ?: --------------------------
    >>>>>>>21:02:22.519 [11356.10212] <2> bpsched: INITIATING (verbose=0) ...
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>"Jeff Redington" ha scritto nel messaggio
    >>>>>>>news:uuev71d9jl4qvunqcksjf64397ub9jik0f@4ax.com...
    >>>>>>>> Don't look for an error message in the bpsched. Look for the name
    >>>>>>>> of
    >>>>>>>> the policy and it should explain when you find it why it chose not
    >>>>>>>> to
    >>>>>>>> run it. If the bpsched thinks there was a good reason not to run
    >>>>>>>> the
    >>>>>>>> policy it wont list that as an error in the logs.
    >>>>>>>>
    >>>>>>>> Jeff
    >>>>>>>>
    >>>>>>>> On Mon, 9 May 2005 12:05:59 +0200, "Massimo Dalla Giustina"
    >>>>>>>> wrote:
    >>>>>>>>
    >>>>>>>>>Hi,
    >>>>>>>>>
    >>>>>>>>>I have the same problem... I try to find errors on bpsched log file
    >>>>>>>>>but
    >>>>>>>>>I
    >>>>>>>>>can't find error about skipped clients
    >>>>>>>>>or the reasons for the skipped backup job.
    >>>>>>>>>Instead I found many rows like this:
    >>>>>>>>>
    >>>>>>>>>21:02:22.472 [11128.10976] <8> get_failure_count: cannot list
    >>>>>>>>>C:\Program
    >>>>>>>>>Files\VERITAS\NetBackup\db\failure_history: No error (0)
    >>>>>>>>>
    >>>>>>>>>The jobs not executed are those with full backup policy.
    >>>>>>>>>The schedules for all my policy are:
    >>>>>>>>>Name | Type | Retention | Frequency
    >>>>>>>>>-------------------------------------------
    >>>>>>>>>year | Full | infinity | 54 weeks
    >>>>>>>>>month | Full | 6 months | 4 weeks
    >>>>>>>>>week | Full | 3 weeks | 1 week
    >>>>>>>>>day | Diff. Incr. | 2 weeks | 1 Day
    >>>>>>>>>
    >>>>>>>>>Differential backup on: Mon, Tue, Wed, Thu
    >>>>>>>>>Full backup on: Fri
    >>>>>>>>>
    >>>>>>>>>Help me please!
    >>>>>>>>>
    >>>>>>>>>"Jeff Redington" ha scritto nel messaggio
    >>>>>>>>>news:6kp171tnavvlrkp6mhl9fe9e8094r7vji3@4ax.com...
    >>>>>>>>>> The best place to look to find out why a job failed to run is in
    >>>>>>>>>> the
    >>>>>>>>>> bpsched log on the master. You can search the log for the client
    >>>>>>>>>> name
    >>>>>>>>>> or the policy name and it should spell out exactly why the job
    >>>>>>>>>> was
    >>>>>>>>>> not
    >>>>>>>>>> run.
    >>>>>>>>>>
    >>>>>>>>>> Jeff
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>> On 27 Apr 2005 21:53:58 -0500, "chalse kim"
    >>>>>>>>>> wrote:
    >>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>Hi ~~
    >>>>>>>>>>>Sometimes, netbakcup's scheduled backup jobs do not execute.
    >>>>>>>>>>>
    >>>>>>>>>>>I don't know this reason.
    >>>>>>>>>>>
    >>>>>>>>>>>backup policy, schedule, bakcup windows are all normal condition.
    >>>>>>>>>>>
    >>>>>>>>>>>But any logs are not logged and cannot see any activities in
    >>>>>>>>>>>Activity
    >>>>>>>>>>>Mornitor
    >>>>>>>>>>>tab.
    >>>>>>>>>>>
    >>>>>>>>>>>And cannot see any logs because scheduled jobs were not executed.
    >>>>>>>>>>>
    >>>>>>>>>>>I wonder that scheduled jobs were not executed same this case.
    >>>>>>>>>>>
    >>>>>>>>>>>Please give me a hands.. if you have solutions or case.
    >>>>>>>>>>>
    >>>>>>>>>>>Thanks in advance.
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>
    >>>

    >>

    >




+ Reply to Thread