Re: [Veritas-bu] Oracle RMAN backups fail with Netbackup status 245 - Solved

2010-12-16 Thread Justin Piszcz
I have battled this problem a long time ago, with 5.1 it didn't seem to 
happen.  With 6.0+ it started.

If the client is in more than 1 policy you *SHOULD* specify the policy, 
e.g. export NB_ORA_POLICY I believe for the policyname of the backup (user 
backup).

This solves the problem.
They can also add that into the ORA rman backup script.

Justin.

On Thu, 16 Dec 2010, Lightner, Jeff wrote:

 Just posting this for list posterity as I didn't see much in search
 (mostly about 245 on Informix).



 We're running NBU 6.5x and this morning I saw an RMAN archive log backup
 that runs at night as well as the man RMAN database backup we run
 starting at 9 AM both failed with status code 245.   Interestingly the
 detail for both jobs had almost no information and didn't even allow me
 to see what a 245 was.



 A web search shows this issue for Informix (from 2004) but not for
 Oracle RMAN.



 Running bperror -statuscode 245 displayed:

 the specified policy is not of the correct client type

 A user backup specified a policy that is not the type that is required
 for the client.





 Running bperror -jobid 632020 which is one of the failed jobs didn't
 help much as it only displayed:

 1292508052 1 66 4 atubks01 632020 -1 0 *NULL* nbpem CLIENT ralpha
 POLICY RALPH-DB-ORA  SCHED Full-Offsite  EXIT STATUS 245 (the specified
 policy is not of the correct client type)



 On checking the two policies I found that both had policy as Standard
 instead of Oracle.Yesterday my co-worker had tried to do a mass
 change to move policies from one of our data domain units to another.
 One of the unintended consequences of what he did was it reactivated
 many of our deactivated policies.   My theory is that it also changed
 the policy type from Oracle to Standard on these two policies as they
 were among the ones moved.

 
 __

 Jeff Lightner | UNIX/Linux Administrator | DS Waters of America, Inc |
 5660 New Northside Drive, Ste 250 | Atlanta, GA 30328
 *: (Direct Dial) 770-486-3516 |*: (Cell) 678-772-0018 |
 *:jlight...@water.com

 Proud partner. Susan G. Komen for the Cure.

 Please consider our environment before printing this e-mail or attachments.
 --
 CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential 
 information and is for the sole use of the intended recipient(s). If you are 
 not the intended recipient, any disclosure, copying, distribution, or use of 
 the contents of this information is prohibited and may be unlawful. If you 
 have received this electronic transmission in error, please reply immediately 
 to the sender that you have received the message in error, and delete it. 
 Thank you.
 --

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Oracle RMAN backups

