backup run

[ramLUKE]

I have 2 policies win23 and win46 and each have 5 clients.

Scenario:

Both policies run at 02:00 AM and both have same priority

• Which will run first?
• if win23 runs then other will be in queue or will be ignored?
• What are the factors which NBU keeps in mind (hierarchical order) while running the backup which have  same start time ?ally)
• And out of 5 client ,which client backup will run first?(alphabatiically)?

NBU 7.1.0.2

LINUX OS

[Marianne · Accepted solution]

It all depends on available resources and if Multiplexing is enabled or not.

If both policies are due at exactly the same time, they will both be submitted. The amount of jobs that go active depends on available resources.

Have you read the article about Frequency based scheduling that I referred you to in your other post? 

Please also read through How NetBackup determines which schedule to run next in NBU Admin Guide I as well as About multiplexing all the way through to Example of using multiplexing with schedules. 

You can use 'nbpemreq -predict_all -date <mm/dd/yyyy HH:MM:SS>' to check/verify.

This looks like another WHAT IF scenario.

You are the best person to determine what the effect of schedules have on your environment.

We are happy to assist with real issues.

PS:

I believe you are aware of all of these posts?

https://www-secure.symantec.com/connect/forums/frequency 

https://www-secure.symantec.com/connect/forums/himy-backup-window-set-0600-am 

https://www-secure.symantec.com/connect/forums/query-8 

https://www-secure.symantec.com/connect/forums/schedule-confusion

[ramLUKE]

Multiplexing is not enabled

Backup is going on disk.

[revarooo]

Whichever one hits the queue and requests the resources first. Simples.

[ramLUKE]

It does not depends on the Schedule name,retention level,client not run for many days...etc ..etc

[revarooo]

No it's which ever one hits the callback queue first and gets the resources assigned.

There may be some other underlying logic underneath the hood. Why do you need to know this?

[RamNagalla]

ramLUKE,

please gothough the Marianne suggestions, and posts listed above, they will help you to understand it.. 

[ramLUKE]

Because i need to configure backup for my environment.Please tell me that logic or rule .

[revarooo]

It depends on resources such as drives and how your policies are configured. Go and read Mariannes post as already suggested. IF you don't have the available resources then some jobs will queue if you don't use multiplexing with your policies configured correctly and don't have enough drives etc some jobs may queue.

[ramLUKE]

If it is in a single policy,then NBU will neglet the other schedule which coincides?

[Marianne]

Let me guess: Data Domain???

Please show us Storage Unit Settings:

bpstulist -L

[Marianne]

You need to give us details of your config:

bppllist <policy-name> -U

bpstulist -L

Output of nbpemreq as per my post above.

PS: Have you read the sections in the manual as per my post above?

Have a look at the example in the manual - it applies to disk as well when you have Maximum concurrent jobs enabled in STU and MPX in policy schedules.

Also show us job details of a queued job.

We have messed around enough with theory. 
Please show us something to work with.

[revarooo]

This doesn't compute. You were talking about 2 separate policies before. Now you are talking about schedules? Schedules in 1 policy or shedules in multiple policies. Nothing will be 'ignored' if you have the resources multiple policies can run, if you don't then 1 will queue, the 1 that is last in the queue.

[Joseph_TKLee]

• Which will run first?  => Both
• if win23 runs then other will be in queue or will be ignored? => Both will run as the maximum concurrent jobs of the disk storage units will be around 40.
• What are the factors which NBU keeps in mind (hierarchical order) while running the backup which have  same start time ?ally) ==> Dunno^^
• And out of 5 client ,which client backup will run first?(alphabatiically)? ==> almost same time. Master server will request each client

Cheers,

[ramLUKE]

Label:                wd1

Storage Unit Type:    Disk

Media Subtype:        DiskPool (6)

Host Connection:      lx21

Host Connection:      lx22

Concurrent Jobs:      1

On Demand Only:       yes

Robot Type:           (not robotic)

Max Fragment Size:    524288

Max MPX:              1

Block Sharing:        no

File System Export:   no

Ok On Root:           no

Disk Pool:            wd1-dp

Policy Name:       WIN21

  Policy Type:         MS-Windows

  Active:              yes

  Effective date:      11/19/2012 16:00:00

  Backup network drvs: no

  Collect TIR info:    no

  Mult. Data Streams:  no

  Client Encrypt:      no

  Checkpoint:          yes

       Interval:       30

  Policy Priority:     99999

  Max Jobs/Policy:     Unlimited

  Disaster Recovery:   0

  Collect BMR info:    no

  Residence:           FULL2

  Volume Pool:        RAM

  Server Group:        *ANY*

  Keyword:             (none specified)

  Data Classification:       BC

  Residence is Storage Lifecycle Policy:    yes

  Application Discovery:      no

  Discovery Lifetime:      0 seconds

  Granular Restore Info:  no

  Ignore Client Direct:  yes

  HW/OS/Client:  PC            Windows2003   win23

  Include:  ALL_LOCAL_DRIVES

  Schedule:          Monthly_FULL

    Type:            Full Backup

    Maximum MPX:     4

    Synthetic:       0

    PFI Recovery:    0

    Retention Level: 0 (5 weeks)

    Number Copies:   1

    Fail on Error:   0

    Residence:       mon2

    Volume Pool:     (same as policy volume pool)

    Server Group:    (same as specified for policy)

    Calendar sched: Enabled

      Sunday, Week 5

    Residence is Storage Lifecycle Policy:     1

    Daily Windows:

          Sunday     16:00:00  -->  Sunday     22:00:00

  Schedule:          Weekly_FULL

    Type:            Full Backup

    Frequency:       every 4 days

    Maximum MPX:     4

    Synthetic:       0

    PFI Recovery:    0

    Retention Level: 0 (5 weeks)

    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

    Daily Windows:

          Sunday     16:00:00  -->  Sunday     22:00:00

  Schedule:          INCR

    Type:            Cumulative Incremental Backup

    Frequency:       every 12 hours

    Maximum MPX:     4

    Synthetic:       0

    PFI Recovery:    0

    Retention Level: 0 (5 weeks)

    Number Copies:   1

    Fail on Error:   0

    Residence:       INCR2

    Volume Pool:     (same as policy volume pool)

    Server Group:    (same as specified for policy)

      EXCLUDE DATE 0 - 05/21/2010

      EXCLUDE DATE 1 - 05/24/2010

    Residence is Storage Lifecycle Policy:     1

    Daily Windows:

          Monday     20:30:00  -->  Monday     24:00:00

          Tuesday    20:30:00  -->  Tuesday    24:00:00

          Wednesday  20:30:00  -->  Wednesday  24:00:00

          Thursday   20:30:00  -->  Thursday   24:00:00

          Friday     20:30:00  -->  Friday     24:00:00

          Saturday   20:30:00  -->  Saturday   24:00:00

[Marianne]

Concurrent Jobs:      1

Not good!

No wonder you have status 196's!

But none of the schedules in your policy seem to use this STU?
The policy also does not reflect the config in your opening post.
 

It does not help to show us bits and pieces of unrelated output...