Re: Impact on running rman

  • From: "Jared Still" <jkstill@xxxxxxxxx>
  • To: "Robert Freeman" <robertgfreeman@xxxxxxxxx>
  • Date: Wed, 27 Jun 2007 12:09:51 -0700

On 6/27/07, Robert Freeman <robertgfreeman@xxxxxxxxx> wrote:


Pretty cool, eh? I believe (need to look this up to be sure) that rate is
deprecated in 10g... still available, but not really supported anymore.



I misread the docs.

BACKUP DURATION 4:00 TABLESPACE users;

RMAN backs up the specified data at the maximum possible speed. If the
backup is
not complete in four hours, the backup is interrupted. Any completed
backupsets are
retained and can be used in restore operations, even if the entire backup is
not
complete. Any incomplete backupsets are discarded.


What needs to be done here is to ensure that your backup is not in 1
backupset, or it is
possible you'll never get a backup.

Yes it is a neat feature.  RMAN however gets more and more complex.

I didn't see anything in the docs about RATE being deprecated. Possibly in
another doc.

The RATE parameter specifies the bytes/second that RMAN reads on this
channel.
Use this parameter to set an upper limit for bytes read so that RMAN does
not
consume excessive disk bandwidth and degrade online performance.
For example, set RATE=1500K. If each disk drive delivers 3 MB/second, then
RMAN
leaves some disk bandwidth available to the online system.


--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

Other related posts: