Forum Discussion

katek's avatar
katek
Level 2
9 years ago

Expired images manually, but job does not work

Hi there,

 

I expired some images in Catalog because of high watermark (error 127).

However, after deleting images, the backup job does not work.

I can backup manually (by right-click the policy), but scheduled jobs are not working.

I have enough disk space, and other jobs doing well.

 

Please advice,

 

Kate

7.6
Windows Server (2003
  • Marianne's avatar
    Marianne
    9 years ago
    I have seen since NBU 5.x days how one failure broke hourly backups with default 2 tries per 12 hours.
    Sometimes a manual backup will kickstart the hourly backups again, but this does not always work.
    Global setting of 1/2 tries per 1 hour will fix the problem, but not always desirable as this is a Global setting and cannot be customised per client or per policy.
  • Marianne's avatar
    Marianne
    Level 6
    9 years ago

    Are Policy schedules configured as Calendar or Frequency?
    How often are jobs supposed to run?
    When last did a manual job succeed? 

    Please bear in mind that manual jobs will affect Automatic schedules.

    The Global settings of "x tries per xx hours" will also affect retries of jobs after a failure.

     

    • katek's avatar
      katek
      Level 2
      9 years ago
      Marianne,

      Thank you for quick reply.

      The job is supporsed to run once per hour, configured as Frequency.
      It stopped just before I expired images.

      I waited several hours (or changed time setting of server), but nothing happens.
      I'm gonna check global settings, and maybe wait for another hour.

      Arigato!

      Kate
      • Marianne's avatar
        Marianne
        Level 6
        9 years ago
        I have seen since NBU 5.x days how one failure broke hourly backups with default 2 tries per 12 hours.
        Sometimes a manual backup will kickstart the hourly backups again, but this does not always work.
        Global setting of 1/2 tries per 1 hour will fix the problem, but not always desirable as this is a Global setting and cannot be customised per client or per policy.