View Retention policy expiry column

Hi All
We are experimenting with Retention Policies to see if we can replace a 3rd party product.
What I would like to do is add the retention policy expiry column to my view panel in Outlook. I realize that I can see these details when I preview each email, but I'd like to see the column rather than have to open each email or run a 'expiring soon report'.
I tried adding the 'expiry' column, but I guess that's not the correct one? Does anyone know the correct column to add?

Hi,
Thanks for posting your issue to us here. I will be assisting you with this issue.
To narrow down the issue, do you mind help me with some questions below:
1. Which version Outlook are you using? Outlook 2013/2010 or older version?
2. Are you the only person who faced this issue?
3. How did you set-up your expires?
I tested from my side, I could see the expires by following steps below:
1. Open Outlook
Take Outlook 2010 and Outlook 2013 for example: Double click the message to open it in its own
window-> File-> Properties ->expires after –>fill you expire date
2. Add the expires column, you will see your expire date displayed there
Let me know, if I misunderstood anything, thank you.

Similar Messages

Retention Policy not working for OWA accounts

I have Exchange 2010 running, with 100% of users using OWA, not Outlook as their mail client.
I have one use that wants to have messages in all his folders deleted at the end of each day. Specifically, these folders are under the Inbox, but are subfolders in the Inbox, not the Inbox itself.
I set up a retention policy tag with the Tag Type "All other Folders in the Mailbox", with age limit for retention for 1 day, and the action to delete and allow recovery.
Then I applied the Retention policy just to that one users.
The next morning, all the messages from the day before were still there. Did I miss something in the setup?
Does the "1 day" retention delete messages after 24 hours of the message being there, or at the end of each day can I have it delete all the previous messages?
Does this have something to do with the fact that we are running OWA, not Outlook? I can right click on the folders and view retention policy...it just says "Use Parent Folder Policy"...nowhere can I find the parent folders policy.
Any advice would be appreciated.

Hi,
For your retention policy not working issue, we can try the following troubleshooting:
1. Please check whether it has Event ID 9017 and 9018, to make sure the MRM working well.
2. Please check the Managed Folder Assistant service is working well.
3. Please use MFCMAPI Tool to check the "PR_MESSAGE_DELIVERY_TIME" and "PR_CREATION_TIME" properties on the items that should be removed.
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
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 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

Sharepoint List Retention Policy based on Modified Date

How do I implement a Sharepoint List Retention Policy that deletes list items that haven't been modified in X days?
I've tried to create a retention policy in Sharepoint, but I only get the option to base the policy on:
Created Date
Declared Record
I need the policy to be based on Modified Date, a standard date field that appears against all lists & document libraries. Is there a configuration change I can make to cause Modified Date to appear in the list of available fields on the Retention Policy
dialog window?
Thanks.

Veda, thanks but I'm not really a hardcore C# coder.
We found more elegant solution was to create a List View which returns all records that should be deleted, based on our own custom deletion criteria, and then create an very simple SSIS Package in Visual Studio using the
Sharepoint Connectors for SSIS to delete all Sharepoint List Items returned from that List View. The Sharepoint Destination Connector has a delete operation.
This worked for us and didn't require any coding.

Retention policy configuration

Hi, I need some clarification regarding the two configuration parameter of retention policy, so please help me regarding this , I am giving my view about both the configuration
1 . CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
Explanation => This configuration ensure that there can be the maximum of three backup of copies of a data file and control file, we we take the backup for our database/ datafile/ control file for the 4th times, then our previous backup which was taken for the first time will be not be in used, it become obsolete...
suppose on the above configuration , the first backup will be obsolete after taking the database/datafile/controlfile
backup for fourth time...when we take the backup for 5th time, the process will goes as previous , the second backup that was taken earlier will become obsolete..
2.CONFIGURE RETENTION POLICY TO RECOVER WINDOW OF 5 DAYS;
Explanation = > This configuration deals basically with the time based..here the main concept is that the backup will be there of period basis. The recovery window is a period of time that begins with the current time and extend backward in time to the period of recoverability is the earliest time.
Here, the backup that was taken early will remain there unless and until the specified days does not met..
on the above configuration the backup will remain and can be in use that was taken from last five days
suppose. today is 08/11/2010, and the back up is taken then the backup can be recovered form 04th of nov..
Please show me the right path regarding my view and clear up my concept if I am wrong....
Thanks in advance

