Re: Take the archives during the backup

From: healdv_at_googlemail.com <healdv_at_gmail.com>
Date: Sat, 28 Aug 2010 09:54:59 -0700 (PDT)
Message-ID: <43dd71c6-4229-401f-bdaf-33d9fe08a19a_at_l20g2000yqe.googlegroups.com>

On Aug 28, 5:40 pm, "hea..._at_googlemail.com" <hea..._at_gmail.com> wrote:
> On Aug 28, 7:28 am, "bob123" <bob..._at_gmail.com> wrote:
>
>
>
> > OK Mark thanks
> > the goal is duplicate a production database
> > to a test database
> > my answers below
>
> > <Additional infromation is necessary to properly answer your question.
> > <
> > <Are you using a backup set or file copies?
> > backup
>
> > <Did you include the archive logs as part of the backup set or not?
> > Yes but this is my problem.
> > To have the smallest backupset
> > I would like to have only the archives
> > necessary to open the copy of the database.
> > I don't do delete input on the source database
> > so no problem for my source database.
>
> > <Are you restoring to the same or a different machine?
> > to another machine
>
> > <Do you use a recovery catalog?
> > nocatalog
>
> > <Options would include Point in Time Recovery (PITR) to a predetermined
> > <SCN or timestamp or potentially you could perform a recover until
> > <cancel operation.
> > OK but to have the smallest backup set
> > how can I only  include the archives needed to
> > recover the test database.
> > Taking all the archives is to big for my
> > working window.
>
> > Thanks again
>
> Using RMAN the most practical and safest approach to me would be to
> backup all the archives that have not been backed up, then backup the
> database plus the archives logs and then you would just copy the files
> from the time of the second backup which you could get from the
> listing the backups to know which files to copy and you still have
> your archives backed up from before.
>
> Something like:
>
> SQL 'ALTER SYSTEM CHECKPOINT'';
> SQL 'ALTER SYSTEM SWITCH LOGFILE'';
> backup archivelog all;
> SQL 'ALTER SYSTEM CHECKPOINT'';
> backup database plus archivelog;

I've just thought, you could just do the duplicate database using rman using the auxillary, look up duplicate database. Ive used it before to create standby databases but can use it just to clone a database too which will also give you the desired effect you are wanting. If the other system does not have the same paths (same directory layout) then you would have to rename files to the new paths as you duplicate so will have to tell us if it has the same directory structure as the current system. Received on Sat Aug 28 2010 - 11:54:59 CDT