FAQ
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

Search Discussions

  • Guillermo Alan Bort at Feb 7, 2011 at 7:23 pm
    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 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
  • Alan Sterger at Feb 7, 2011 at 8:04 pm
    Alan,

    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 > 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
  • Guillermo Alan Bort at Feb 7, 2011 at 8:41 pm
    If you are going to use a redundnacy 1, then I'd take a full backup every
    day and just delete the old one... that saves the most space and makes
    recovery fastest. but it makes backup slower. How are you safeguarding
    backups? are they staying on the same storage as the db? are they being
    shipped to tape?

    cheers
    Alan.-
    On Mon, Feb 7, 2011 at 5:04 PM, Alan Sterger wrote:

    Alan,

    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>> 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
  • Jack van Zanen at Feb 7, 2011 at 10:19 pm
    I hope this is hypothetical question only.

    Get client to invest in more disk space. Most likely cheaper than the amount
    of time (money) spent on a new backup strategy and the testing involved with
    it.

    Jack van Zanen

    This e-mail and any attachments may contain confidential material for the
    sole use of the intended recipient. If you are not the intended recipient,
    please be aware that any disclosure, copying, distribution or use of this
    e-mail or any attachment is prohibited. If you have received this e-mail in
    error, please contact the sender and delete all copies.
    Thank you for your cooperation
    On Tue, Feb 8, 2011 at 5:22 AM, Alan Sterger 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
  • Niall Litchfield at Feb 8, 2011 at 12:38 pm
    Hi Alan

    I'm sure you'll have done this already for the client but please impress
    upon them that enough space on media to *always* have a known good completed
    backup available is not optional. Suppose (just one failure scenario) that
    you delete the old backup then start backing up only to have a fatal
    hardware error corrupting the system datafile. RMAN will error on backup (as
    the database crashes!) and you will have no way back. There are other
    failure scenarios as well. Bottom line you need the disk space to store a
    known good backup and the new backup before you delete the old one.

    What can you do to alleviate the problem if the client doesn't want to
    address the above?

    First you could upgrade to 10g or higher (11.2.0.2 would be my current
    recommendation as anything else is currently a terminal release or
    desupported to all intents and purposes). This gets you built in backup
    compression. (and a host of other RMAN improvements, that amongst other
    things mean you'll likely have smaller "uncompressed" backups as well).

    Second this appears to be a windows system. In the event that this is the
    case and the client likes the idea of running current software even less
    than the idea of buying disk then you could compress the F:\orabackups
    directory using NTFS compression which will slow the backup process down
    somewhat but may well buy you the space you need.

    My experience is that every time folks get creative about saving disk space
    on backup media then sooner or later they find they haven't got the
    necessary resources to recover from some unexpected event. Disk isn't
    cheap - despite what the vendors say - lost databases tend to be more
    expensive though.
    On Mon, Feb 7, 2011 at 6:22 PM, Alan Sterger 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

    --
    Niall Litchfield
    Oracle DBA
    http://www.orawin.info

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

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouporacle-l @
categoriesoracle
postedFeb 7, '11 at 6:22p
activeFeb 8, '11 at 12:38p
posts6
users4
websiteoracle.com

People

Translate

site design / logo © 2022 Grokbase