Hi,
Welcome to forums.. !!
1 . CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
Explanation => This configuration ensure that there can be the maximum of three backup of copies of a data file and control file, we we take the backup for our database/ datafile/ control file for the 4th times, then our previous backup which was taken for the first time will be not be in used, it become obsolete...
suppose on the above configuration , the first backup will be obsolete after taking the database/datafile/controlfile
backup for fourth time...when we take the backup for 5th time, the process will goes as previous , the second backup that was taken earlier will become obsolete..
2.CONFIGURE RETENTION POLICY TO RECOVER WINDOW OF 5 DAYS;
Explanation = > This configuration deals basically with the time based..here the main concept is that the backup will be there of period basis. The recovery window is a period of time that begins with the current time and extend backward in time to the period of recoverability is the earliest time.
Here, the backup that was taken early will remain there unless and until the specified days does not met..
on the above configuration the backup will remain and can be in use that was taken from last five days
suppose. today is 08/11/2010, and the back up is taken then the backup can be recovered form 04th of nov..Your understanding is correct. some times if the backups will not become obsolete, under the recovery window, when it needs for recovery.
- Pavan Kumar N

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

RETENTION POLICY TO REDUNDANCY value

Hi,
in 10g R2 on Win 2003,
we do an incremental rman backup every night excepte sunday and every sunday a full rman backup. We want to be able to restore from last 3 weeks (I mean from 21 days before, if today is 25 of feb, to be able to restore/recover from 4 of Feb). Then what should be the value of RETENTION POLICY TO REDUNDANCY of RMAN catalog ?
Many thanks.

thank you . How about this :
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/setup005.htm#sthref261
3.5.5.1 Configuring a Recovery Window-Based Retention Policy
The RECOVERY WINDOW parameter of the CONFIGURE command specifies the number of days between the current time and the earliest point of recoverability. 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.
Run the CONFIGURE RETENTION POLICY command at the RMAN prompt. This example ensures that you can recover the database to any point within the last week:
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
RMAN does not automatically delete backups rendered obsolete by the recovery window. Instead, RMAN shows them as OBSOLETE in the REPORT OBSOLETE output and in the OBSOLETE column of V$BACKUP_FILES. RMAN deletes obsolete files if you run the DELETE OBSOLETE command.
3.5.5.2 Configuring a Redundancy-Based Retention Policy
The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many backups of each datafile and control file that RMAN should keep. In other words, if the number of 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.
As you produce more backups, RMAN keeps track of which ones to retain and which are obsolete. RMAN retains all archived logs and incremental backups that are needed to recover the nonobsolete backups.
Assume that you make a backup of datafile 7 on Monday, Tuesday, Wednesday, and Thursday. You now have four backups of the datafile. If REDUNDANCY is 2, then the Monday and Tuesday backups are obsolete. If you make another backup on Friday, then the Wednesday backup becomes obsolete.
Run the CONFIGURE RETENTION POLICY command at the RMAN prompt, as in the following example:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
3.5.5.3 Showing the Current Retention Policy
RMAN> SHOW RETENTION POLICY;
see V$RMAN_CONFIGURATION

VPD Update policy at column level

Hi,
I have a table abc and I have applied a policy for update. Now the user who has no access is unable to update the table abc. Can I just restrict the user from updating a specific column ( user_id column in the table abc), rather than restricting the user from updating all columns?
Thanks.

hi,
You can use sec_relevant_cols parameter of the DBMS_RLS.ADD_POLICY procedure
begin
dbms_rls.add_policy (
object_schema => 'SCOTT',
object_name => 'EMP',
policy_name => 'VPD_TEST_POLICY',
function_schema => 'SCOTT',
policy_function => 'TEST_VPD',
statement_types => 'select, insert, update, delete',
sec_relevant_cols => 'sal,comm');
end;
you can see this doc
http://www.in-oracle.com/Oracle-DBA/DBA-I/vpd-virtual-private-database.php
or
You can also use views to enforce column-level security, showing only which columns in a table may be updated. For example, assume that you must design roles based a table where only managers may view or update the salary column of the employee table (column restriction).
1 - You can grant the end-user access to only those columns you wish to update:
grant update (col1, col2) on mytab to fred;
2 - You might create a view with only those columns that you want to allow updates, the table appears to the end-user as-if it contains only those columns. By granting access only to that view (and not the base table), you can effectively implement column-level security and restrict which columns in a table may be changed.
regards,
Edited by: dataseven on 04.Eki.2012 23:22

