And we have a winner.
The "default priorities" (ie, JOB_PRIORITY in bp.conf) control at what
priority some types of jobs will spawn, but where priority is a saved
configuration knob (especially, policies, but probably see also duplications
under Vault and SLP) it is checked at the time that configuration is
added.
That means that I do need to go change all my existing policies (which
isn't that big a deal, looping bpplinfo around output from bppllist) but also
that if you (as I do) frequently use bppolicynew -sameas, you won't get the new
defaults.
No further comment on the first/second issue at this
time.
-- gabriel rosenkoetter Radian Group Inc, Senior Systems
Engineer gabriel.rosenkoetter AT radian DOT biz, 215 231 1556
Ok, take two.
There has to be a value for the policy priority, period.
If you do not specify one when creating the policy, it will accept the default
value of whatever is in the Default Job Priorities list. If you create a new
policy with the GUI, it automatically fills in the value based on the setting in
the aforementioned list, whereas on the CLI you have the option of specifying it
or accepting the default value, again pulled from the list, by omitting this
option.
With that said, my feeling
is the priority is read from the policy and not from the Default Job Priorities
list. However, I don't know the difference between the first and second priority
which you alluded to. Perhaps this could be something like a Vault policy, with
its own priority, which spawns a duplication job, which has a different
priority. If that example is true, then the vault policy priority overrides the
dupe's.
This is all speculation, and
Sounds Good (TM), and is inline with what you have come up with, but doesn't
help since I don't know for sure either.
Rusty Major, MCSE, BCFP, VCS ▪
Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite
200, Houston TX 77079 ▪ 281-584-4693 Keeping
People and Information Connected® ▪ http://availability.sungard.com/ P Think before you print
CONFIDENTIALITY: This e-mail
(including any attachments) may contain confidential, proprietary and privileged
information, and unauthorized disclosure or use is prohibited. If you
received this e-mail in error, please notify the sender and delete this e-mail
from your system.
"Rosenkoetter, Gabriel"
<Gabriel.Rosenkoetter AT radian DOT biz>
02/04/2009 11:53 AM
|
To
| "'Rusty.Major AT sungard DOT com'"
<Rusty.Major AT sungard DOT com>
|
cc
| "veritas-bu AT mailman.eng.auburn DOT edu"
<veritas-bu AT mailman.eng.auburn DOT edu>
|
Subject
| RE: [Veritas-bu] Making use of
6.5.2+ default priorities in the presence of pre-existing policy
priority settings |
|
Rusty, your answer on the first question doesn't really get at what I
want. I want to NOT override the default settings. For example, if I change the
default priority for backups to 50000 (it's initially set to 0), but have 0 for
a policy's priority setting, at which priority is the policy evaluated? I think
that it should be at 50000 (which is what I want, to make all backups a higher
priority than duplications, for example), but the documentation is unclear,
given that it asserts that the policy priority will "override" the default
priority, but doesn't provide a NULL value for the policy priority.
-- gabriel rosenkoetter Radian Group Inc, Senior Systems
Engineer gabriel.rosenkoetter AT radian DOT biz, 215 231 1556
From: Rusty.Major AT sungard DOT com
[mailto:Rusty.Major AT sungard DOT com] Sent: Wednesday, February 04, 2009
12:42 PM To: Rosenkoetter, Gabriel Cc:
veritas-bu AT mailman.eng.auburn DOT edu;
veritas-bu-bounces AT mailman.eng.auburn DOT edu Subject: Re: [Veritas-bu]
Making use of 6.5.2+ default priorities in the presence of pre-existing policy
priority settings
Gabe,
For your first question, if I'm reading it right, any policy set to 0
has the lowest priority. When creating a policy, the default priority is 0
unless specified otherwise. I think that the two descriptions are saying the
same thing differently. Symantec has alluded in the past to wanting to shore up
these differences in all the different documentation.
For the second question, I have no
idea.
HTH,
Rusty Major, MCSE, BCFP,
VCS ▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge
Suite 200, Houston TX 77079 ▪ 281-584-4693 Keeping People and Information Connected® ▪ http://availability.sungard.com/ P Think before you print
CONFIDENTIALITY: This e-mail
(including any attachments) may contain confidential, proprietary and privileged
information, and unauthorized disclosure or use is prohibited. If you
received this e-mail in error, please notify the sender and delete this e-mail
from your system.
"Rosenkoetter, Gabriel"
<Gabriel.Rosenkoetter AT radian DOT biz> Sent by:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
02/04/2009 11:18 AM
|
To
| "veritas-bu AT mailman.eng.auburn DOT edu"
<veritas-bu AT mailman.eng.auburn DOT edu>
|
cc
|
|
Subject
| [Veritas-bu] Making use of 6.5.2+
default priorities in the presence of pre-existing policy priority
settings |
|
In my environments, there are already
some policy priority settings in place. For the most part, I would like to clear
those and make use of default priorities... but I'm hazy on what "clear"
means.
The bpplinfo man page says:
-priority
priority
The priority of
this policy in relation to other policies.
Priority is greater than or equal to 0. This value
determines the order in which policies
are run. The higher the
value, the earlier the policy is run. The default is 0,
which is the lowest priority.
And the 6.5.2
documentation update says (on page 369):
bpplinfo Use the -priority
option to specify a new priority for the backup
job that overrides the default job priority.
Has anyone yet
determined empirically whether a priority setting of 0 (which is the default if
no priority is specified with bppolicynew) on the policy is a special case that
means "use the default" rather than "override the default", even if the priority
was previously set to a higher number?
The 6.5.2 documentation update
also mysteriously refers to a "first" and "second" priority in the
"Understanding the Job Priority setting" section (on page 358):
The
NetBackup Resource Broker (NBRB) maintains resource requests for jobs in a
queue. NBRB evaluates the requests sequentially and sorts them based on
the following criteria: * The request's first priority. * The request's
second priority. * The birth time (when the Resource Broker receives the
request). The first priority is weighted more heavily than the second
priority, and the second priority is weighted more heavily than the birth
time.
Has anyone sorted out what "first" and "second" mean
here?
-- gabriel rosenkoetter Radian Group Inc, Senior Systems
Engineer gabriel.rosenkoetter AT radian DOT biz, 215 231
1556
_______________________________________________ Veritas-bu
maillist -
Veritas-bu AT mailman.eng.auburn DOT edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|