cancel
Showing results for 
Search instead for 
Did you mean: 

Datastore value-8 and limit jobs per policy set to-1 for vmware backups

arjun7
Level 4

Datastore value-8 and limit jobs per policy value is set to-1 for vmware backups. then howmany discover, snapshot and vm backup jobs will run.

NBU master and medis server version- 7.6.0.1

2 ACCEPTED SOLUTIONS

Accepted Solutions

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

from that specific policy it is going to 1 job

and if you have mulitple vmware polices..trying to take the backup of the VMs from the same data stores.. then datastore limit will come to active.

in my opinon 8 jobs for data store is high... .. what is your avarage data store unitlization in your enviornment.?

View solution in original post

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Limit jobs per policy of 1 will limit max number of active jobs to 1 - as per your instruction.

Alternatively you can change it to the default of 0 (unlimited) and allow Resource Limits to do its job.

 

**** EDIT ***

Correction!!

Limit jobs per policy only limits the number of discovery jobs if VIP is used.

See http://www.symantec.com/docs/HOWTO92128 

For the policies that select virtual machines automatically (Query Builder)

The Limit jobs per policy option controls the number of parent (discovery) jobs that run simultaneously for the policy. This option does not limit the number of snapshot jobs and backup (bpbkar) jobs that the parent job launches. For example, if this option is set to 1 and you begin a backup of a policy that discovers 100 virtual machines: all the snapshot jobs and backup jobs for each of the 100 virtual machines are allowed to execute simultaneously. Only the initial discovery job counts against Limit jobs per policy. If you begin a second backup of the policy, its discovery job cannot start until all the child jobs from the first backup are complete.

View solution in original post

8 REPLIES 8

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

from that specific policy it is going to 1 job

and if you have mulitple vmware polices..trying to take the backup of the VMs from the same data stores.. then datastore limit will come to active.

in my opinon 8 jobs for data store is high... .. what is your avarage data store unitlization in your enviornment.?

View solution in original post

arjun7
Level 4

sorry...the datastore value is set to '2'.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I agree - 8 jobs per datastore is too high.

Have a look at this discussion:

https://www-secure.symantec.com/connect/forums/v-ray-best-number-vadp-streams-datastore 
(Some of the TNs have been expired in the meantime)

NetBackup for VMware best practices:
http://www.symantec.com/docs/HOWTO70892 

arjun7
Level 4

 For example, if the 'limit jobs for policy' option is set to 1 and you begin a backup of a policy that discovers 100 virtual machines and datastore value is set to 2. then howmany backups will run in this situation.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

If all VMs are in the same policy, then max jobs per policy of 1 will limit number of active jobs to 1.

Limit jobs per policy policy attribute is described in NetBackup Administrator's Guide, Volume I 

Chapter 20, p.670.

arjun7
Level 4

 (1). 1-discovery job, 100-snapshot and backups jobs will run........ or

(2).  1-dicovery job , 2-snapshot and backups jobs will run, because datastore value is set to 2

which point is correct.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Limit jobs per policy of 1 will limit max number of active jobs to 1 - as per your instruction.

Alternatively you can change it to the default of 0 (unlimited) and allow Resource Limits to do its job.

 

**** EDIT ***

Correction!!

Limit jobs per policy only limits the number of discovery jobs if VIP is used.

See http://www.symantec.com/docs/HOWTO92128 

For the policies that select virtual machines automatically (Query Builder)

The Limit jobs per policy option controls the number of parent (discovery) jobs that run simultaneously for the policy. This option does not limit the number of snapshot jobs and backup (bpbkar) jobs that the parent job launches. For example, if this option is set to 1 and you begin a backup of a policy that discovers 100 virtual machines: all the snapshot jobs and backup jobs for each of the 100 virtual machines are allowed to execute simultaneously. Only the initial discovery job counts against Limit jobs per policy. If you begin a second backup of the policy, its discovery job cannot start until all the child jobs from the first backup are complete.

View solution in original post

arjun7
Level 4

Thanks Ram and Marianne.. Now I got clarification from both your comments...