Mailbox Retention Policy - Tracking - Logging

we have a mbx retention policy which deleted items older than 6 months in sent items and it allows the users to receover from the recover deleted items.
This one users sent items disappered today completely except for 2 emails. Then she receovered the items from recover deleted items. Is there a way I can find when was the mbx retetnion policy fired agianst this user? Even if it was fired
its shoudl be gradual.
thanks u

you can look in event viewer on mailbox server, App logs - filter by event ID
event ID 10027 Managed Folder Assistant - statistics of MRM expiration at end of this work cycle
you will not see specific usernames there, but you can isolate this user by just applying policy on her mailbox and run MRM on demand with PS
start-managedfolderassistant -identity clientname
also you can temporarily put retention hold and run mrm to see items tagged and their status.. like expires date on top of messages
thanks

C an you display set retention policy?

Is there a way for a Outlook client to display the current applied retention policy for all items in a folder? I know it is displayed on each item, and I looked for a column to add but didn't see anything applicable.
This is a request from staff that have large mailboxes that are just starting to use MRM.
Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.

Hi,
DPTs apply to untagged mailbox items in the entire mailbox. Untagged items are mailbox items that don't already have a retention tag applied, either by inheritance from the folder in which they're located or by the user.
There is no way to list all items that have the DPT policy applied either.
Best regards,
Belinda Ma
TechNet Community Support

Can i use the retention policy without using the Flash Recovery area?

Yes ,lets see here
RMAN>list backup summary
C:\>dir *.bus
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
File Not Found
C:\>dir *.arc
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
File Not Found
RMAN> crosscheck backup
2> ;
using channel ORA_DISK_1
RMAN> list backup summary
2> ;
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
RMAN> run {
2>   allocate channel ch0 type disk;
3>   backup as compressed backupset database format
4>   'c:\rman_%s_%d_%T.bus'
5>   plus archivelog format 'c:\arch_%s_%d_%T.arc';
6>   release channel ch0;
7>   allocate channel ch1 device type disk format 'c:\arch_%s_%d_%T.arc';
8>   release channel ch1;
9>   delete force noprompt obsolete;
10>   allocate channel ch2 device type disk format 'c:\rman_%s_%d_%T.bus';
11>   release channel ch2;
12>   delete force noprompt obsolete;
13> }
released channel: ORA_DISK_1
allocated channel: ch0
channel ch0: sid=146 devtype=DISK
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=24 recid=79 stamp=652108461
input archive log thread=1 sequence=25 recid=80 stamp=652112650
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_130_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:05
Finished backup at 15-APR-08
Starting backup at 15-APR-08
channel ch0: starting compressed full datafile backupset
channel ch0: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSTEM01.DB
F
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSAUX01.DB
F
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\USERS01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\UNDOTBS01.D
BF
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\RMAN_131_ORCL1_20080415.BUS comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:45
Finished backup at 15-APR-08
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=26 recid=81 stamp=652112703
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_132_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 15-APR-08
Starting Control File and SPFILE Autobackup at 15-APR-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\AUTOBACKUP\2008_
04_15\O1_MF_S_652112718_408X3ZVJ_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 15-APR-08
released channel: ch0
allocated channel: ch1
channel ch1: sid=146 devtype=DISK
released channel: ch1
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=146 devtype=DISK
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           128    15-APR-08
Backup Piece       128    15-APR-08          C:\ARCH_130_ORCL1_20080415.ARC
Archive Log          79     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_24_408RYXDF_.ARC
Archive Log          80     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_25_408X1SCR_.ARC
deleted backup piece
backup piece handle=C:\ARCH_130_ORCL1_20080415.ARC recid=128 stamp=652112652
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\ARCHIVEL
OG\2008_04_15\O1_MF_1_24_408RYXDF_.ARC recid=79 stamp=652108461
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\ARCHIVEL
OG\2008_04_15\O1_MF_1_25_408X1SCR_.ARC recid=80 stamp=652112650
Deleted 3 objects
released channel: ORA_DISK_1
allocated channel: ch2
channel ch2: sid=146 devtype=DISK
released channel: ch2
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=146 devtype=DISK
no obsolete backups found
RMAN>
C:\>dir *.bus
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
04/15/2008 02:24 PM        96,813,056 RMAN_131_ORCL1_20080415.BUS
               1 File(s)     96,813,056 bytes
               0 Dir(s) 61,960,724,480 bytes free
C:\>dir *.arc
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
04/15/2008 02:25 PM            56,832 ARCH_132_ORCL1_20080415.ARC
               1 File(s)         56,832 bytes
               0 Dir(s) 61,960,724,480 bytes free
C:\>
RMAN> run {
2>   allocate channel ch0 type disk;
3>   backup as compressed backupset database format
4>   'c:\rman_%s_%d_%T.bus'
5>   plus archivelog format 'c:\arch_%s_%d_%T.arc';
6>   release channel ch0;
7> }
released channel: ORA_DISK_1
allocated channel: ch0
channel ch0: sid=146 devtype=DISK
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=26 recid=81 stamp=652112703
input archive log thread=1 sequence=27 recid=82 stamp=652112873
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_134_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 15-APR-08
Starting backup at 15-APR-08
channel ch0: starting compressed full datafile backupset
channel ch0: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSTEM01.DB
F
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSAUX01.DB
F
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\USERS01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\UNDOTBS01.D
BF
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\RMAN_135_ORCL1_20080415.BUS comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:45
Finished backup at 15-APR-08
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=28 recid=83 stamp=652112925
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_136_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 15-APR-08
Starting Control File and SPFILE Autobackup at 15-APR-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\AUTOBACKUP\2008_
04_15\O1_MF_S_652112928_408XBKCZ_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 15-APR-08
released channel: ch0
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           129    15-APR-08
Backup Piece       129    15-APR-08          C:\RMAN_131_ORCL1_20080415.BUS
Backup Set           130    15-APR-08
Backup Piece       130    15-APR-08          C:\ARCH_132_ORCL1_20080415.ARC
Backup Set           131    15-APR-08
Backup Piece       131    15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\AUTOBACKUP\2008_04_15\O1_MF_S_652112718_408X3ZVJ_.BKP
Backup Set           132    15-APR-08
Backup Piece       132    15-APR-08          C:\ARCH_134_ORCL1_20080415.ARC
Archive Log          81     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_26_408X3HRP_.ARC
Archive Log          82     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_27_408X8RXN_.ARC
RMAN>Note: i have archivelog which is at FRA ,it also apply there and as well yours own defined backupsets path.
Yours comments are wellcome.
http://oraware.blogspot.com/2008/04/can-i-use-retention-policy-without.htmlKhurram

Hmmm, I can't see where the confusion originates. The table near the bottom of www.apple.com/timecapsule/specs.html has one row labelled "For backup using Time Machine" and another row labelled "For AirPort Disk with a USB hard drive".
The requirement for backup via Time Machine is OS 10.5.1 or better. Time Machine is not supported in pre-Leopard (OS 10.5) nor in Windows.
The requirement for using Time Capsule as a remote disk is identified as "Mac with Mac OS X v10.4.8 or later" or "PC with Windows XP (SP2) or Windows Vista; Bonjour for Windows (included on Time Capsule CD)".
Doesn't that pretty much spell out that Time Capsule works as a network drive without the need for Time Machine?
Also Joe (the OP) never indicated any desire to use it with Windows so I'm not sure why all the discussion about Windows compatibility. ??
Also the quote posted by Henry seems pretty clear:
"Time Capsule with Time Machine in Leopard is the ideal backup solution. But that doesn’t mean Tiger, Windows XP, and Windows Vista users can’t enjoy the benefits of Time Capsule, too. Because it mounts as a wireless hard drive, Tiger and Windows users simply access Time Capsule directly from the wireless network for exchanging and storing files quickly and easily."

Performance Issue when turning on Retention Policy

Hello,
I am currently in the process of enabling retention policy for my organization. We have 18,000+ mailboxes. How much of a performance impact (if any) will it be to the end users if we were to enable retention polices for so many mailboxes at once?
We have not had retentions enabled for about 3 years and the goals to basically delete/purge anything over 15 months. I tried doing some research on this and can't seem to find any topics pertaining to this particular question.
Thanks,
Emmanuel
Emmanuel Fumero Exchange Administrator

The user impact of enabling retention on this many mailboxes at once is not your primary issue - your primary issue will be how long it will take to complete the process on all of your mailboxes so it can "just keep up" from that point onward.
I'll give you some information about our own results and let you decide how you wish to implement retention for your users.
We have 14,000+ mailboxes running on Exchange 2010, fully updated. We migrated three years ago from "another messaging platform" well known for allowing users to have huge mailboxes with little or no capability to restrict how large the
mailboxes grew - and they grew. When I started here, our average mailbox size had just popped over 2GB, and our corporate target mailbox size limit was 2GB. We had mailboxes over 30GB, and messages older than 10 years (our corporate retention policy
states no emails older than 7 years is allowed). We were tasked with implementing retention across the board, with the following settings:
Daily emails will be kept only for 60 days, and can be recovered (if necessary) for another 60 days
Working emails (things needed for projects, etc) can be kept for 2 years, and can be recovered (if necessary) for another 60 days
Messages required for legal reasons can be kept for up to 7 years, and can't be recovered if they are deleted
Messages saved for legal reasons do not count against the 2 GB mailbox size limit
Due to my previous experience implementing retention (when I was a consultant focused on Microsoft Exchange), I knew that deploying to all users at once would cause a hit on our servers (your current fear, and well founded), but I had only deployed to smaller
organizations, and never in so radical a manner - previously, size limits had been in effect, so retention was just to "maintain the status quo", rather than to hack huge amounts of stale data from the system. However, we did have huge servers
(72 GB RAM and 24CPUs, but multirole) that, early on, were not highly taxed (under 15% CPU average during the peak timeframe, and we are in only two time-zones, so all 13,000 users will connect during the 7:00-10:30 Eastern timeframe). So we determined
that we would ramp retention across the organization in the same manner that we migrated - each 1000 users would get retention enabled weekly in a phased manner.
When we started our first group, the IT group (naturally), most users kept their mailboxes relatively small - only 1.8 GB average - so retention ran from Thursday (the day we kicked off the implementation) through the weekend. However, as each subsequent
group was placed into retention, we found that the retention task was taking longer and longer. Toward the end, we had to slip some of our retention groups a day or so because retention for the previous mailboxes hadn't completed. We attribute
this to two factors - 1) the mailboxes were larger on average, and B) there were also more and more mailboxes in retention already that also had to be handled.
In the end, we took 22 weeks to fully implement retention across the organization, and the process took another two weeks to get to the point that is was "running the status quo", rather than yanking huge volumes of stale email out of mailboxes.
During implementation, our servers' performance numbers were good - still under 30% CPU - and users weren't complaining about poor performance due to that (cached mode is a godsend), but getting the process to complete was our sticking point. If
you turn on retention for all 18,000 of your mailboxes at once, you will see some server performance degradation (especially if your servers aren't as beefy as ours), but the process may never have a chance to complete across the board. Our 22 weeks
may well take over a year for your mailboxes.
HTH - you are going to need all the help you can get. (-;

Why can't I view album artwork in column view in iTunes 11

What happened to the view album artwork in column view for iTunes 11?
It used to be in the previous versions.
It's so hard to add new artwork to the music now.

Sorry, but it's not there anymore as Apple has removed it
The only thing you can do is send feedback
http://www.apple.com/feedback/itunesapp.html

Creating a view with existing GeoRaster columns and new SDO_GEOMETRY column

Hi,
In a nutshell, I already have 1 real table, which has several attributes including types such as text, numbers etc. but also a GeoRaster column. This table works great, has its metadata stored properly and is spatially indexed; no worries.
I am then creating a view based on the above mentioned table, including the GeoRaster column. This worked, no problems. However now I want the same view to also have a SDO_GEOMETRY column which explicitly stores the spatial extent for each GeoRaster. Note the original table does not have this SDO_GEOMETRY column. So, I have created a revised SQL statement to create the view, but now it dynamically adds a new column and puts the GeoRaster.spatialextents into the SDO_GEOMETRY column.
This worked, the data made it into the view, but when we try to view the SDO_GEOMETRY in a viewer, we get errors. I added a system metadata entry for the view, but this did not help. Also, it is not possible to spatially index a view so I knew that was not the problem.
I think what has happened is the SDO_GEOMETRY column is in a sort of "limbo", where because it was not contained in the original table (and indexed there) and it is not able to be indexed in a view, it cannot be manipulated/viewed/used spatially.
Here is a snippet describing the original table:
"IMAGERY_ID" NUMBER NOT NULL ENABLE,
"CAM_ANGLE_X" NUMBER,
"CAM_ANGLE_Y" NUMBER,
"CAM_ANGLE_Z" NUMBER,
"SPEED" NUMBER,
"HEADING" NUMBER,
"IMAGE_GEOR" "SDO_GEORASTER",
"ACQUISITION_TIME" TIMESTAMP (6),
"SENSOR_ID" NUMBER,
"DOWNWARD_LOOKING" CHAR(1 BYTE),
"ORG_ID" NUMBER,
"POC_ID" NUMBER,
"FILE_NAME" VARCHAR2(100 BYTE),
"CORRELATION_ID" VARCHAR2(256 BYTE),
And here is the statement I used to create the new view:
CREATE VIEW level_0_img_view (imagery_id, cam_angle_x, cam_angle_y, cam_angle_z, speed, heading, image_geor, acquisition_time, sensor_id, downward_looking, org_id, poc_id, file_name, correlation_id, geor_extents)
AS
SELECT a.imagery_id, a.cam_angle_x, a.cam_angle_y, a.cam_angle_z, a.speed, a.heading, a.image_geor, a.acquisition_time, a.sensor_id, a.downward_looking, a.org_id, a.poc_id, a.file_name, a.correlation_id, a.image_geor.spatialextent
FROM imagery a
WHERE a.file_name LIKE '%.lev0';
Note in the above statement that the "geor_extents" column is the new column added dynamically (and not in the original table). Note the new column with the SDO_GEOMETRY data is flawless, I have looked at the records in SQL developer and all the data is there.
Any ideas?
In case you're wondering, I do have reasons for: (i) wanting an explicit column with the SDO_GEOMTRY (serving via WFS), and (ii) not wanting to alter the original table to include the equivalent SDO_GEOMETRY column.
Cheers,
M.

Hi,
if you are having problems to display your view spatial columns in MapBuilder/MapViewer, you may be missing to register the view information in the metadata (name and spatial columns).
For example, lets see the following table that simulates your case:
SQL> desc pci_image;
Name Null? Type
GEORID NOT NULL NUMBER
TYPE VARCHAR2(32)
GEORASTER MDSYS.SDO_GEORASTER
-- create a view
create view pci_img_view (georid,georaster,geor_extents)
as
select a.georid,a.georaster,a.georaster.spatialextent
from pci_image a;
-- register metadata for view spatial columns (GeoRaster and geometry column)
insert into user_sdo_geom_metadata
select 'PCI_IMG_VIEW','GEORASTER.SPATIALEXTENT', diminfo, srid
from user_sdo_geom_metadata where table_name = 'PCI_IMAGE'
insert into user_sdo_geom_metadata
select 'PCI_IMG_VIEW','GEOR_EXTENTS', diminfo, srid
from user_sdo_geom_metadata where table_name = 'PCI_IMAGE'
There is no need to index the spatial columns if they have been indexed before.
Now, if you go in MapBuilder you should see the the view name in the list of geometry tables, and be able to create a theme on column GEOR_EXTENTS (select it on the combo box) and to preview it.
For the GeoRaster column, currently the view name is not shown on the list of GeoRaster tables in MapBuilder.
For GeoRaster data, MapBuilder uses the contents of metadata view user_sdo_geor_sysdata, and then it would be needed to register the view contents there. We will talk with Jeffrey to check if there is any problem in registering
view contents in this metadata view. If the view name and georaster column is registered in user_sdo_geor_sysdata,
then it should show in MapBuilder. But you can still create a GeoRaster theme for this view using a SQL command, and should be able to preview it in MapBuilder.
-- create a GeoRaster theme based on view Georaster column.
insert into user_sdo_themes values (
'PCI_IMAGE_V_GEOR',
'View of georaster column',
'PCI_IMG_VIEW',
'GEORASTER',
'<?xml version="1.0" standalone="yes"?>
<styling_rules theme_type="georaster" raster_id="1" raster_table="RDT_PCI" raster_bands="0,1,2">
</styling_rules>');
-- commit changes
commit;
Joao

View Retention policy expiry column

Similar Messages

Maybe you are looking for