status 237 after adding new schedule

[nbritton]

I have a policy for an exchange dag, where i orginally had the full.  upon complettion of the backup, i added a new schedule for the daily differential backups.  When i go to run the schedule i get a 237 error code.  But all of the settings look right and its active.  

I have tried coping it to a new policy and then it works, but i would like to see how to resolve the problem without cretinga  new policy and maintiaing our naming standards.

If i delete the policy and recreate it with the same name it will give me the 237 status code again as well

Thoughts??

[Marianne]

Please show us policy with problematic schedule? bppllist 'policy-name' -U

[nbritton]

Here is the results from the bppllist command:

Policy Name:       oma00ee01_30_pl

  Policy Type:         MS-Exchange-Server
  Active:              yes
  Effective date:      02/18/2014 11:46:59
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           oma00linux6163dpd_su
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Exchange Source active db:               yes
  Exchange DAG Preferred Server: (none defined)
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
  ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
  Enable Metadata Indexing:  no
  Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows2008   dag01

  Include:  NEW_STREAM
            Microsoft Exchange Database Availability Groups:\

  Schedule:              Full
    Type:                Automatic Backup
    Frequency:           every 7 days
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     2 (30 days)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:   0
    Daily Windows:
          Saturday   01:00:00  -->  Saturday   05:00:00

  Schedule:              Diff
    Type:                Differential Incremental Backup
    Frequency:           every 1 day
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     2 (30 days)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:   0
    Daily Windows:
          Sunday     01:00:00  -->  Sunday     06:00:00
          Monday     01:00:00  -->  Monday     06:00:00
          Tuesday    01:00:00  -->  Tuesday    06:00:00
          Wednesday  01:00:00  -->  Wednesday  06:00:00
          Thursday   01:00:00  -->  Thursday   06:00:00
          Friday     01:00:00  -->  Friday     06:00:00

[Marianne]

Apologies for only responding now. Your post got blocked by the spam filter. How exactly is this policy/schedule kicked off? We normally only see this error when a policy is kicked off from cmd or a 3rd-party scheduler. I have never seen this error when kicked off by NBU internal scheduler.

[nbritton]

I get the error each time I try to run the schedule manually from the admin console.

[Marianne]

Highly unusual....

Is this still happening? Bearing in mind that the nbpem process has been refreshed multiple times in the meantime... 

If so, I would like to see bprd log on the master (this is where manual backup requests is logged) as well as nbpem log for the last couple of minutes (enough time to cover the manual backup attempt)
vxlogview -o 116 -t 00:10:00

Above command will display nbpem log for the last 10 minutes.
bprd log folder does not exist by default - it must be created under netbackup\logs followed by restart of NBU Request Service.

[Ron_Cohn]

For how I read this, your schedule name is "Diff".  The name you are using maybe interpreted as a NBU Keyword and causing you heartburn.  Try using something like "EXCH_Daily" and see if you get the same results...
 

[nbritton · Accepted solution]

I ended up fixing this by restarting the processes on the master.  Everything seems to work as expected.

Thank you all for your assistance.