The usage that I've seen and used is to start with a level 0, and from there on out you'd only take level 1 incrementals. Then, based on your recovery window, you could roll your base backup image forward, for example to 7 days ago, if that is your window. It saves you the time of not having to do another level 0, but having a recent level 0 image to start with for recovery. The reason I stopped using it is that you HAVE to do a backup COPY. I didn't have the disk to hold an actual copy, and needed to have compression. Don. On 12/4/06, Steiner, Randy <Randy.Steiner@xxxxxxxx> wrote:
In the documentation, it is refered to as Incrementally Updated Backups: Rolling forward image copy backups. It is a level 1 incremental that is applied to the image copy and rolled forward to the point in time when the level 1 was created. > -----Original Message----- > From: Jared Still [mailto:jkstill@xxxxxxxxx] > Sent: Monday, December 04, 2006 11:50 AM > To: Steiner, Randy > Cc: oracle-l@xxxxxxxxxxxxx > Subject: Re: rman incremental merge > > On 12/4/06, Steiner, Randy <Randy.Steiner@xxxxxxxx> wrote: > > Have people been using the incremental merge feature of > rman successfully? > > It seems a little scary to me. > > > By 'incremental merge', are you referring to restoring a > database using incremental backups? (sorry, unfamiliar with this term) > > If so, consider this: why would that be any scarier than > apply archive logs? > > > -- > Jared Still > Certifiable Oracle DBA and Part Time Perl Evangelist > > -- //www.freelists.org/webpage/oracle-l
-- //www.freelists.org/webpage/oracle-l