2006-11-27 Thread smpt
netbackup 6 works the same way


  ---Original Message---
  From: Austin Murphy [EMAIL PROTECTED]
  Subject: Re: [Veritas-bu] Oracle RMAN backups
  Sent: 27 Nov '06 22:15
  
  On 11/24/06, mkiles [EMAIL PROTECTED] wrote:
   I am going through the NetBackup for Oracle Admin
   guide, it mentions that you can have multiple
   schedules in the policy with different retention
   periods. That is you can have a FULL backup schedule
   with retention period of 1 year and an INCREMENTAL
   backup schedule with retention of 1 month.
  
   This may be new in NBU 6, but I remeber in NBU 5.x,
   the retention period that was always used was that of
   Default-Application-Backup schedule.
  
   So in my NBU 5.0 environment, I have ONE policy for
   FULL Oracle backup with 1 year retention and ONE
   Oracle policy for INCREMENTAL backups with 1 month
   retention. Each policy has 2 schedules in it, one of
   those is Default-Application-Backup schedule, both
   schedule have same retntion period, i.e. for FULL
   Backup policy retention period for both schedules is 1
   year and for INCREMENTAL policy retention period for
   both schedules is 1 month.
  
   So my question is, is it the same behaviour in NBU 6.0
   for Oracle and SQL backups, or it has changed.
  
  I'm familiar with NB 5.1, where there are 2 kinds of Oracle schedules:
  Automatic and Application.
  - Automatic schedules simply act as triggers and execute the RMAN
  script on the client.
  - Application schedules receive the incoming datastream(s) generated
  by the RMAN script.
  
  If the incoming data stream does not specify an Application schedule
  (by default, it doesn't), NetBackup will assign it the first schedule
  that meets the following criteria:
  - in the specified policy (by default this is sent)
  - open window
  
  You can easily set the window so you get incrementals to be retained
  for a different time period than the fulls, but you can't
  differentiate between backups done at the same time of the week, but
  with different retentions. (weekly/monthly/yearly for instance)
  
  The retention level of the Automatic backup schedule is not useful.
  It specifies how long to keep record of the fact that an Automatic
  backup schedule was triggered.  The retention level of the incoming
  data is set by the schedule used to receive the incoming data stream.
  
  Turn up logging for bphdb and you will see which variables get passed
  to the RMAN script.
  # NB_ORA_PC_SCHED is the name of the AUTO schedule.
  # NB_ORA_SCHED is the name of the APP schedule.
  
  Using these variables, you can have the RMAN script pick which
  Application Backup schedule to use.  This will let you avoid using
  multiple policies to backup one Oracle server.
  You can even skip the AUTO schedule and use your own timer/scheduler
  to trigger the RMAN script whenever you want.
  
  You send the variables back to NetBackup like this:
  ...
  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  SEND 'NB_ORA_SCHED=$NB_ORA_SCHED';
  BACKUP
  ...
  
  This technique does not apply to MS-SQL backups (w/ NB 5.1) since they
  use a different mechanism to send data to NetBackup.
  
  I don't know how this applies to NB 6.x.
  
  Austin
  ___
  Veritas-bu [EMAIL PROTECTED]
  http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
  
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Oracle RMAN backups

2006-11-25 Thread Wayne T Smith
NetBackup is pretty weird in this area, IMHO.  In order to to have 
multiple retentions in one Oracle Agent policy, you need to have 
multiple application backup schedules, not just a default application 
backup schedule.

As with regular file system backups, separate policies are independent 
(except that your agent script probably erases archive redologs under 
some circumstances).

The archives of this mailing list are filled with advice on agent 
backups, how they work and how people use them. I recommend searching 
for posts of  Michael F. Lavelle for excellent information on the subject.

Everything I've written above applies to v5 ... I haven't moved to v6.0.

cheers, wayne

 I am going through the NetBackup for Oracle Admin
 guide, it mentions that you can have multiple
 schedules in the policy with different retention
 periods. That is you can have a FULL backup schedule
 with retention period of 1 year and an INCREMENTAL
 backup schedule with retention of 1 month.

 This may be new in NBU 6, but I remeber in NBU 5.x,
 the retention period that was always used was that of
 Default-Application-Backup schedule.

 So in my NBU 5.0 environment, I have ONE policy for
 FULL Oracle backup with 1 year retention and ONE
 Oracle policy for INCREMENTAL backups with 1 month
 retention. Each policy has 2 schedules in it, one of
 those is Default-Application-Backup schedule, both
 schedule have same retntion period, i.e. for FULL
 Backup policy retention period for both schedules is 1
 year and for INCREMENTAL policy retention period for
 both schedules is 1 month.

 So my question is, is it the same behaviour in NBU 6.0
 for Oracle and SQL backups, or it has changed.
   

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Oracle RMAN backups

2006-11-24 Thread Whelan, Patrick
I was under the impression that RMAN backups were supposed to have INFINITE 
retention and that RMAN took care of expiring the images, there by keeping the 
RMAN catalog in sync with the NetBackup catalog. Otherwise RMAN will think 
there is a good backup, but NetBackup has expired it, if the retention level is 
different than what RMAN expects.

Someone please correct me if I'm wrong.

Patrick Whelan
NetBackup Specialist
Architect  Engineering
+44 20 7863 5243

Of all the things I've lost, I miss my mind the most! - Unknown

There are only 10 kinds of people on earth - those who understand binary
and those who don't.

Als sie mich holten,
gab es keinen mehr, der protestieren konnte 
-- Martin Niemöller

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mkiles
Sent: 24 November 2006 16:11
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Oracle RMAN backups

Hi All

I am going through the NetBackup for Oracle Admin
guide, it mentions that you can have multiple
schedules in the policy with different retention
periods. That is you can have a FULL backup schedule
with retention period of 1 year and an INCREMENTAL
backup schedule with retention of 1 month.

This may be new in NBU 6, but I remeber in NBU 5.x,
the retention period that was always used was that of
Default-Application-Backup schedule. 

So in my NBU 5.0 environment, I have ONE policy for
FULL Oracle backup with 1 year retention and ONE
Oracle policy for INCREMENTAL backups with 1 month
retention. Each policy has 2 schedules in it, one of
those is Default-Application-Backup schedule, both
schedule have same retntion period, i.e. for FULL
Backup policy retention period for both schedules is 1
year and for INCREMENTAL policy retention period for
both schedules is 1 month.

So my question is, is it the same behaviour in NBU 6.0
for Oracle and SQL backups, or it has changed.

THX


 

Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


*
The message is intended for the named addressee only and may not be disclosed 
to or used by anyone else, nor may it be copied in any way. 

The contents of this message and its attachments are confidential and may also 
be subject to legal privilege.  If you are not the named addressee and/or have 
received this message in error, please advise us by e-mailing [EMAIL PROTECTED] 
and delete the message and any attachments without retaining any copies. 

Internet communications are not secure and COLT does not accept responsibility 
for this message, its contents nor responsibility for any viruses. 

No contracts can be created or varied on behalf of COLT Telecommunications, its 
subsidiaries or affiliates (COLT) and any other party by email Communications 
unless expressly agreed in writing with such other party.  

Please note that incoming emails will be automatically scanned to eliminate 
potential viruses and unsolicited promotional emails. For more information 
refer to www.colt.net or contact us on +44(0)20 7390 3900.


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Oracle RMAN backups

2006-11-24 Thread mkiles
I am talking about NetBackup expiration only, RMAN
catalog should be cross checked with NBU catalog,
periodically to keep both in sync.

In my case I dont use RMAN catalog, I use control
file.

Thx
--- Whelan, Patrick [EMAIL PROTECTED] wrote:

 I was under the impression that RMAN backups were
 supposed to have INFINITE retention and that RMAN
 took care of expiring the images, there by keeping
 the RMAN catalog in sync with the NetBackup catalog.
 Otherwise RMAN will think there is a good backup,
 but NetBackup has expired it, if the retention level
 is different than what RMAN expects.
 
 Someone please correct me if I'm wrong.
 
 Patrick Whelan
 NetBackup Specialist
 Architect  Engineering
 +44 20 7863 5243
 
 Of all the things I've lost, I miss my mind the
 most! - Unknown
 
 There are only 10 kinds of people on earth - those
 who understand binary
 and those who don't.
 
 Als sie mich holten,
 gab es keinen mehr, der protestieren konnte 
 -- Martin Niemöller
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]
 On Behalf Of mkiles
 Sent: 24 November 2006 16:11
 To: veritas-bu@mailman.eng.auburn.edu
 Subject: [Veritas-bu] Oracle RMAN backups
 
 Hi All
 
 I am going through the NetBackup for Oracle Admin
 guide, it mentions that you can have multiple
 schedules in the policy with different retention
 periods. That is you can have a FULL backup schedule
 with retention period of 1 year and an INCREMENTAL
 backup schedule with retention of 1 month.
 
 This may be new in NBU 6, but I remeber in NBU 5.x,
 the retention period that was always used was that
 of
 Default-Application-Backup schedule. 
 
 So in my NBU 5.0 environment, I have ONE policy for
 FULL Oracle backup with 1 year retention and ONE
 Oracle policy for INCREMENTAL backups with 1 month
 retention. Each policy has 2 schedules in it, one of
 those is Default-Application-Backup schedule, both
 schedule have same retntion period, i.e. for FULL
 Backup policy retention period for both schedules is
 1
 year and for INCREMENTAL policy retention period for
 both schedules is 1 month.
 
 So my question is, is it the same behaviour in NBU
 6.0
 for Oracle and SQL backups, or it has changed.
 
 THX
 
 
  


 Do you Yahoo!?
 Everyone is raving about the all-new Yahoo! Mail
 beta.
 http://new.mail.yahoo.com
 ___
 Veritas-bu maillist  - 
 Veritas-bu@mailman.eng.auburn.edu

