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

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 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

Using Merge to Update to Insert, Update, and also deleting obsolete records

Hi all!!!
Suppose that a have the following table, called Orders:
ORDERID        STATUS      PRICE
         1          0        100
         2          0        200
         3          0        300
         4          0        350
         5          0        390 Also, there is a procedure that will generate some data on a global temporary table, called Orders_Temp. This temporary table will be used to update the Orders table.+Orders+ have a trigger that will perform different operations when a Insert, Delete or Update command is performed.
Consider that the Orders_Temp table have the following data after running a procedure that is responsible for updating orders data:
ORDERID        STATUS      PRICE
         1          1        100
         2          2        200
         3          0        300
         5          0        390
         6          0        350 As you can see, orders 1 and 2 were updated. Order 3 and 5 were untouched, order 4 was deleted and order 6 was inserted. Merge will handle the correctly handle orders 1, 2, 3, 5 and 6, even though generating a update to orders 3 and 5, that were not changed.
So, here are the questions:
1) How could I delete the order 4 from Orders, since this order was not present on the Orders_Temp? Is there a way to use the merge command to do this?
2) Is there any way to not generate a update operation for orders 3 and 5, that were not changed?
I´m using Oracle 10.2 SE.
Thanks a lot!
Regis

Hello G!
Thank you so much for your help.
Your code took only a modification:
MERGE INTO orders tgt
USING (SELECT A.*, 1 mask
          FROM orders_temp A
        UNION ALL
        SELECT A.*, 0
          FROM orders A
         WHERE NOT EXISTS
                 (SELECT 1
                    FROM orders_temp b
                   WHERE A.order_id = b.order_id)) src
    ON (tgt.order_id = src.order_id)
WHEN MATCHED
THEN
UPDATE SET tgt.status = src.status, tgt.price = src.price
     /*WHERE src.mask = 1
       AND tgt.status != src.status
       AND tgt.price != src.price*/
DELETE
     WHERE src.mask = 0
WHEN NOT MATCHED
THEN
INSERT VALUES (src.order_id, src.status, src.priceWithout doing this, the DELETE WHERE clause was never called. After reading the docs, I found why:
Specify the DELETE where_clause to clean up data in a table while populating or updating it. The only rows affected by this clause are those rows in the destination table that are updated by the merge operation. That is, the DELETE WHERE condition evaluates the updated value, not the original value that was evaluated by the UPDATE SET ... WHERE condition. If a row of the destination table meets the DELETE condition but is not included in the join defined by the ON clause, then it is not deleted. Any delete triggers defined on the target table will be activated for each row deletion.http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9016.htm
>
From what I understand, if we restrict the records on update set_clause, the delete where_clause will no be able to process because they were not touched. So, as as workaroud, I´m checking if the record was changed inside my trigger.
Thanks a lot!
Regards.
Regis

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&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

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.

Apply Retention Policy to All New Mailboxes

I have created a retention policy tag to “Delete and Allow Recovery” after 14 days of all items in the “Deleted Items” folder.
I then created a Retention Policy to apply the tag. I see using the EMS I can run a command “Get-Mailbox | Set-Mailbox –RetentionPolicy “Empty Trash” to apply to all existing mailboxes but how do I apply this to all new mailboxes as
well?
I see a posting at
http://www.proexchange.be/blogs/exchange2010/archive/2011/08/31/using-the-scripting-agent-to-automate-some-basic-housekeeping-tasks.aspx
that describes using the Scripting Agent to automate this processes but it seems overkill for my simple requirement. If I go this route does this need to be applied to each Exchange Server? Is this the only way or is there a simpler way to apply a recipient
policy to all existing and future mailboxes?
Pacerfan9

Hi,
Any updates on this issue?
If anything is unclear, please feel free to let us know.
Thanks,
Evan Liu
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

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

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

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

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

Exchange Retention Policy Tag for Voicemails - worked for UM but not for new Cisco Unity - Any ideas?

Hi All,
We're in the process of moving from Unified Messaging to Cisco Unity. In the past, I had successfully applied the following Retention Policy Tag which worked with UM:
New-RetentionPolicyTag "Voice Mail 60 Day Retention" -Type All -MessageClass voicemail -Comment "Untagged messages removed after 60 days." -RetentionEnabled $true -AgeLimitForRetention 60 -RetentionAction DeleteAndAllowRecovery
Now, with Cisco Unity, I see that the voicemails show "Expires: Never."
The Cisco voicemails differ from UM in that instead of being *.mp3 files, they are *.wav.
I cannot figure out a way to create a Retention Policy tag that deletes a specific file type. Any ideas?
Thank you,
MrMister

Hi All,
We're in the process of moving from Unified Messaging to Cisco Unity. In the past, I had successfully applied the following Retention Policy Tag which worked with UM:
New-RetentionPolicyTag "Voice Mail 60 Day Retention" -Type All -MessageClass voicemail -Comment "Untagged messages removed after 60 days." -RetentionEnabled $true -AgeLimitForRetention 60 -RetentionAction DeleteAndAllowRecovery
Now, with Cisco Unity, I see that the voicemails show "Expires: Never."
The Cisco voicemails differ from UM in that instead of being *.mp3 files, they are *.wav.
I cannot figure out a way to create a Retention Policy tag that deletes a specific file type. Any ideas?
Thank you,
MrMister
Those don't exist. The tags work on message class. The Cisco VMs are not the same forms as the Exchange UMs essentially.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Retention Policy to delete both backup sets and archivelogs automatically

I configured the Recovery Window-Based Retention Policy for my database for the window=14 days. I also set up a crontab to do a full backup every Monday. So say in a month, there will be 30 archive logs and 4 full DB backup sets.
Now that I understand if the FRA gets filled up, older archive logs that are not needed for the 14 days recoverable window will be automatically deleted. My questions is what happen to the old backup sets? Will they get deleted automatically too if there is no space left in FRA? Or I need to use "DELETE OBSOLETE" to delete them?
Thanks.

One of the advantages of the FRA is, in case of space pressure obsolete objects (obsolete due to the defined retention policy) are deleted automatically. That's true for backups and archivelogs. The objects are NOT deleted automatically after the retention policy expires, but only when additional space is needed. That does not mean you don't have to care about FRA space consumption. You may have unusual amounts of archivelogs, additional backups and flashback logs (if flashback database is configured), which fill up the FRA.
Werner

"Permanently Delete" fail in outlook client after setting up the "Archive and Retention Policy" in Exchange 2010

In Exchange 2010 server, we have setup a policy under "Default Archive and Retention Policy" as all messages under "Inbox", "Sent Items" and "Deleted Items" will be Permanently Delete after X months.
However, one of our client found that some of the email messages was still found under his "Deleted Items". All other email messages under her outlook client (2010) were successfully deleted according to the policy.
Is there any reason for this exception?
Thank you

Hi,
Based on your description, you created retention policy tags for Inbox, Sent Items and Deleted Items folders. Then you linked them to the default archive and retention policy
Default Archive and Retention Policy.
Please check if this issue affects all users.
Please create a different retention policy which is associated with these retention tags, and apply this policy to a test user to check result.
Best regards,
Belinda Ma
TechNet Community Support

Retention Policy and report/delete obsolete

Similar Messages

Maybe you are looking for