Retention Policy and Managed folder based retention

What is difference between "Retention Policy/ Policy Tags" and " Managed Content Settings"?
In my setup , my managed folder folder become general folder after following steps
1. Created Managed folder
2. Created managed content settings for IPM.post and IPM.Appointment with retention action "Delete and Allow recovery".
3. Created managed policy and applied to 1 mailbox, and this is working properly
But After that,
1. Created 3 retention tags(1 for inbox, 1 for sent, 1 personal).
2. Created retention policy combining these 3 tags.
3. Applied to SAME mailbox
4. Ran 'ManagedFolderAssitant'
**After this, Managed folder become general outlook folder.
So, cant I have "Managed folder based retention for managed folders" and General retention for "Inbox,Sent"

Exchange 2010 RTM introduced Retention Policies as the successor to the Message Records Management (MRM) technology introduced in Exchange 2007. MRM was the successor to Mailbox Manager Policies in Exchange 2003. Message Records Management is called MRM
1.0 and Retention Policies is being called MRM 2.0 for short. MRM 1.0 as well as MRM 2.0 are both available in Exchange 2010. Only difference is we can manage Retention Policies from the EMC and EMS, but the Managed Folder Mailbox Policy is only Managed from
the EMS through cmdlets in Exchange 2010 SP1.
It completely depends on your requirements when to use MRM 1.0 and when to Use MRM 2.0.
 Certain new features are added in MRM 2.0 (Retention Policy) which allow us to manage our mailbox email items at very granular level. But if we are still happy with earlier version MRM 1.0 then we can continue using Managed folder mailbox
Policy in Exchange 2010.
[ Note: If we are Using the Retention Policy (MRM 2.0) then we can view the expiry of  each and every email items of the folders on which the retention Policy is tagged and this can be only view from OWA and Outlook 2010, But this feature
is not available  for  Managed Folder Mailbox Policy (MRM 1.0) ]
We cannot use the Base Folder only switch in MRM 2.0 because it is TAG  specific (DPT, RPT, and PPT) not Managed Folder specific.
Managed folder Mailbox Policy is folder specific this would be the major difference.
Refer to this link :
Retention policies vs Managed folders

