cancel
Showing results for 
Search instead for 
Did you mean: 

why is my monthly backup policy using daily pool?

manatee
Level 6

NBU 7.7.3

daily.PNG

you will notice that my monthly backup policy uses the SLP monthly. please take note of the "Volumne Pool" column. it says "Daily".

below is the SLP definition for the above "Oracle_Monthly_Policy". it correctly shows to use the "Monthly" pool.

monthly.PNG

question now is, why my monthly backup policy shows volume pool "Daily"?

regards,

2 ACCEPTED SOLUTIONS

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

This has been a known issue for a long time. 
If the client exists in more than one policy, the wrong policy can be selected by the child jobs.
The policy name should be included in the script.

See: https://www.veritas.com/support/en_US/article.TECH31742

View solution in original post

fixed!

it's a bug in the Java GUI. the simple solution is a bit.. simple but the actual solution is to never make copies of existing backup policies. better create a fresh one to avoid this Java bug.

long term solution is to avoid Java entirely :)

View solution in original post

5 REPLIES 5

Marianne
Level 6
Partner    VIP    Accredited Certified

This has been a known issue for a long time. 
If the client exists in more than one policy, the wrong policy can be selected by the child jobs.
The policy name should be included in the script.

See: https://www.veritas.com/support/en_US/article.TECH31742

two follow up questions:

  1. we are already using option 2 as specified in the link:
    1. SEND 'NB_ORA_CLIENT=avs0021f600005f,NB_ORA_POLICY=Monthly_avs0021f600005f,NB_ORA_SERV=ovmmanager';
  2. and will there be a fix if this is a known issue?

 

 

Marianne
Level 6
Partner    VIP    Accredited Certified

Check that all parts of the script contains the backup policy variable:
BACKUP .... DATABASE
BACKUP .... ARCHIVELOG
BACKUP  ....  CURRENT CONTROLFILE

If all checks out, best to log a Support call. 
Ask them at the same time if this will be fixed.

fixed!

it's a bug in the Java GUI. the simple solution is a bit.. simple but the actual solution is to never make copies of existing backup policies. better create a fresh one to avoid this Java bug.

long term solution is to avoid Java entirely :)

Marianne
Level 6
Partner    VIP    Accredited Certified

Another known issue for which there is a downloadable hotfix:

https://www.veritas.com/support/en_US/article.000109333