Re: rman script to backup on both instances in a RAC env.

  • From: "Jeffery Thomas" <jeffthomas24@xxxxxxxxx>
  • To: oracle-l <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 2 May 2007 08:09:41 -0400

If you do try and parallelize the backup across multiple instances -- then
all instances that participated in the backup must also be available to
perform recovery?


On 5/2/07, Johnson, William L (TEIS) <WLJohnson@xxxxxxxxxxxxxxxxxxx> wrote:

 Try allocating channel t3 and/or t4 to the second instance in the RAC
environment.  Currently we run 4 channels in our RAC backups – 2 to each

Here is the syntax we use in our backup to allocate a channel to the
second instance in the RAC environment…

allocate channel node1_t4 type 'SBT_TAPE' MAXOPENFILES 16
parms="ENV=(NB_ORA_CLASS=class_name-w-hot)" connect '


*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Nizar Ahmed
*Sent:* Wednesday, May 02, 2007 5:51 AM
*To:* LazyDBA Discussion
*Cc:* oracle-l
*Subject:* rman script to backup on both instances in a RAC env.

Currently my RMAN script runs on one instance of a two node RAC.

I want to modify it to run on both instances. I have tried but no luck in
allocation of channels or connection to both instance. How can I modify this



connect target rmanbk/123@odsprod

connect catalog rman_ods/123@rmancat




set command id to 'odsprod1';

allocate channel t1 type SBT_TAPE  parms

allocate channel t2 type SBT_TAPE  parms

allocate channel t3 type SBT_TAPE  parms

allocate channel t4 type SBT_TAPE  parms

sql 'alter database backup controlfile to trace';

backup archivelog  all delete input

format 'odsprod_arc_%T_%s.bak';

 backup incremental level=2 cumulative

 filesperset 50

 tag 'Level 2 Backup'

format 'odsprod_db_%T_%s.bak'

(database include current controlfile);

release channel t1;

release channel t2;

release channel t3;

release channel t4;


 Disclaimer: The information in this email and in any files transmitted
with it,
is intended only for the addressee and may contain confidential and/or
privileged material.
Access to this email by anyone else is unauthorized. If you receive this
in error,
please contact the sender immediately and delete the material from any
If you are not the intended recipient, any disclosure, copying,
distribution or
any action taken or omitted to be taken in reliance on it, is strictly
Statement and opinions expressed in this e-mail are those of the sender,
and do not
necessarily reflect those of STC.

Other related posts: