Backup Policy

HI,
I does not have that much exposure on Backup.
Our Environment:
EBS : R12.1.3
OS:RHEL 4.6
DB:11i
DB Size: 75GB
Our Environment is not 24*7 .. we can down the database after business hours. ...
We planned to backup to D2D2T ...
We are using Symantec Backup EXEC 2010.
Please suggests us the best backup stratagies we can adopt to our business.
Thanks

Hi;
Please check:
backup and recovery startegy for EBS
Re: Backup System
backup polincy-ebs
Backup Policy for EBS can
I just sahere 2 but You can find many good previous thread in search link which is posted by Hussein Sawwan
Regard
Helios

Similar Messages

  • Backup policy on Grid, using RMAN and Recovery Catalog.

    Hello Gurus,
    I'm trying to move ahead the new features of Oracle 10g in my company. So I've already created Grid Control and will deploy Agents/Targets during the next week. I also want to switch the backup process from the archaic exp/imp to RMAN with the Recovery Catalog.
    My question is such: could anybody suggest the best book or text with solutions and descriptions of backup policy, using the Grid, RMAN and Catalog? What I want to do is to create eventually the powerful and centralized storage of every database in a company and do all daily routine from there. But as long as I'm only in the very beginning I want to gain some knowledge before the bad experience, like crashed recovery catalog and no backups for all databases :-)))
    Definitely I'll keep existing imp/exp and hotbackup for a long time. I'm not going to substitute all our backup strategy with one catalog. I just want to understand what will be the best practice in the backup perspective.
    And at all, I wonder if you please could give me very brief answer to this question: Let's say I have a huge monster with 5 disks by 500Gb RAD0+1. Is it a bad idea to store all of them in one physical machine before they will tape to backup or it could make sense? For me it sounds a bit scary, but probably if all made with the brain it's not a bad idea?
    Please, send me to some valuable and good source (like Tom Kyte or Don Burleson) Unfortunately, I didn't find anything regard the backups itself. Only pretty much general thought.
    Thanks a lot in advance.
    M.

    great!
    thanks a lot!
    this is definitely valuable info and I'll read right away. but as far as understand they suggest to use Data Guard, Standby and RAC which are the best ways to prevent your environment from crash. But in reality (I mean in my company) nobody is going to move to RAC at this point and I'm not sure, that they will have a chance to do in the next year. they just aren't up to it.
    what I'm looking for is probably some tips and hints about backups in more or less big environment, but not as big as Oracle itself :-) unfortunately, i'm the only DBA in my surrounding. i mean, i have no friends or mentors DBAs that could seat with me in a pub and pass theirs knowledge from generation to generation :-)))
    but anyway, I'll devote this week-end to this link.
    thanks a lot!

  • RMAN backup policy needed to confirm!

    Hi, All friends:
    I am working on a production db, now set up Rman backup policy.
    My purpose: keep only one backupset of datafile and control file, backup all archived logs--never delete--so database can be recovered to any time before.
    so for Rman configuration;
    configure retention policy to redundancy 1;
    in DB control, setup a night whole db backup with backup archivelog and with with delete obsolete.
    Am I right?
    if anything wrong, please tell me, I want to confirm.
    thanks a lot in advance.

    thanks for your answer.
    I want to use disk for backup storage because db size is small(only 7G) and we want a quick recovery.
    To clarity, for my understanding,
    if
    configure retention policy to redundancy 1;
    backups of archived redo logs won't be marked as obsolete, only backups of datafiles and control files will be marked as obsolete.
    so if you run delete obsolete. it won't delete backups of archived logs.
    (this is not like recovery windows, say you set retention policy to recovery window of 4 days, if you delete obsolete, RMAN will delete both backups of archived logs and data/control files)
    AM I RiGHT?
    thanks

  • RMAN Backup policy

    Hi,
    I have few basic doubts in RMAN backup policy
    1 . Is that possible to set Retention policy to recovery window in minutes??
    2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
    Regards,
    007

    1 What does the documentation of your unknown version of RMAN say? Does it states minutes are possible? If so, why are you asking rhetorical questions? (questions for which you already know the answer)
    2 Rman only considers level 0 backups to determine whether a backup is obsolete, as you can't restore from an incremental backup.
    Setting up a backup scheme for 4 days with a recovery window of 3 days wouldn't make any backup obsolete.
    Sybrand Bakker
    Senior Oracle DBA

  • Recommended backup policy for 500 users company .

    Hi Guys ,
     We are planing for a new and effective backup policy for our organization. the total data size per data may be 5-7 GB and weekly 40-45 GB .need a suggestion how to schedule backup ( how many full,incremental or differential ) per day and per week . it will be very helpful if someone suggest an idea .....     
    This topic first appeared in the Spiceworks Community

    Andrew,
    This topic has been discussed several times before on this forum. Please check the following threads for more details:
    Apps Backup
    Re: Apps Backup
    Backup Oracle Applications (11.5.10.2)
    Re: Backup Oracle Applications (11.5.10.2)
    Best Backup Strategy
    Re: Best Backup Strategy
    System Backup
    system backup
    Reommended backup and recovery startegy for EBS
    Re: Reommended backup and recovery startegy for EBS
    I say this because users complain performance problem with forms. The backup method has no impact on the system performance.

  • Script will not accept target volume when setting Windows Backup policy

    I have manually configured a Windows Backup on a VM using the GUI. I set the target volume for the backup and it works fine. However, I am trying to script out the configuration of the backup and when I run the script, I get the following output:
    Label                  : Backup
    WBDisk                 :  \\ ?\Volume{96ab04f0-5a45-11e4-80f1-00155dbae602}
    WBVolume               : Backup (E:)
    Path                   :
    TargetType             : Volume
    InheritAcl             : False
    PreserveExistingBackup : False
    Date        : 10/23/2014 12:00:00 AM
    Day         : 23
    DayOfWeek   : Thursday
    DayOfYear   : 296
    Hour        : 0
    Kind        : Unspecified
    Millisecond : 0
    Minute      : 30
    Month       : 10
    Second      : 0
    Ticks       : 635496210000000000
    TimeOfDay   : 00:30:00
    Year        : 2014
    DateTime    : Thursday, October 23, 2014 12:30:00 AM
    Date        : 10/23/2014 12:00:00 AM
    Day         : 23
    DayOfWeek   : Thursday
    DayOfYear   : 296
    Hour        : 6
    Kind        : Unspecified
    Millisecond : 0
    Minute      : 30
    Month       : 10
    Second      : 0
    Ticks       : 635496426000000000
    TimeOfDay   : 06:30:00
    Year        : 2014
    DateTime    : Thursday, October 23, 2014 6:30:00 AM
    Date        : 10/23/2014 12:00:00 AM
    Day         : 23
    DayOfWeek   : Thursday
    DayOfYear   : 296
    Hour        : 12
    Kind        : Unspecified
    Millisecond : 0
    Minute      : 30
    Month       : 10
    Second      : 0
    Ticks       : 635496642000000000
    TimeOfDay   : 12:30:00
    Year        : 2014
    DateTime    : Thursday, October 23, 2014 12:30:00 PM
    Date        : 10/23/2014 12:00:00 AM
    Day         : 23
    DayOfWeek   : Thursday
    DayOfYear   : 296
    Hour        : 18
    Kind        : Unspecified
    Millisecond : 0
    Minute      : 30
    Month       : 10
    Second      : 0
    Ticks       : 635496858000000000
    TimeOfDay   : 18:30:00
    Year        : 2014
    DateTime    : Thursday, October 23, 2014 6:30:00 PM
    Set-WBPolicy : The specified file path does not exist or is not on a locally attached disk.
    At D:\Admin\Configure_Backup.ps1:44 char:1
    + Set-WBPolicy -force -policy $BackupPolicy
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Set-WBPolicy], Exception
        + FullyQualifiedErrorId : System.Exception,Microsoft.Windows.ServerBackup.Commands.SetWBPolicy
    The E: volume is one of three drives for the VM.  I attach and detach the volume from the Hyper-V host weekly - creating a new VHD for each week of backups.  This all works fine with me doing it manually, but I want to automate the process and
    the script below won't let me.  IDEAS???
    # Open the existing policy in Edit mode
    $BackupPolicy = Get-WBPolicy -Editable
    # Now,define the parts of it.
    # First,let's specify the files to backup
    $FileSpec = New-WBFileSpec -Filespec C:\,D:\
    # and then add that to the policy we're building
    Add-WBFileSpec -policy $BackupPolicy -filespec $FileSpec
    # Remove the existing target
    $Target = Get-WBBackupTarget -Policy $BackupPolicy
    Remove-WBBackupTarget -Policy $BackupPolicy -Target $Target
    # Add the new target
    $Target = New-WBBackupTarget -VolumePath E:
    Add-WBBackupTarget -policy $BackupPolicy -target $Target
    # Add System State and Bare Metal Recovery
    Add-WBSystemState -policy $BackupPolicy
    Add-WBBareMetalRecovery -policy $BackupPolicy
    # Define the schedule
    Set-WBSchedule -policy $BackupPolicy -schedule 00:30,06:30,12:30,18:30
    # Finally, set for VSS Copy Backup
    Set-WBVssBackupOptions -policy $BackupPolicy -VssCopyBackup
    # Finally, we need to SET the policy before it actually takes control
    Set-WBPolicy -force -policy $BackupPolicy

    Hi Dan,
    Since you want to replace the destination volume for the existing backups, I recommend you can delete the existing backup task and create a new backup task, or you can also try the steps below:
    Reattach the original (old) volume and also attach the new volume to VM, then run the powershell script to
    add the new target volume firstly, then remove the old volume, after you run the script you can detach the original volume from VM.
    If there is anything else regarding this issue, please feel free to post back.
    Best Regards,
    Anna Wang

  • Backup retention policy check

    Dear all,
    I want to check rman catalog to confirm if the records are being removed as per the retention and backup policy we have implemented in our system.
    which means; how many days of incremental backups are on FRA before oracle removes from controlfile catalog and from disk. How can I check that?
    Our system is running in 11.2.0.2.3 version under Redhat linux 5 and we are using ASM.
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name ADVDB are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+ORAFLASH/sncforcl.ora';
    RMAN>
    sql > show parameter control_file_record_keep_time
    NAME                                 TYPE        VALUE
    control_file_record_keep_time        integer     31Thank you,
    Diego

    asifkabirdba wrote:
    run {
    crosscheck backup;
    delete noprompt obsolete;
    Run this on RMAN and check.
    Regards
    Asif Kabir
    Handle:      899660
    Status Level:      Newbie
    Registered:      Nov 29, 2011
    Total Posts:      22
    Total Questions:      *6 (6 unresolved)*
    -- If answered close the thread and mark your post as correct/helpfulHi Asif,
    Thank you, but, I am asking how to check how many days of incremental backups are on Flash Recovery Area before oracle removes from controlfile catalog and from disk

  • What is the best backup plan for Archive Databases in Exchange 2013?

    Hi,
    We have Exchange 2013 with Hybrid setup with O365.
    We have On premise exchange 2013 servers with 3 copies of primary Database & Single Copy of Archival DBs.
    Now we have to frame backup policy with Symantec Backup Exec which has to backup our primary & Archival DBs
    In 2007 exchange, before migration to 2013, we had policy of DBs - Weekly Full backup & Monthly Full Backup
    Please suggest what would be the best possible backup strategy we can follow with 2013 DBs.
    That too, especially for Archiving DBs
    Our Archiving Policy are - 3 category - Any emails older than 6 month OR 1 Year OR 2 Year should go to Archive mailbox.
    Keeping this in mind how to design the backup policy ? 
    Manju Gowda

    Hi Manju,
    you do not find best practice different from the common backup guidelines, as there is no archive db specific behaviour. Your users may move items to their archive at any time as well as your retention policies may move items that machted the retention policies
    at any time. The result is frequently changing content to both, mailbox and archive mailbox databases, so you need to backup both the same way. You also may handle archives together with mailboxes together in the mailbox db 
    Please keep in mind that backup usually means data availability in case of system failure. So you may consider to do a less frequent backup with your archive db with dependency to the "keep deleted items" (/mailboxes) setting on your mailbox database.
    Example:
    keep deleted items: 30 days
    backup of archive db: every 14 days
    restore procedure:
    * restore archive DB content
    * add difference from recover deleted items (or Backup Exec single item recovery) for the missing 14 days.
    So it depends more on your process than on a backup principle.
    Regards,
    Martin

  • Need Advice on RMAN backup script

    Hi;
    Can any one advice if any error or guide to make RMAN backup proper :
    Backup Policy are:
    1.     0 level backup
    2.     current log file is arvhived before backing up
    3.     backup whole database (datafiles)
    4.     backup separate control file
    5.     backup is done on disk
    6.     control file auto backup ON
    7.     only 7 days archive log are need to be preserve ; old need to be deleted
    ### one time paramters seting
    RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    ### Command for weekly 0 level backup
    run {
    allocate channel c1 type disk;
    sql 'alter system archive log current';
    backup incremental level 0 tag = weekly_database format 'o:\rman\backup\full_weekly_%d_%s_%p_%t'(database);
    release channel c1;
    configure controlfile autobackup format for device type disk to 'o:\rman\backup\auto_ctrl_weekly_%f';
    allocate channel c1 type disk;
    backup tag = weekly_arch archivelog until time 'sysdate-7' format 'o:\rman\backup\archive_weekly_%d_%s_%p_%t';
    delete archivelog until time 'sysdate-7';
    release channel c1;
    Regards
    Smith

    Dear Pierre F.;
    Actually, I just added in my backup plan to have daily backup through RMAN, instead of COLD backup.
    I have planned to take cold backup once a week. here is the side of data:
    *** datafile 410
    *** size of database : 86 GM
    *** relog files size : 250MB
    *** daily archive logs are : 250MB * 4(number of files) = 1GM aprox.
    yes, time constraint is there; just because of the size of database. and we r going for 24/7
    Is this script going to run only one per week ?
    Ans: no I this was level 0 backup; i will take level 1 incremental backup with same script daily too.
    Do you have any other RMAN script ?
    ANS: no, I will modify same script for incremental.
    after local copy of backup all backup files (RMAN) will be copy over network to backup server or we can install LTO tape device to copy directly from database server.
    kindly advise me I am new in RMAN.
    regards;
    SMITH

  • RMAN backup files are still exist since long time, how to delete?

    Dear sir;
    I'm using the below script to do daily backup, however there are many rman backup files are still exist and consumes HD size, how could I delete these files in daily bases? some files dated in FEB, MAR, APR,
    ============Daily RMAN script=========
    rman target /<<!
    backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
    backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
    backup current controlfile format '/u15/rman/control_%U.rman';
    delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
    delete noprompt obsolete;
    ================================END
    Thanks and best regards
    Ali

    Hi;
    Our backup policy should have 7 days; however we have here some files from JAN, FEB,MAR, APR /2012 WHICH ARE BEYOND THE RETENTION DATE and these files should be deleted by executing " delete noprompt obsolete; ".
    All files are exist in /u15/rman/
    -rw-r----- 1 oracle oinstall 1151763968 Jan 21 01:36 arc_backup_7kn19h4a_1_1.rman
    -rw-r----- 1 oracle oinstall 1136882176 Jan 21 01:36 arc_backup_7ln19h4q_1_1.rman
    -rw-r----- 1 oracle oinstall 1135984640 Jan 21 01:36 arc_backup_7mn19h5a_1_1.rman
    -rw-r----- 1 oracle oinstall 1126627328 Jan 21 01:37 arc_backup_7nn19h5q_1_1.rman
    -rw-r----- 1 oracle oinstall 880606720 Mar 12 02:53 arc_backup_7nn5ldhp_1_1.rman
    -rw-r----- 1 oracle oinstall 1093043712 Jan 21 01:37 arc_backup_7on19h6a_1_1.rman
    -rw-r----- 1 oracle oinstall 9797632 Dec 15 01:04 control_04mu7tcp_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 3 02:55 control_4cn4tm9k_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 4 02:53 control_4on50ahm_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 5 02:55 control_56n52v1j_1_1.rman
    -rw-r----- 1 oracle oinstall 16252928 Jan 23 01:40 control_8tn1eq3t_1_1.rman
    -rw-r----- 1 oracle oinstall 16252928 Jan 24 01:40 control_9cn1heg0_1_1.rman
    -rw-r----- 1 oracle oinstall 202940416 Dec 15 01:04 full_backup_01mu7t50_1_1.rman
    -rw-r----- 1 oracle oinstall 1097728 Dec 15 01:04 full_backup_02mu7tcc_1_1.rman
    -rw-r----- 1 oracle oinstall 201285632 Dec 14 01:04 full_backup_0nmu58ou_1_1.rman
    -rw-r----- 1 oracle oinstall 5957304320 Feb 29 02:46 full_backup_2ln4g9l1_1_1.rman
    -rw-r----- 1 oracle oinstall 4128768 Feb 29 02:47 full_backup_2mn4gft8_1_1.rman
    -rw-r----- 1 oracle oinstall 6027075584 Mar 1 02:49 full_backup_32n4o6ov_1_1.rman
    -rw-r----- 1 oracle oinstall 4128768 Mar 1 02:49 full_backup_33n4od66_1_1.rman
    -rw-r----- 1 oracle oinstall 6187171840 Mar 2 02:51 full_backup_3gn4qr50_1_1.rman
    -rw-r----- 1 oracle oinstall 4145152 Mar 2 02:51 full_backup_3hn4r1kn_1_1.rman
    -rw-r----- 1 oracle oinstall 6115786752 Mar 3 02:51 full_backup_40n4tfgu_1_1.rman
    above is a short list of contents.
    to do our daily backup we perform the following script (in daily)
    ==================
    backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
    backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
    backup current controlfile format '/u15/rman/control_%U.rman';
    delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
    delete noprompt obsolete;
    ==================
    Thanks and best regards
    Ali

  • Oracle Database 11g Backup Deduplication using CommVault

    Hi Everyone
    We have recently implemented Commvault solution for a Backup and Recovery of Oracle database and other IT softwares / fileservers. Oracle E-business suite 12.1.1 is implemented in our organization with 11g database 11.2.0.3.6, for all the backups we have enabled deduplication and it is giving more then 90& dedup on all softwares except for Oracle database, for oracle it is giving just 40% or max 50% which is not acceptable to our organization
    Production DB sizee = 257 GB
    Used block = 157 GB
    Backup Policy = Daily Full backup incremental 0 with commvault dedup enabled
    Deduplication % = 40 to 50 %
    requiement = should be over 90%
    Our database is small and there are around 6 to 7 GB of archives daily so the data is not changing much, commvault support is saying that the block signatures are changing due to this we are not getting the full deduplication and they are asking us to check what changes are made during the day and oracle support says that once the rman backup is completed it has nothing to do with the third party dedup, and we are stuck so i thought to put it in the forum and may be oracle gurus can help find a solution here, my questions are:
    1. Is there a non issue of not getting fully deduplication of Oracle database using third party deduplication solutions? Is there any one who have used oracle backups with Commvault and dedup enabled, any help would be great
    2. I also need to know how to check what changes are made in database on a daily basis.
    Please help
    Thank you
    Regards
    shahrukh

    The instructions are the same, where the server is physical or virtual. Best bet is the docs at http://docs.oracle.com/database/121/RILIN/toc.htm
    This may also be useful - RAC Attack - Oracle Cluster Database at Home - Wikibooks, open books for an open world

  • RMAN Problem -- Crosscheck backup & list backup showing different results

    Pls Help !!!
    I'm using RMAN for backup policy is to recovery window of 7 days
    but even on thired day after incremental 0 backup ... if run 'crosscheck backup'
    it shows the previous as expired but when i issue 'list backup' it says available
    what may be the problem.......
    Backup volume is on RAID10 (ZFS on SOLARIS 10)
    Thanks in advance !!
    Regds
    Gyanendra Singh

    if run 'crosscheck backup'
    it shows the previous as expired but when i issueHave u deleted the previous backup...........because according to my knowledge crosscheck command is used to validate any inconsistency between the logical and physical backup files.
    'list backup' it says available
    what may be the problem.......
    List backup will show the previous backup because of the recovery window
    Try this
    crosscheck database
    delete expired
    list backup
    and then see the result
    Regards
    Amit Raghuvanshi

  • Full, Differential and log backup or Full and log backup? What to choose?

    Hi All,
    I have a SQL Server 2012 database of size <1 gb and the data of this db is expected to grow by 100 MB every month (i.e., ~ 1 gb per year). We have to backup this database to Azure Blob storage and data loss of 2 hrs. is accepted. Now can you please suggest
    the best database backup policy. The option i have in mind are
    1. Full database backup every week followed by differential backup every 2 hrs (or)
    2. Full database backup every week followed by differential backup every day followed by transactional log backup every 2 hrs (or)
    3. Full database backup every week followed by transactional log backup every 2 hrs
    Note: My database is in Full recovery model

    Well its bit difficult for us to tell what would be best for you as you only told RPO but did not tell us RTO. I mean in how much time, if disaster strikes, would you like database to be up and running. Backup policy would depend on that
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Restore Online Backup in SCDPM 2012 R2

    Dear all,
    i have a question on SCDPM 2012 R2 + Azure Backup.
    i had deployed such solution and disk backup are perfect! However, i had configured online backup policy to Azure Backup since February and i noticed i do not have the options to allow me to perform online restore!
    Below is my online protection policy:
    i believe i configured it correct to adhere below policy:
    - perform a monthly backup and keep for ONE year
    - perform a yearly backup and keep for SEVEN years
    but when i go to recovery tab, it just doesnt show February backup, nor March 2nd have any backup. all the backup available are disk short term of 30 days.

    Hi DeVaLiaN,
    Thanks for posting here!
    Each DPM backup to Azure Backup is a recovery point. With an Azure current limit of 366 recovery points your retention time for all backups shouldn’t exceed the 366 limit. In other words the retention times you set for you daily + weekly + monthly
    + yearly backups should sum up to 366 or less.
    You might want to double check your configuration.
    Refer to the below listed articles which might help you narrow down the issue.
    http://blogs.technet.com/b/systemcenter/archive/2014/03/16/using-azure-backup-with-dpm.aspx
    http://social.technet.microsoft.com/wiki/contents/articles/19751.system-center-2012-data-protection-manager-dpm-sp1-part-4-backup-to-azure.aspx
    https://msdn.microsoft.com/en-us/library/azure/dn337332.aspx
    Hope this helps!
    Regards,
    Sadiqh

  • Rman Retention policy to recovery window

    Hi,
    I have few basic doubts in RMAN backup policy
    1 . Is that possible to set Retention policy to recovery window in minutes??
    2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
    Regards,
    007

    1) Syntax is .... TO RECOVERY WINDOW OF integer DAYS ... no other time statement.
    2) Backups become obsolete when no longer needed to fulfil a retention policy. In a (theoretical) scenario, you perform a level 0 backup and then only incremental backups, the starting level 0 backup must be kept for ever (even if it WOULD be possible to define a recovery window in minutes).
    Werner

Maybe you are looking for