cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

Scheduler found no backups due to run(200) for VMWare backups

npais
Level 2
Partner

Apologies if this has been asked (and answered) before, but I couldn't find a solution. We have a windows 2008 master server running Netbackup 7.6.0.4 and vmware backups with vCloud director integration enabled. The issue we are facing is that backups fail with status 200 when the policy kicks off as per the frequency based schedule daily at 18:30 hrs, but is successful when it automatically retries again in some time.

The backup host is the media server (5230 appliance) with SAN transport mode

I have checked the credentials being used for the vCenter and they are the same. Netbackup is able to connect just fine. 

Below is the output from bppllist <policyname> -U

Policy Name:       MA****4-1003656-64-vCloud-BaaS-12-S***n

  Policy Type:         VMware
  Active:              yes
  Effective date:      28/10/2014 10:53:07
  File Restore Raw:    yes
  Application Consistent:    yes
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           stu_disk_cmsma-bk03
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             FrontOfficeClientId=64
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      yes
  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:  yes
  HW/OS/Client:  VMware        Virtual_Machi cmsma-bk03

  Include:  vmware:/?filter=vCDOrg Equal 'MA****4' AND vCDOrgvDC Equal 'MA****4-01' 
    AND vCDvApp Equal 'vAppA*****B****s' OR vCDOrg Equal 'MA****4' 
    AND vCDOrgvDC Equal 'MA****4-01' AND vCDvApp Equal 'vApp_T*****C******u' OR vCDOrg Equal 'MA****4' 
    AND vCDOrgvDC Equal 'MA****4-01' AND vCDvApp Equal 'vAppWWW'

  Schedule:              Daily
    Type:                Full 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:     13 (12 months)
    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     18:30:00  -->  Monday     05:30:00
          Monday     18:30:00  -->  Tuesday    05:30:00
          Tuesday    18:30:00  -->  Wednesday  05:30:00
          Wednesday  18:30:00  -->  Thursday   05:30:00
          Thursday   18:30:00  -->  Friday     05:30:00
          Friday     18:30:00  -->  Saturday   05:30:00
          Saturday   18:30:00  -->  Sunday     05:30:00

while I understand that 200 is generally a warning, and I do have successful backups after the auto-retry, it is still annoying and doesn't make my opscenter success reports look good.

any ideas on how to fix this?

6 REPLIES 6

watsons
Level 6

Error 200 means that it could not find a matching schedule to run the job.

When did your last backup complete? The job might be checking with last backup time to see if it can run right now - but might not be in your backup window. 

I will try to change to calendar-based schedule to see if it works.

npais
Level 2
Partner
I'm afraid I don't understand. Assuming that my scheduled daily-full backup last night at 6pm failed but was successful in the next attempt at 6:30, does this mean that my next backup at 6pm today will fail because it is less than 24 hours since the last backup??

watsons
Level 6

What I meant was if your last successful backup was at 6:30pm. Your next backup will only run 24 hours later at 6:30pm but if that time is not in your backup window, it may fail.. whether it fails with an error 200 or 196 I am not sure. I could be wrong.

Maybe it's better to call support and check if there is any bug about error 200 of VMware backups, I remember hearing about this some time ago but not in latest versions.

http://www.symantec.com/docs/TECH178534

npais
Level 2
Partner
Thanks @watsons, but like i said, even if we go by the 24 hour rule, it is still within my next backup window. I have opened a case with support. Will keep you posted.

sclind
Moderator
Moderator
   VIP   

I have an open case with support on exactly the same problem.  My VMware backups are set to run on odd days of the month.  More often then not they fail rc=200.  Then sometimes they run OK.

 

If I find a solution I will post it.

sclind
Moderator
Moderator
   VIP   

please check out:

https://www-secure.symantec.com/connect/forums/vmware-backup-failures-status-code-200