β06-04-2014 07:25 AM
I have a Windows Server 2008 R2 64-bit, Netbackup 7.5.0.6 master server for my virtual datacenter. I run vmware query based policies with overlapping full and differential backup schedules. I have 150 policies for about 2,000 virtual servers that start off in 30 minute increments from each other spread out accross a 24 hours per day, 7day window. Over time this has migrated to a steady and fairly even rate of data processing distribution throughtout the window. My backup failure rate before removing the false positive is under 1.5% on average each week. It would be less that that if there was a way to prevent these error/exit code 200's from occuring which are only informational in nature. Is there a way that when Netbackup finds that it has no jobs that are needed to run for a query based policy that they could be an exit code 0?
Solved! Go to Solution.
β06-04-2014 12:43 PM
I don't understand why you have 08:00 - 08:00 windows as well as 01:00 - 01:00 schedules in the same policy...
Why not all from midnight to midnight?
i.e.
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
β06-04-2014 07:50 AM
what is the frequency set for each schedule (both full and incr)?
does both full and incrmental backups are in same policy?
may i know how did you determined this EC 200 is due to schedule overlap.. since it has other reasons to though this error...?
http://www.symantec.com/business/support/index?page=content&id=HOWTO35074
β06-04-2014 08:38 AM
I have the full and differential schedules each in the same policy. I allow a backup to run at any time during the day or night on any day of the week whenever each type needs to run. My bandwidth usage through my switches is very even and steady. I've eliminated large spikes in this manner. I also routinely check each host that I'm indeed capturing fulls at least once a week and differentials on each day that a full doesn't need to run. It works great and I have veried the exit code 200's are indeed due to overlapping schedules and are informational only. It's annoying that Netbackup can determine that backup doesn't need to run but exits as an error. It's not an error.
β06-04-2014 08:47 AM
Do you have Frequency or Calendar based scheduling?
Please share the schedule section of 'bppllist <policy-name> -U'
β06-04-2014 09:03 AM
Here's an example of one of my policies. (I had to redact hostname/customer name info)
------------------------------------------------------------
Policy Name: XXXXXX
Policy Type: VMware
Active: yes
Effective date: 05/03/2012 13:37:22
File Restore Raw: 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: XXXXXXXXXXXXXXX
Volume Pool: XXXXXXXXX
Server Group: *ANY*
Keyword: (none specified)
Data Classification: Silver
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: no
HW/OS/Client: VMware Virtual_Machi MEDIA_SERVER
Include: vmware:/?filter=VMFolder StartsWith "vm%5CCustomer Servers%5CXXX" AND VMDNSName IsSet
Schedule: Full
Type: Full Backup
Frequency: every 7 days
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 8 (1 year)
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 08:00:00 --> Monday 08:00:00
Monday 08:00:00 --> Tuesday 08:00:00
Tuesday 08:00:00 --> Wednesday 08:00:00
Wednesday 08:00:00 --> Thursday 08:00:00
Thursday 08:00:00 --> Friday 08:00:00
Friday 08:00:00 --> Saturday 08:00:00
Saturday 08:00:00 --> Sunday 08:00:00
Schedule: Differential-Inc
Type: Differential Incremental Backup
Frequency: every 1 day
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 4 (2 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 08:00:00 --> Monday 08:00:00
Monday 08:00:00 --> Tuesday 08:00:00
Tuesday 08:00:00 --> Wednesday 08:00:00
Wednesday 08:00:00 --> Thursday 08:00:00
Thursday 08:00:00 --> Friday 08:00:00
Friday 08:00:00 --> Saturday 08:00:00
Saturday 08:00:00 --> Sunday 08:00:00
Schedule: Monthly_Fulls
Type: Full Backup
Frequency: every 28 days
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: Weekly_Fulls
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 1
Schedule indexing: 0
Daily Windows:
Sunday 01:00:00 --> Monday 01:00:00
Monday 01:00:00 --> Tuesday 01:00:00
Tuesday 01:00:00 --> Wednesday 01:00:00
Wednesday 01:00:00 --> Thursday 01:00:00
Thursday 01:00:00 --> Friday 01:00:00
Friday 01:00:00 --> Saturday 01:00:00
Saturday 01:00:00 --> Sunday 01:00:00
β06-04-2014 09:06 AM
Frequency Based.
β06-04-2014 12:43 PM
I don't understand why you have 08:00 - 08:00 windows as well as 01:00 - 01:00 schedules in the same policy...
Why not all from midnight to midnight?
i.e.
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
β06-05-2014 05:21 AM
I tried midnight to midnight and I found I was getting credit buffering on my switches because too many jobs were trying to start at once. I found by offsetting every schedule in each policy by 30 minutes and restricting my jobs to 1 snapshot per datastore (I have over 200 datastores) and 6 streams per storage unit that I can spread the bandwidth load out more evenly throughout the day and week. It was actually impacting the fabric performance before and impacting VM servers, so I had to spread it out.
β06-23-2014 08:17 AM
What I ended up doing was removing all my full schedules and re-creating them with the same schedules as the differentials. I also found I had some policies that the vm folder didn't have any powered on vm's in them and deactivated them. That has eliminated all the error code 200's. Thank you Marianne, as always!