Extended retention for ORACLE backup using command line backup on v11 SP6

Last post 04-28-2017, 6:04 AM by Mateusz Szyba. 2 replies.
Sort Posts: Previous Next
  • Extended retention for ORACLE backup using command line backup on v11 SP6
    Posted: 04-26-2017, 9:43 AM

    Hi,

    I have question about retention for Oracle backup from command line (3-party-Backup). For example, We have third script for backup (weekly full, incremental and archive logs). All backup is linked to one storage policy.

    I know that we can configure subclient with Selective Online Full backup which is intended for long retention backup (we can selected this option on content and via aux copy copy to selective copy with long retention). 

    For commandline backup, on v11 SP6 version we have posssibilty to configure long retention on selective copy for 3-party-Backup job? We can use this scipt:

    http://documentation.commvault.com/commvault/v11_sp6/article?p=products/oracle/t_ora_copy_full_cycle.htm 

    and

    http://documentation.commvault.com/commvault/v11_sp6/article?p=products/oracle/t_ora_enable_retention.htm

    for configure extended retention for 3-part backup?

    Best regards.

  • Re: Extended retention for ORACLE backup using command line backup on v11 SP6
    Posted: 04-26-2017, 12:41 PM
    • efg is not online. Last active: 03-24-2020, 6:10 PM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Master
    • Points 1,720

    Hi,

    Command line backups do not qualify for extended retention.

    This is documented here: Retention Rules for Oracle Backups

    Scroll down and you will see the following:

    Retention Rules for Command Line Backups

    • The third party command line log backups can be linked to third party command line data backups as well as any other kind of backup data as per regular data link rule.
    • Data from third-party command line backups ages differently than data from backups initiated through the CommCell Console. Retention cycles are not used for copies involved in operations from the third-party command line. For such operations, data is aged according to the associated retention time. However, you can manually set the retention time for each third party command line job from the storage policy copy. The command line log backups are aged according to the retention time set for its associated command line data backup job.
    • Command line full jobs are aged only when all of the incremental data backups in that cycle are eligible for pruning.
    • Command line backup are not eligible for extended retention.

    It is possible to manually retain these jobs by right clicking on the job in the storage policy copy and selecting retain.


    Ernst F. Graeler
    Senior Engineer III
    Development
  • Re: Extended retention for ORACLE backup using command line backup on v11 SP6
    Posted: 04-28-2017, 6:04 AM

    Hi,

     

    On Your last sentense You wrote about:

    It is possible to manually retain these jobs by right clicking on the job in the storage policy copy and selecting retain.

    I belived that, when We set on RMAN for example:

    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;

    We have retention 30 days for job on RMAN site and when we change retention via Commvault GUI we don't change retention for RMAN job.

    Of course, for extendet retantion, for this case we should set subclient for Selective Online Full backup ( http://documentation.commvault.com/commvault/v11/article?p=products/oracle/t_ora_sel_onln_full_sc.htm )

    for incremental backup subclient for selective online incremental ( http://documentation.commvault.com/commvault/v11/article?p=products/oracle/t_ora_sel_onln_incr.htm ) and for archive logs subclient for archive logs (  http://documentation.commvault.com/commvault/v11/article?p=products/oracle/t_ora_log_subclnt.htm ) 

    This sbuclient should be linked to one storage policy with selective copy.

     

    Do You agree with me?

    Thanks in advance.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy