Home » RDBMS Server » Backup & Recovery » RMAN - script (Redhat linux3, 10.2)
RMAN - script [message #355656] Sun, 26 October 2008 22:37 Go to next message
mmee
Messages: 38
Registered: July 2007
Member

hi to all..
this script intension is reduce the CPU utilization,full backup with archivelog.

i need your feedback or any other method?


>rman.sh
connect target
sql 'alter system switch logfile';
backup archivelog all;
Backup as COMPRESSED BACKUPSET DURATION 00:50 minimize load database;
sql 'alter system switch logfile';
backup archivelog all not backed 1 times;
restore database validate;
Re: RMAN - script [message #355669 is a reply to message #355656] Mon, 27 October 2008 00:14 Go to previous messageGo to next message
Michel Cadot
Messages: 64106
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
If you want to minimize cpu utilization don't compress.

Regards
Michel
Re: RMAN - script [message #355676 is a reply to message #355669] Mon, 27 October 2008 00:56 Go to previous messageGo to next message
mmee
Messages: 38
Registered: July 2007
Member

thnk you michel

due to space concern, i was use in compress mode..

but actuly my problem is ..

my rman backup while running its goes to hang. and it's happening monthly four or five times.

and

1) I could not find any information from alert log
2)Rman and recovery i/o, lot of wait event in my AWR report.
3) while backup running time cpu utilization 100%.

as per point 3 and 2, i have changed my rman script..below here

OLD script:
-----------
>rman.sh
connect target
Backup as COMPRESSED BACKUPSET database plus archivelog;
restore database validate;

New script:
-----------
>rman.sh
connect target
sql 'alter system switch logfile';
backup archivelog all;
Backup as COMPRESSED BACKUPSET DURATION 00:50 minimize load database;
sql 'alter system switch logfile';
backup archivelog all not backed 1 times;
restore database validate;


Pls guide me..

Re: RMAN - script [message #355688 is a reply to message #355676] Mon, 27 October 2008 01:42 Go to previous messageGo to next message
Michel Cadot
Messages: 64106
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
If you have at the same time space and cpu problem, I think your system is undersized and there is few things to do.
Backup less often and only tablespace per tablespace, separate archivelog and database backup.

Regards
Michel
Re: RMAN - script [message #355787 is a reply to message #355688] Mon, 27 October 2008 09:28 Go to previous messageGo to next message
varunvir
Messages: 363
Registered: November 2007
Senior Member
Hi Michel,
Can we compress backup set manually at O.S level If RMAN
is utlizing lot of CPU.The only concern is if we 
compress backup manually then delete obsolete command 
will work fine to delete manually comressed backup sets.

Can you tell me the use of following command in RMAN script:-
sql 'alter system switch logfile';
Regards,
Varun Punj,


Re: RMAN - script [message #355789 is a reply to message #355787] Mon, 27 October 2008 09:49 Go to previous messageGo to next message
Michel Cadot
Messages: 64106
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
You can compress at OS level but it then does not save cpu.

alter system switch logfile

Regards
Michel
Re: RMAN - script [message #356755 is a reply to message #355656] Sun, 02 November 2008 02:36 Go to previous messageGo to next message
mmee
Messages: 38
Registered: July 2007
Member

pls go through output....

rmna>backup database;


Starting backup at 13-OCT-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00006 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/plant_user
input datafile fno=00007 name=/opt/datahist/plant_hist.dbf
input datafile fno=00002 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/undotbs01.dbf
input datafile fno=00001 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/system01.dbf
input datafile fno=00003 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/sysaux01.dbf
input datafile fno=00005 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/example01.dbf
input datafile fno=00008 name=/opt/data/oradata/orcl/plant_aq
input datafile fno=00004 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/users01.dbf
channel ORA_DISK_1: starting piece 1 at 13-OCT-08
channel ORA_DISK_1: finished piece 1 at 13-OCT-08
piece handle=/home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCLDRS/backupset/2008_10_13/o1_mf_nnndf_TAG20081013
T111555_4h5r4o8z_.bkp tag=TAG20081013T111555 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:18:16
Finished backup at 13-OCT-08


rman> backup as compressed backupset database;

using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00006 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/plant_user
input datafile fno=00007 name=/opt/datahist/plant_hist.dbf
input datafile fno=00002 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/undotbs01.dbf
input datafile fno=00001 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/system01.dbf
input datafile fno=00003 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/sysaux01.dbf
input datafile fno=00005 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/example01.dbf
input datafile fno=00008 name=/opt/data/oradata/orcl/plant_aq
input datafile fno=00004 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/users01.dbf
channel ORA_DISK_1: starting piece 1 at 27-OCT-08
channel ORA_DISK_1: finished piece 1 at 27-OCT-08
piece handle=/home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCLDRS/backupset/2008_10_27/o1_mf_nnndf_TAG20081027
T111552_4jbodksf_.bkp tag=TAG20081027T111552 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:22:26
Finished backup at 27-OCT-08



rman>backup as COMPRESSED BACKUPSET DURATION 02:00 minimize load database;


using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00006 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/plant_user
input datafile fno=00007 name=/opt/datahist/plant_hist.dbf
input datafile fno=00002 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/undotbs01.dbf
input datafile fno=00001 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/system01.dbf
input datafile fno=00003 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/sysaux01.dbf
input datafile fno=00005 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/example01.dbf
input datafile fno=00008 name=/opt/data/oradata/orcl/plant_aq
input datafile fno=00004 name=/home/oracle/oracle/product/10.2.0/oradata/orcldrs/users01.dbf
channel ORA_DISK_1: starting piece 1 at 28-OCT-08
channel ORA_DISK_1: throttle time: 1:###:37
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 10/28/2008 13:01:42
ORA-19591: backup aborted because job time exceeded duration time


my observation:
1)i have taken three type of backup,(pls refer above output)
a)normal backup ------- sucessful
b)compressed backup ---- sucessful
c)duration backup ----- error
2) my cpu utilation very low while Duration backup running.

my query:
1) why my duration backup is unsucessfull or error ?



pls give me your feedback...

Re: RMAN - script [message #356779 is a reply to message #356755] Sun, 02 November 2008 06:01 Go to previous messageGo to next message
Michel Cadot
Messages: 64106
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Because it can't finished in 2 minutes in minize load mode.
I think you should use one or the other parameter but nor both at the same. You have to choose between load and duration.

Regards
Michel
Re: RMAN - script [message #356863 is a reply to message #356779] Sun, 02 November 2008 22:40 Go to previous messageGo to next message
mmee
Messages: 38
Registered: July 2007
Member

Hi michle...

Because it can't finished in 2 minutes in minize load mode.
but i have received abort message after 2 hrs
and
DURATION 00:00 (it means -- HH:MM),



I think you should use one or the other parameter but nor both at the same. You have to choose between load and duration.
DURATION command having two parameter
a)minimize time (default)
b)minimize load

if i use minimize time parameter, definetlay cpu utilation is goes to high, so that i can use minimize load.

i don't know what is wrong with my command? i realy appriciate if you explain little more?

And

i have changed my script also..

New script:
-----------
>rman.sh
connect target
sql 'alter system switch logfile';
backup archivelog all;
Backup as COMPRESSED BACKUPSET datafile 1,2,3;
Backup as COMPRESSED BACKUPSET datafile 4,5,6;
sql 'alter system switch logfile';
backup archivelog all not backed 1 times;
restore database validate;


pls guide to me


Re: RMAN - script [message #356872 is a reply to message #356863] Sun, 02 November 2008 23:15 Go to previous message
Michel Cadot
Messages: 64106
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
Because it can't finished in 2 minutes in minize load mode.
but i have received abort message after 2 hrs
and
DURATION 00:00 (it means -- HH:MM),

Was just a typo, I meant hours not minutes.

Quote:
if i use minimize time parameter, definetlay cpu utilation is goes to high, so that i can use minimize load.

Yes that what I said, in this case don't limit the duration. You can't have (or seldomly) a low load and a short duration.

Regards
Michel
Previous Topic: standby recovery help please
Next Topic: Storing RMAN Backup at different locations.
Goto Forum:
  


Current Time: Mon Dec 05 02:31:11 CST 2016

Total time taken to generate the page: 0.16691 seconds