http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
 
 

*
 The message is intended for the named addressee only
 and may not be disclosed to or used by anyone else,
 nor may it be copied in any way. 
 
 The contents of this message and its attachments are
 confidential and may also be subject to legal
 privilege.  If you are not the named addressee
 and/or have received this message in error, please
 advise us by e-mailing [EMAIL PROTECTED] and delete
 the message and any attachments without retaining
 any copies. 
 
 Internet communications are not secure and COLT does
 not accept responsibility for this message, its
 contents nor responsibility for any viruses. 
 
 No contracts can be created or varied on behalf of
 COLT Telecommunications, its subsidiaries or
 affiliates (COLT) and any other party by email
 Communications unless expressly agreed in writing
 with such other party.  
 
 Please note that incoming emails will be
 automatically scanned to eliminate potential viruses
 and unsolicited promotional emails. For more
 information refer to www.colt.net or contact us on
 +44(0)20 7390 3900.
 
 



 

Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Oracle RMAN backups and media IDs

2006-06-19 Thread ida3248b
Hi Paul

Oracle(rman) dosn't track the media ID as default, it requests a restore of a 
fileset. 

Regards
Michael

On Mon, 19 Jun 2006 09:27:21 -0400, Paul Keating wrote
 When using the Netbackup Oracle Agent, and a client initiated 
 backup is written, does the Oracle apps retain any record of media ID?
 f'rinstance, if a backup is run, then the tape is bpduplicated to
 another media ID, then the 2nd copy is promoted to primary.
 When a restore is attempted, will the proper tape be accessed?
 I'm assuming the application tracks something like the image ID, and
 netbackup will figure out the proper media.
 
 ??
 
 Paul


--
Cybercity Webhosting (http://www.cybercity.dk)

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu