RE: RMAN Sizing - Anomaly?
- From: "Weatherman, John" <John.Weatherman@xxxxxxxxxxx>
- To: <bbel5@xxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 16 Feb 2009 13:48:44 -0600
Bambi,
Have you done a "RMAN> list backupset;" to verify what is in each set?
Are all the files really in the "...plus archivelog" backup? How does a
"RMAN> backup as compressed backupset archivelog all;" look?
What version is this coming off of?
Thanks,
John
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Bellows, Bambi
(Comsys)
Sent: Monday, February 16, 2009 1:32 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RMAN Sizing - Anomaly?
Friends --
I'm at a loss to explain why two nearly identical scripts -- one to
backup the database only and one to backup the database plus archivelog
should have this particular sizing anomaly. First, here are the
scripts...
1)
$ORACLE_HOME/bin/rman <<EOF
connect target;
connect catalog $RMANID/$RMAN@$RMAN_CATDB;
backup as compressed backupset database;
EOF
And
2)
$ORACLE_HOME/bin/rman <<EOF
connect target;
connect catalog $RMANID/$RMAN@$RMAN_CATDB;
backup as compressed backupset database plus archivelog;
EOF
Now the results...
Database only: 48 minutes - 39.1GB
Database plus archivelog: 63 minutes - 15.2GB
Why should the database plus archivelog be 40% smaller than the database
without? I've run this test a bunch of different times, sometimes
setting the incremental level to 0, sometimes not; sometimes running the
db+arch first, sometimes second. But consistently, the db+arch is
appreciably smaller than the db without. How come?
Thanks!
Bambi.
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
