Re: RMAN delete BEFORE backup

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default

Observed tight storage on Saturday sometimes breaking last L1 backup job. Execute 'crosscheck archivelog all' and 'delete expired archivelog all' to free space. Then sufficient space available for a Level 0 to complete.

Changed to a mid-week Level 0 as a workaround. Is this the best space utilization scenario?

Great name by the way!

Cheers,

• Alan Sterger

On 2/7/2011 2:23 PM, Guillermo Alan Bort wrote:
> Alan,
>
> What is the retention policy set in rman?. The delete input cannot
> be deleted before the backup, because if you do, then there would be
> nothing to backu up, because you just deleted it... On the other hand,
> if the retention policy is a RECOVERY WINDOW, it's possible to run the
> delete obsolete before the backup, HOWEVER, if you have a lvl0 once a
> week, then that level 0 would be kept as well as all the level 1
> backups to match the recovery window.
>
> Can you upgrade to 10g? after 10g, it's possible to compress the
> backups on the fly, and only generate a compressed dump... it's a hog
> on CPU, but it saves space....
>
> hth
> Alan.-
>
>
> On Mon, Feb 7, 2011 at 3:22 PM, Alan Sterger <asterger_at_earthlink.net
> <mailto:asterger_at_earthlink.net>> wrote:
>
> Hello Listers,
>
> Using Oracle 9i RMAN template below. Level 0 executes on Sunday,
> Level 1 the rest of the week.
>
> Client has limited disk space. Can the 'delete input' and/or
> 'delete obsolete' be executed BEFORE the two 'backup' commands?
>
> Are there other tweaks that can be applied? Got a better script?
>
> run {
> allocate channel Channel1 type disk format
> 'F:\orabackups\%d_%s_%p_%t';
> backup incremental level 1
> ( database include current controlfile );
> backup ( archivelog all delete input );
> }
> allocate channel for maintenance device type disk;
> delete obsolete device type disk;
>
>
> Cheers,
>
> Alan Sterger
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

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