Good Morning Dave, 

I know of no way to change the number of job retries on a policy or client or 
schedule object. 
I can see where this would be a nice feature to have. 

There are many different reasons that a rman backup job can fail. 

>From a netbackup end of things one could have a 96 error no scratch tapes, 
A media fault, A network issue. Etc. 
Or it could be a oracle issue. 

For something like a media issue that is cleared up on the netbackup end of 
things I would think that the dba's would want the backup to be retried. For an 
oracle issue I do not know enough. 

But either way I believe that you could add the control you require into the 
script that netbackup runs on the client to run the rman commands. Might not be 
easy. 

I am sure other that know oracle can give you a better answer then this, and I 
look forward to learning. 
As a simple case of go or nogo without any variance based on the prior failure 
you could try.
In the beginning of the script you could set a state value of "STARTED" into a 
file on client. At the end of the script the vaule could be changed to 
"COMPLETE". 
At the start of the script if the value is not "COMPLETE" the script could give 
an error return and exit. Someone would have to change the statue value to 
"STARTED" to enable the script to run. This could be done after clearing the 
problem. This can also be used to bypass the running of the backup at the 
script level when the   oracle dba's are doing maintenance work on the oracle 
database. If you use and check for some state value of "BYPASS" then the script 
could exit with a normal return code and netbackup would not have a backup but 
would think that everything is ok and not retry. 
You  could also use touch files instead on one state file. 

Let us know what you end of doing to solve this issue. 

len

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu 
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Dave 
Markham
Sent: Monday, April 06, 2009 8:17 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Number of retries query

Guys does anyone know if you can change the number of job retries in xx 
time period on a per client basis?

I currently have the global set at 2 tries per 12 hours which is fine 
for our needs and good in the fact it will try a failed backup.

However the DBA for an RMAN and oracle policy doesn't want this to 
happen and re-run a backup if there is a failure so i need to try and 
find a way of setting it to 1 try for just one client.

Any ideas?

Cheers
_______________________________________________
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