Similar Messages

  • Retention policy and deletion of archived files

    hello, I 'am a novice DBA having a backup question.
    Our retention policy is set to 14 days; weekly we have full database backup; daily we have an incremental backup.
    See scripts below.
    The drive "\\is003s012\rhea\rman" where the backup files reside has files older than 2 months.
    I expected these files to be deleted already by rman.
    I can't find the cause why these files are not removed.
    The database backup jobs are running fine ; logs file do not contain any errors and once and a while you see that rman removes obsolete files.
    list expired / report obsolete do not return any files.
    thanks for the assistance
    chris
    ================= full db
    c$rman_script="backup incremental level 0 cumulative device type disk tag '%TAG' database;
    backup device type disk tag '%TAG' archivelog all not backed up delete all input;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    &br_save_agent_env();
    &br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
    my $result = &br_backup();
    exit($result);
    ================ incr db
    $rman_script="backup incremental level 1 cumulative device type disk tag '%TAG' database;
    recover copy of database;
    backup device type disk tag '%TAG' archivelog all not backed up delete all input;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    &br_save_agent_env();
    &br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
    my $result = &br_backup();
    exit($result);
    ================== rman setting
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name RHEA are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '\\is003s012\rhea\rman\%F';
    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 CHANNEL DEVICE TYPE DISK FORMAT '\\is003s012\rhea\rman\%U';
    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 BACKED UP 1 TIMES TO 'SBT_TAPE';
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFRHEA.ORA'; # default

    Chris,
    Thanks for the info; my current setting for this parameter:
    SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME;
    NAME                                 TYPE        VALUE
    control_file_record_keep_time        integer     7
    I found another thread that elaborated on this: Re: CONTROL_FILE_RECORD_KEEP_TIME vs Retention Policy in RMAN
    a) RMAN Retention Policy set to recovery window of 30 days means backups and archivelogs that you need to do a Point in Time Recovery to before 30 days do not get obsolete.
    b) CONTROLFILE_RECORD_KEEP_TIME=7 will keep (potentially, if space pressure in the controlfile) the records of these files for only 7 days
    Effect: Your old backups and archivelogs (+7 days) are no longer known by the system and will not get deleted (automatically or by delete obsolete) and your recovery area/backup location/archive destination will get filled up with old files.
    Therefore set b) > a)
    Based on this I changed the parameter:
    alter system set CONTROL_FILE_RECORD_KEEP_TIME=35 scope=both;
    Even tho the 'stale' backupsets are still invisible (still getting 'no obsolete backups found' when doing REPORT OBSOLETE), I guess that's because it will take a while (23 days?) for the CONTROL_FILE_RECORD_KEEP to catch up to the RMAN Retention Policy of 30 days)....
    Barry

  • Retention Policy and report/delete obsolete

    The database is Oracle 9i on Solaris 8 Platform.
    The backup of datafiles and archivelog files use tape and run every night.
    The backups should be held for two weeks therefore using RMAN retention policy with REPORT / DELETE OBSOLETE will be the apropiate method. Unfortunatelly somehow none of the two methods of retention policy RECOVERY WINDOW or REDUNDANCY don't seem to work. The big question is WHY?
    I configured the retention policy using:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 7
    Then ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
    I ran CROSSCHECK BACKUP with a correct output and then REPORT OBSOLETE. The report displays all existing backups - (SYSDATE-2)!
    If using RECOVERY WINDOW OF 7 DAYS then the obsolete report displays the list of backups - (SYSDATE-1).
    Somehow whatever number I use (7/9/5)in any of the retention policy the result is identical with the one above!

    Really I do not know if there is a limitation regarding that aspect if you take the backups in tapes directly. I have implanted and I have seen it function well when backups are store directly in disk.
    Find out here if that is a limitation.
    Recovery Manager Quick Reference Contents / Search / / PDF
    Recovery Manager Reference Contents / Search / Index / PDF
    Recovery Manager User's Guide Contents / Search / Index / PDF
    http://otn.oracle.com/pls/db92/db92.docindex?remark=homepage
    Joel P�rez

  • Purpose of Retention Policy Recovery Window and Redundancy

    Hi,
    Good Evening,
    I have some queries regarding the RMAN Retention Policy Recovery Window and Redundancy.
    1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
    2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
    3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
    4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
    Thanks in advance.
    Vijay.

    Hi,
    Take a look of the above doc contents:
    Configuring the Backup Retention Policy
    As explained in "Backup Retention Policies", the backup retention policy specifies which backups must be retained to meet your data recovery requirements. This policy can be based on a recovery window or redundancy. Use the CONFIGURE RETENTION POLICY command to specify the retention policy.
    so  you have option to choose either  recovery windows or redundancy based you can set the configuration like
    read in the Doc What it said for both:
    Recovery Window-Based Retention Policy ==>RMAN does not consider any full or level 0 incremental backup as obsolete if it falls within the recovery window.  Additionally, RMAN retains all archived logs and level 1 incremental backups that are needed to recover to a random point within the window.
    Redundancy-Based Retention Policy==>The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many full or level 0 backups of each datafile and control file that RMAN should keep. If the number of full or level 0 backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete. The default retention policy is REDUNDANCY 1.
    RMAN> show RETENTION POLICY;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name DDTEST are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    new RMAN configuration parameters are successfully stored
    RMAN> show RETENTION POLICY;
    RMAN configuration parameters for database with db_unique_name DDTEST are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters are successfully stored
    RMAN> show RETENTION POLICY;
    RMAN configuration parameters for database with db_unique_name DDTEST are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONTROL_FILE_RECORD_KEEP_TIME:This parameter applies only to records in the control file that are circularly reusable (such as archive log records and various backup records) ref Doc:CONTROL_FILE_RECORD_KEEP_TIME
    1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
    2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
    3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
    4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
    so i believe you can get the Answer from Your Question from Above details.
    HTH

  • Applying retention Policy tags to inbox in Exchange Server 2010

    I configured a Journal inbox in Exchange server 2010. I would like to configure a retention policy of 30 days so after a month all emails will be deleted from the Inbox of the Journal account. I configured the retention policy but messages
    would never get deleted.

    Hi,
    Based on the description, you created a retention policy tag, the type was Inbox, added this tag to a retention policy and then applied this policy to the journal mailbox. However, this retention policy didn't work.
    For this issue, first, I recommend you check if this tag is disabled. Besides, please check the application log to see if the Managed Folder Assistant has processed this journal mailbox. You can force the Managed Folder Assistant to apply the policy manually
    by running the Start-ManagedFolderAssistant command.
    If you have checked the above, I suggest you change the Action that retention policy tag performs to check the result.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Recovery Window-Based Retention VS Redundancy-Based Retention

    Hi Experts,
    We'd like to know your take on the use of Recovery Window-Based Retention Policy e.g.
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;against the use of Redundancy-Based Retention Policy, e.g.
    CONFIGURE RETENTION POLICY TO REDUNDANCY 7;Do you have any recommendations or preferences to which should be used? Is there a preferred method by oracle?
    We're currently setting up RMAN for a client that's using Oracle 11.1.0.7 standard edition, so is there a preference to what's better suited for the standard edition? The plan is to back up data to Disk, and this data will be then backed up to tape.
    Thanks

    REDUNDANCY 7 is 7 backups -- irrespective of the number of days.
    If you are running only 1 backup a day, you'd assume that it is equivalent to 7 days. However, if one day you run a backup twice, then the 7-day old backup becomes redundant ! If, the next day, you again run the backup twice, the 5-day old backup becomes redundant ! (Conversely, if you don't run a backup for 2 days, then even the 9 day old backup is not redundant !).
    So, be aware (or beware) that any adhoc backup runs or changes to the backup frequency would change your retention duration (and if this happens 6 months from now, the IT Manager / DBA onsite may not know that retention has changed !)
    Hemant K Chitae

  • Managed Folder Policy - Missing Emails

    We have a Managed Folders policy in place that my boss set up prior to leaving his job. However, a few users have complained that
    emails in subfolders of the Managed Folders\Retain Folder have been purged. I don't know if these are user created or system created subfolders. I was under the assumption that anything under the Retain Folder would not be deleted. Emails directly under the
    Retain folder are fine. Here is the only code I could find  that was saved when the policy was created. Is there an argument that I should be adding?  How does the retention of custom created subfolders work?
    get-mailbox -resultsize unlimited | where-object -FilterScript {$_.organizationalunit -match "exchange123.foo.com/Exchange Mailboxes/foo/foo"} | Set-Mailbox -ManagedFolderMailboxPolicy retain -ManagedFolderMailboxPolicyAllowed -Confirm:$false

    Hi,
    I suggest getting them back via database recovery.
    Since we are going to move to Office 365 and don't want to change managed folder to retention policy, please make a full back up promptly to protect data in time.
    Please double check whether the managed folder mailbox policy is configured correctly via following command:
    Get-ManagedFolderMailboxPolicy | FL
    Please check whether it has Event ID 9017 and 9018, to make sure the MRM working well.
    Please check the Managed Folder Assitant service is working well.
    Please increas the diagnostic logging level for the MRM, and then monitor the Event in the App log.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • RMAN Retention Policy - redundancy vs recovery window

    Hi All,
    I'm wondering what the most commonly used rman retention policy is, to provide point-in-time recovery. We have 2 oracle servers, one using redundancy policy (3) and the other using recovery window (2 days). I would like to standardize them but am not confident in which direction I should go in.
    I'm tempted to lean towards redundancy but wanted to pose the question to a wider, experienced audience for any things to think about/watch out for. Also, I assume the restore process would the same for either.
    Thanks in advance.

    Redundancy based retention policy means how many backups of each datafile must be retained and Recovery windows based retention policy is a period of time which starts with current time and goes backward in time upto the point of recoverability.
    Oracle suggests and its Best practice is "Recovery Window" .( I don't know the reason though)
    Two things you need to consider:
    1) You might need more space in case of "recovery window" because it depends upon the schedule of the backup. In "redundancy" , your space consumption will be same.
    2) You need to keep "recovery window" time less than the value of "control_file_Record_keep_time" so your backup records won't be overwritten in controlfile.
    We use "Recovery Window"

  • Retention Policy to start a Workflow not working in sub sites.

    HI,
    SharePoint 2010
    I have created a Retention Policy on a content type.
    It involves the stage to start a workflow.
    I have used a reusable workflow on the content type.
    The Retention Policy works on the main site collection. However the stages is show as "Invalid Retention Stage" for documents inside the sub sites.
    I wasn't able to figure out any solution for this.
    If anyone has encountered this before and managed to find a workaround, Kindly help.
    Thanks in advance.
    Regards,
    Rivin Jose

    Hi,
     Hope below links will help
    http://office.microsoft.com/en-in/sharepoint-server-help/create-and-apply-information-management-policies-HA101631505.aspx
    http://sharepoint.stackexchange.com/questions/74973/retention-policy-and-recurrence
    http://answers.flyppdevportal.com/categories/sharepoint2010/sharepoint2010setup.aspx?ID=774671f2-e987-4d63-89c3-2ef4a2143148
    Regards,
    MS

  • SharePoint Retention Policy workflow does not start

    Hi,
    Using Nintex workflows I have created a workflow and attached it to a content type and tested that it runs manually ok.  I want it to run according to a retention policy, and so I created a policy based on one of the content type's date fields to start
    my workflow automatically.  When I manually run the timer jobs I see the following error in ULS logs and the workflow does not start.  Interestingly if I amend the policy to do something simple like move the item to the recycle bin, that works fine.
    Can anyone suggest what is wrong and where I can go from here to find the issue?
    Thanks
    Error running the expiration action on item <document url> .  Error:  System.InvalidOperationException:
    The workflow with id=<workflow id > is no longer available.    
     at Microsoft.Office.RecordsManagement.PolicyFeatures.WorkflowExpirationAction.RunExpirationWithPostActions(SPListItem
    item, XmlNode parametersData, DateTime expireDate)    
     at Microsoft.Office.RecordsManagement.PolicyFeatures.BaseExpirationAction.Microsoft.Office.RecordsManagement.PolicyFeatures.IExpirationActionWithPostActions.OnExpirationWithPostActions(SPListItem
    item, XmlNode parametersData, DateTime expireDate)    
     at Microsoft.Office.RecordsManagement.PolicyFeatures.ExpirationTask.ExpirationActionData.RunExpirationAction(SPListItem
    item, DateTime expireDate)    
     at Microsoft.Office.RecordsManagement.PolicyFeatures.ExpirationTask.<>c__DisplayClass19.<ProcessExpiredItems>b__17(SPListItem
    item)    
     at Microsoft.Office.Server.Utilities.MonitoredScopeWrapper.RunWithMonitoredScope(Action code)  
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessItem(SPListItem item, Boolean fIncludeFolderItems,
    MonitoredScopeWrapper monitoredScopeWrapper, ItemProcessor itemProcessor, ItemProcessorErrorCallout errorCallout)

    Hi,
    Based on your description, my understanding is that the Retention Policy cannot start the Nintex workflow.
    To narrow the issue scope, I recommend to check the things below:
    Create a SharePoint 2010 Reusable workflow for the same content type or 2013 list workflow and modify the Retention Policy to start this workflow, and then check how it works.
    Create Retention Policy with the Nintex workflow in another list and then compare the results.
    Thanks,
    Victoria
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Victoria Xia
    TechNet Community Support

  • Retention Policy is not auto archiving email

    Hi, I created a new Retention Policy and attached 2 Retention Tags.
    I have a mailbox that is 18 GB and i need for all items\folders to be transferred to the same folder structure in the archive.
    The archive is presently empty, i only see a deleted items folder and the retention policy is not moving emails automatically.
    The Retention Tags attached to the policy are:
    Tag Type: Personal Tag, Age Limit for Retention 365 days, Move to Archive
    and
    Tag Type: All other folders in the mailbox, Age Limit for Retention 365 days, Move to Archive
    I also tried running the start Start-ManagedFolderAssistant cmdlet.
    Any advice would be greatly appreciated.
    Thank you,

    Hi,
    For the personal tag you created as follows, and users need to apply this tag to items from Outlook side.
    Personal Tag, Age Limit for Retention 365 days, Move to Archive
    For the "All other folders in the mailbox", if you choose the option of All other folders in the mailbox, then this would be a DPT. The DPT is applied to any folder that doesn't have a Retention Tag associated with it.
    The action "Move to Archive" moves a message to the user's archive mailbox. If the mailbox user doesn't have an archive mailbox, no action is taken. So please make sure you have enabled archive on this user mailbox.
    Once a retention policy is applied to a user mailbox, then the retention policy tag for an item will appear in the header in the Reading Pane. Please check whether you can see the retention policy description when you open a message in Outlook.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Backup with retention policy to recovery window of N days

    Hello,
    I've issued command to create database incremental backup with configuration:
    run
      configure retention policy to recovery window of 14 days;
      backup incremental level 1 cumulative
        tag daily_incr_14_days
        database
      plus archivelog delete all input;
    All parameters are set to their default values and database backups goes to FRA. I've got recovery catalog connected and all RC_ views at my disposal.
    1) Is there any way to find out, what recovery window was used for backup from any command in rman or query from RC_ views or local database views (information from control file)?
    2) If I use other recovery window setting with configure command what would rman crosscheck or report commands do?
    BR
    Patrycjusz.

    TenakaKhan wrote:
    Mahir,
    thanks for answer - this means that recovery window should be used mainly for maintenance purposes (crosscheck, delete obsolete, report need backup etc.) and it's not related to actual retention period with backup pieces like 'keep until' clause for backup ... database command (this information are saved with backup as I could check in rc_backup_set view from recovery catalog)?
    Yes it is.
    Maintaining RMAN Backups and Repository&amp;nbsp;Records
    keepOption
    backup retention policy
    A user-defined policy for determining how long backups and archived logs must be retained for media recovery. You can define a retention policy in terms of backup redundancy or a recovery window.
    RMAN retains the data file backups required to satisfy the current retention policy, and any archived redo logs required for complete recovery of those data file backups.
    recovery window
    A recovery window is one type of RMAN backup retention policy, in which the DBA specifies a period of time and RMAN ensures retention of backups and archived redo logs required for point-in-time recovery to any time during the recovery window.
    The interval always ends with the current time and extends back in time for the number of days specified by the user. For example, if the retention policy is set for a recovery window of seven days, and the current time is 11:00 AM on Tuesday,
    RMAN retains the backups required to allow point-in-time recovery back to 11:00 AM on the previous Tuesday.
    Regards
    Mahir M. Quluzade

  • How To Hide Retention Policy Tag View From OWA.

    Aslam

    Hi,
    I have exactly the opposite problem. In OWA 2013 (SP1) the assigned retention policy and the expiration date is not shown. We are in coexistance with Exchange 2010. OWA 2010, Outlook 2010/2013 are showing the assigned retention policy and the expiration
    date as shown in the first messsage of this thread. Setting "MustDisplayCommentEnabled" to true does not help. Any ideas how the information can be activated?
    Best,
    Manfred

  • RMAN backups does not match its retention policy

    Hello,
    I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
    For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
    DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
    I have clear retention policy and set to 14 days again but does not seem to work.
    I would appreciate suggestion(s) regarding the strange issue.
    Thanks a lot.
    Best Regards

    John-MK wrote:
    Hello,
    I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
    For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
    DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
    I have clear retention policy and set to 14 days again but does not seem to work.
    I would appreciate suggestion(s) regarding the strange issue.
    Thanks a lot.
    Best Regards
    We would need to know what kind of backups and when they were taken.  Consider this scenario:
    retention policy of 7 days.
    Incremental level 0 backup taken on Sundays
    Incremental level 1 backups taken Mon through Sat.
    Let's say Oct 1 is a Sunday, so we take an inc-0 backup on Oct 1, and again on Oct 8.
    Now let's say we are at Oct 10.  Our 7 day retention policy dicatates that we be able to recover to any day back to Oct 3.
    The only way we can recover to Oct 3 is to begin with that inc-0 backup from Oct 1.
    All recovery begins with the last inc-0 backup prior to the point in time to be recovered.  In a normal, regularly cycling schedule of backups,  you will actually end up with backups 1 day short of being twice as old as your retention period.
    Let's take a more extreme example.  Same 7-day retention period, but after a single inc-0 backup, you don't take any more backups for 3 months.  That one single backup is still needed to enforce your recovery window, and so is not obsolete, despite the fact it is 3 months old and your recovery window is only 7 days.
    Also, you mention 'expired'.  In terms of oracle backups, 'expired' is not the same as 'obsolete'.
    "Obsolete" means 'no longer needed to enforce recovery policy'.
    "Expired" is a bit more complex.
    when a backup is taken, or an archivelog is written, a record of that is written to the repository.  when you do an rman 'crosscheck', those repository records are compared to reality -- to see if the recorded backup file or archivelog file actually exists.  Maybe someone used an OS command to delete them.  Any file found to have 'gone walkabout' have their repository records marked as 'expired'.  An rman 'delete expired' then removes those records from the repository.

  • Messaging Records Management: loss of functionality between Managed Folders and Retention Policy

    In Exchange 2007 and 2010 you can use Managed Folders with Managed Content Settings to act on messages based on when they were moved into the folder. E.g.,
    New-ManagedContentSettings -Name DeleteJunk -FolderName ManagedJunk -MessageClass * -RetentionEnabled $true -RetentionAction DeleteAndAllowRecovery -AgeLimitForRetention 30 -TriggerForRetention WhenMoved
    will delete items 30 days after they're moved into the Junk E-Mail folder designated by the Folder Name "Managed Junk".
    However, Exchange 2010 introduces Retention Policies as an alternative to Managed Folders, and Exchange 2013 drops Managed Folders entirely. With a Retention Policy, it's impossible to specify a TriggerForRetention. See http://technet.microsoft.com/en-us/library/dd335226%28v=exchg.141%29.aspx
    and note that New-RetentionPolicyTag lacks -TriggerForRetention as a parameter. If you Get-RetentionPolicyTag | fl you can still see a TriggerForRetention value, but it's "WhenDelivered" and can't be changed.
    Both http://technet.microsoft.com/en-us/library/bb430780%28v=exchg.141%29.aspx (Exchange 2010) and http://technet.microsoft.com/en-us/library/bb430780%28v=exchg.150%29.aspx (Exchange 2013) describe a rather convoluted method used to determine the age of
    a message for retention purposes, but I don't know whether to believe those pages. It seems apparent, though, that basing a message's age on WhenDelivered can easily produce undesired results.
    Consider a Retention Policy Tag placed on the Junk E-Mail folder which will perform DeleteAndAllowRecovery on items older than 30 days. A message arrives on 01/01/15 and is classified as Junk. It immediately starts aging based on the date 01/01/15. The user
    find the message, which was misclassified, and moves it to another folder. Since there's no way to set a TriggerForRetention based on WhenMoved, the message continues to age from 01/01/15. 90 days later, while the user is reviewing their mail, the user accidentally
    clicks the Junk button on the message. Because the message is more than 30 days old, it's deleted immediately.
    1) Am I correct? Or is there a way to use Retention Policies so that messages are acted on based on how long they've resided in their current folder?
    2) What do I have to do to get Microsoft to add the ability to change the TriggerForRetention on a Retention Policy Tag in Exchange 2013?
    Note, I'm not the first person to raise this issue. It's been discussed in a number of places including TechNet. Here are a few:
    http://social.technet.microsoft.com/Forums/exchange/en-US/82c01e6e-0184-4d25-b803-45a604ca0c68/retention-policy-tag-problem?forum=exchangesvrsecuremessaginglegacy
    http://www.shudnow.net/2010/04/08/exchange-2010-sp1-retention-policies/
    http://social.technet.microsoft.com/Forums/exchange/en-US/82c01e6e-0184-4d25-b803-45a604ca0c68/retention-policy-tag-problem

    By default there is no property on a message to identify a message is moved from one folder to another.Managed folder used to stamp a new property Moveddate on the message when the ContentSetting on the target folder was set to WhenMoved.
    WhenMoved functionality is not available with Retention Policy . You can raise your concern to make this functionality available by opening a ticket with support.

Maybe you are looking for