IBM Support

Error: No schedules of the correct type exist in this policy

Question & Answer


Question

Why does my Veritas NetBackup™ manual backup keep getting skipped with the following error: 'No schedules of the correct type exist in this policy'?

Answer

Users or administrators may want to manually execute a backup that is typically automatically scheduled. When users manually execute the backup, the logs show that 'no schedules of the correct type exist in this policy'.

If after reviewing your 'Problems' log, you find that a scheduled backup failed to run because 'no schedules of the correct type exist in the policy', you should review your calendar settings. This can be done by running the NetBackup command bpclsched. This command may be installed on the client in /usr/openv/netbackup/bin/admincmd but will surely exist on the Master or Media server. It can be run as shown below:

    ./bpclsched MyPolicay-M myMasterServer -L
    Schedule:          Default-Application-Backup
      Type:            UBAK DataStore (2)
      Frequency:       7 day(s) (604800 seconds)
      Retention Level: 1 (2 weeks)
      u-wind/o/d:      0 0
      Incr Type:       DELTA (0)
      Incr Depends:    (none defined)
      Max Frag Size:   0 MB
      PFI Recovery:    0
      Maximum MPX:     1
      Number Copies:   1
      Fail on Error:   0
      Residence:       (specific storage unit not required)
      Volume Pool:     (same as policy volume pool)
      Daily Windows:
       Day         Open       Close       W-Open     W-Close
       Sunday      000:00:00  024:00:00   000:00:00  024:00:00
       Monday      000:00:00  024:00:00   024:00:00  048:00:00
       Tuesday     000:00:00  024:00:00   048:00:00  072:00:00
       Wednesday   000:00:00  024:00:00   072:00:00  096:00:00
       Thursday    000:00:00  024:00:00   096:00:00  120:00:00
       Friday      000:00:00  024:00:00   120:00:00  144:00:00
       Saturday    000:00:00  024:00:00   144:00:00  168:00:00

Each automated backup schedule has an associated backup window which is a time range. If you manually execute an automated backup during a time that is not within the backup window, the backup will not start and you will see this error message in the Problems log.

You can also diagnose this problem from the client by reviewing the appropriate log in /usr/openv/netbackup/logs/user_ops/dbext/logs/. You will see the following text:
    Backup started Fri Sep 21 12:24:32 2007

    12:24:32 Initiating backup
    12:24:33 INF - Server status = 240
    12:24:33 INF - Server status = 240
    12:24:33 INF - Backup by nz on client spiral using policy SpiralTest: no schedules of the correct type exist in this policy.

[{"Product":{"code":"SSULQD","label":"IBM PureData System"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":null,"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Historical Number

NZ364135

Document Information

Modified date:
17 October 2019

UID

swg21574853