That is what we have done since our backups have gotten so big that they won't fit on one tape (RS6000/DLT tapedriv e). I limit the size of each file to 2gig. Rman can't really handle files larger than 2 gig, at least 8.0.6.3 can't. I also limit my datafile size to 2 gig so I can backup one datafile per backup piece. I was just hoping to skip a step and do the compress at the same time as the backups.
I have been using rman for 4 years and it works for us. The newer versions are better than the old 8.0.4 version which was very buggy. I can adjust my procedures to accommodate the increased size of the databases. Ruth ----- Original Message ----- To: <[EMAIL PROTECTED]> Sent: Wednesday, February 06, 2002 11:42 AM > Hi Ruth, > > I am new to RMAN. I am reading RMAN documentation and doing some testing on > our development box. > > We are also having same problem. Presently we do compressed full db export > using pipes. > > To avoid this problem, I am planning to limit the size of the backup piece > so that it will create multiple pieces on the disk. As soon as a piece is > completed, I will compress it and move it on to another disk. You already > may knew this option. Do you see any complications or drawbacks with this > approach. > > This is the plan I am going to use. I have't tested yet. Please pass your > suggestions. > > Thanks > Prasad > > -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Ruth Gramolini INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
