Re: Shadow Image....

The rumors of the conventional backup's demise are absolutely true and the corpse should have been buried a long time ago...

RMAN works quite well with those techniques (i.e. file-system snapshot, BCVs, shadow image, etc). First CATALOG DATAFILECOPY the snapped images to enter knowledge of their existence into the RMAN catalog, and then use BACKUP DATAFILECOPY to backup those copies onto tape. Admittedly not as straightforward as simply issuing a BACKUP DATABASE command, but that's what Perl and shell scripts are for, but the restore and recovery is no different. You get corruption checking and the ability to validate recoverability -- things that old-style scripted backups don't provide.

The DBAs still have to put the database into and out of BACKUP mode during the snapshot, but getting it to tape and -- much more importantly -- having an easy time during restore and recovery -- is best done with RMAN.

Yep, deader than roadkill. Better bury it before it stinks up the place...

on 10/9/04 4:38 AM, Hemant K Chitale at hkchital_at_singnet.com.sg wrote:

>
>
> RMAN cannot be used to create backups which rely on
> SnapShot/SnapClone/BCV/ShadowImage technologies.
> DBAs must still put the databases in Backup mode and create the "copied"
> image of the database.
>
> Hemant
>
>
> At 02:57 AM Saturday, Bobak, Mark wrote:
> Carel-Jan,
>
> It's interesting that Oracle provided this enhancement.
>
> The message I thought I was hearing (with the introduction of RMAN,
> and then with the requirement to use RMAN if you go w/ ASM), was
> that conventional backups were *eventually* going away.
>
> Perhaps the rumors of the conventional backup's demise have been
> a bit exaggerated.....
>
> -Mark
>
>
>
> Hemant K Chitale
> http://web.singnet.com.sg/~hkchital
>
>
>
>
> --
> http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l