Policy on Trash Retention.

I'm having a battle with upper management in respects to the Trash folder.
Currently, we are using Retain to archive emails including the Trash folder.
My argument is that the Trash folder should not be archived and a policy should be in place, and set in GroupWise, to limit the number of days items are kept in the Trash folder.
Of course, if everyone used the Trash folder for what it was intended for, this wouldn't be an issue.
I made the point, "If you through something out in the garbage and your trash can is emptied every week, what is your expectation on getting that item back?"
I bring up the cost of archiving trash in respects to the additional time it takes to archive, the amount of disk space, etc., but I still can't convince them otherwise.
Now, they want to know what the policy is for other companies.
So, here I am begging for information.
If you could answer the following questions, perhaps it will help convince the "powers-to-be" to devise a policy!
1. Does the company you work for archive everyone's Mailbox Trash folder?
2. If they do, what is the thought process behind that decision?
3. Do you have GroupWise set to automatically purge the Trash folder, and if you do, what is that number?
Thanks for your time and input!
Stan

In article <[email protected]>, Demaximis wrote:
> I'm having a battle with upper management in respects to the Trash
> folder.
Sadly that is far too common a battle
> My argument is that the Trash folder should not be archived and a policy
> should be in place,
It all comes down to why are you archiving mail. It usually involves legal
reasons, and to ensure full chain of evidence all mail has to be kept,
especially the messages that someone thought were trouble and threw them
in the trash as soon as they arrived.
Retain will show that this has happened, conversely if Retain is having a
problem and you properly have GW set to not purge until archived (and
backed up) you get to see it by growing trashbins
Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
http://forums.novell.com/member.php?userid=75037
If you find a post helpful, please show your appreciation by clicking on
the star below.

Similar Messages

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

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

RMAN -Retention policy doubt

Hi,
I have doubt on RMAN retention policy.
we are taking daily cumulative backup and weekly Full database backup.
And our retention policy is "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS"
My assumption is that RECOVERY window of 3 days will hold the backups of 3 days and delete the previous backups,since we are taking cumulative backups,and using them database can be recovered.
we used below commands to take cumulative backup.
backup incremental level 1 cumulative as COMPRESSED BACKUPSET tag '%TAG' database include current controlfile;
backup as COMPRESSED BACKUPSET tag '%TAG' archivelog all not backed up;
Regards,
mannu

Thanks for reply.
A recovery window is a period of time that begins with the current time and extends backward in time to the point of recoverability. The point of recoverability is the earliest time for a hypothetical point-in-time recovery, that is, the earliest point to which you can recover following a media failure. For example, if you implement a recovery window of one week, then this window of time must extend back exactly seven days from the present so that you can restore a backup and recover it to this point. You implement this retention policy as follows:
In our case:
Jan 24---Level 0 Full backup
Jan 25-Cumulative backup
Jan 26-Cumulative backup
Jan 27--->Cumulative backup
Jan-28 ----->cumulative backup
What would be my point of recoverability? How my recovery window period of 3 days work here.
Regards,
Mannu

Retention Policy Tag on Outlook 2010/Exchange 2010 SP3

While I still wanted to have the Retention Policies and Tags applied to mailboxes, would I just be able to "HIDE" or "SUPPRESS" the Tip that the Outlook 2010 client shows on the read-pane like...
Retention Policy: xx Days Retention Inbox (xx days) Expires x/x/xxxx ??
Please suggest
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. Regards, Siva

Hi,
When a retention policy is applied to an item in user's mailbox, the retention policy for a message appears in the header in the Reading Pane under the recipient names and includes the expiration date. If no retention policy is applied, no information appears
under the message recipient names.
Based on my knowledge, I'm afraid there is no way to hide it in the Reading Pane.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Why are my deleted emails only staying in the trash folder for a month? How can I find older deleted emails?

my trash folder is only showing emails back to April 28th.

Does the account use POP, or IMAP?
If IMAP, your Trash folder is almost certainly on the server and as such, may be subject to the email provider's policy on trash/deleted folders.
Check what your provider's rules are on trash retention. You may be permitted to adjust the period for which they are held. Alternatively you can set Thunderbird to use a trash folder under your Local Folders account which will be on your own hard disk and thus invisible to your email provider.
And of course check the settings in Thunderbird for what to do with deleted messages. You can set it to automatically remove messages after a defined period. Look under Tools|Account Settings for deletion settings.
OTOH, if you're routinely deleting messages and relying on them being kept indefinitely, I'd suggest you rethink your procedure and not delete them until you're confident you no longer need them. Recycle bins, waste bins and the like are the first to go when disk space gets tight. Most email providers have a policy of automatically removing messages over a certain age from the Deleted folder, specifically to manage and reduce disk space usage.

NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES

제품 : RMAN
작성날짜 : 2004-05-20
NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES
=======================================================
오라클 9i RMAN 에서는 백업을 보다 효율적으로 할 수 있는 기능을 보강 했다.
지금 소개할 "Retention Policies" 기능을 통해서 보다 효율적인 RMAN 백업
전략을 세울 수 있다.
1. 백업 화일 최적화 방법 (Backup File Optimization)
백업 화일 최적화란 백업에 소요되는 공간을 최소화 하는 전략이다. RMAN
백업시에 같은 정보 (dbid, checkpoint, and resetlogs data 등등) 를 가지고 있는
화일이 이미 존재하는 백업 셋 내부에 있는지 체크하게 된다. 만일 같은 화일이
이미 백업 되어 있다면 BACK UP 명령은 해당 화일에 대해서는 백업을 하지 않게
된다.
이때 같은 화일이라고 판단하는 기준은 다음과 같다.
* Datafile: 같은 DBID, checkpoint SCN, resetlogs SCN 과 time. 데이타 화일은
반드시정상적으로 offline 되었거나, read-only 이거나, 또는 정상적 으로 close
되어야 함.
* Archived redo log: 같은 thread, sequence number, 그리고 같은 Resetlogs
SCN 과 time.
* Backup Set: 같은 Backup Set recid 와 stamp.
RMAN 이 백업을 수행하다가 위와 같은 조건의 화일이 이미 존재함을 확인하면
이것은 건너뛰게 될 화일의 대상이다. 하지만 이때 바로 Skip 을 결정하지 않고
정해진 Retention Policies 를 조사 한후에 Skip 여부를 결정 하게 된다.
만일 백업 명령에 DELETE INPUT option 이 사용되면 RMAN 은 백업이 Skip
되어도 화일을 지우게 된다.
RMAN 은 모든 화일에 대한 백업이 Skip 되어도 에러메시지나 경고를 보내지
않는다.
그러나 만일 데이터 화일에 대한 백업이 recovery policy window 보다 오래
된 것 이면 RMAN 은 새로운 백업 화일을 만들기 위해서 화일을 백업 하게 된다.
Note:
자체적인 expirations policy 를 가지고 있는 media manager 를 사용할 경우에는
이런 백업 최적화 정책을 사용하는 것에 신중을 기해야 한다.
백업 최적화 를 사용하기 위해서는 CONFIGURE 명령을 사용한다. CONFIGURE
명령은 명령 수행 이후에 이루어지는 모든 백업에 대해 적용이 된다.
예:
CONFIGURE BACKUP OPTIMIZATION ON; # default 는 OFF
2. Backup Optimization에 Retention Policies 적용 하기
Retention Policy 로 백업 최적화를 조절 할 수 있다. 그러나 retention policy를
사용하지 않기 위해서는 'CONFIGURE RETENTION POLICY TO NONE' 을
이용해서 명시적으로 retention policy를 사용하지 않는다고 해야 한다. 디폴트로
REDUNDANCY = 1 이 적용 된다.
a. Recovery Window 를 이용한 Backup Optimization
만일 백업 최적화가 enable 되어 있고 Recovery Window 가 retention policy
적용을 위해서 셋업 되어 있으면 RMAN 은 항상 가장 최근의 백업이 Recovery
Window 보다 오래된 데이터 화일을 백업한다.
예를 들면 다음과 같은 조건에서
o Today is February 21.
o The recovery window is 7 days.
o The most recent backup of tablespace tbs2 to tape is January 3.
o Tablespace tbs2 is read-only.
2월 21일에 tbs2 테이블 스페이스를 테이프로 백업을 하라는 명령을 내리면,
RMAN 은 이 화일이 1월3일 이후에 변경 사항이 없는데도 불구 하고 백업을 하게
된다. 이로써 RMAN 은 최근 7일 동안에 최소한 한번의 백업이 있어야 된다는
조건을 지키게 된다.
이러한 작동 방식은 media manager 가 오래된 테잎을 제거 해도 되도록 한다.
그렇지 않다면, media manager 는 1월 3일의 백업을 무한정 가지고 있게 된다.
2월 21일에 tbs2 테이블 스페이스의 보다 최근의 백업을 만듦으로 써, RMAN 은
media manager 가 1월 3일에 백업 했던 테입을 지워도 되도록 한다.
b. Redundancy 를 이용한 Backup Optimization
Retention policy 로 Redundancy 를 채택 한 경우에 RMAN 은 Redundancy
에 1을 더한 갯수를 초과하는 오프라인 또는 읽기 전용 화일의 백업을 건너뛴다.
이때 'CONFIGURE RETENTION POLICY TO REDUNDANCY n' 명령어로
Redundancy의 갯수를 정한다.
아래와 같은 백업 최적화 명령을 내린 경우를 예로 든다:
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
아카이브 테이블스페이스를 한번도 백업을 받은적이 없고 다음의 작업을 1주일
동안 한다고 하자.
Day Action Result Redundant Backup
Monday Take tablespace archive offline clean.
Tuesday Run BACKUP DATABASE. The archive tablespace is backed up.
Wednesday Run BACKUP DATABASE. The archive tablespace is backed up.
Thursday Run BACKUP DATABASE. The archive tablespace is backed up. Tuesday backup.
Friday Run BACKUP DATABASE. n/a Tuesday backup.
Saturday Run BACKUP DATABASE. n/a Tuesday backup.
Sunday Run DELETE OBSOLETE. The Tuesday backup is deleted.
Monday Run BACKUP DATABASE. The archive tablespace is backed up. Wednesday backup.
화요일, 수요일, 그리고 목요일의 백업은 아카이브 테이블 스페이스를 복사 해서
3개의 백업이 반드시 존재 해야 한다는 조건을 충촉 시킨다. (1+Redundancy)
금요일과 토요일에는 백업 최적화 조건에 의해서 아카이브 테이블 스페이스를
복사하지 않게 된다.
RMAN 은 일요일에는 유효기간이 지난 백업 화일을 지우게 된다. 따라서 화요일에
만든 백업은 삭제 된다. 월요일의 전체 백업은 3개의 백업이 존재 해야 한다는 조건
때문에 아카이브 테이블 스페이스를 또 다시 백업하게 된다. 이런 방식으로 백업
사이클이 진행 된다.
3. RETENTION POLICY NONE vs. DEFAULT
주의 사항:
'CONFIGURE RETENTION POLICY TO NONE' 과 'CONFIGURE RETENTION
POLICY TO DEFAULT' 는 그 의미가 같지 않다. 전자는 RETENTION POLICY
자체가 존재 하지 않는다는 의미 이며 백업은 expire 되지 않으며 'DELETE
OBSOLETE' 명령은 사용 할 수 없게 된다. 후자는 디폴트 RETENTION POLICY
(REDUNDANCY 1) 를 사용하게 된다는 의미 이다.
'DELETE OBSOLETE' 명령은 RETENTION POLICY 기준으로 expire 된 백업을
제거 하라는 명령이다.
보다 자세한 내용은 Oracle9i Recovery Manager User's Guide and
Reference의 Backup Optimization 부분을 참고 하시기 바랍니다.
--------------THE END----------------------------------------------

Hi,
Backup optimisation = +- do not copy empty space.
So, when you issue your BACKUP statement, it backs up the datafile. dot. nothing more.
In order to achieve what you're testing, look into TFM for BACKUP INCREMENTAL LEVEL x .
Regards,
Yoann.

RMAN-08591: WARNING: invalid archived log deletion policy

Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,

kkrm333 wrote:
Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,
bcm@bcm-laptop:~$ oerr rman 8591
8591, 3, "WARNING: invalid archived log deletion policy"
// *Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived
//         log deletion policy was APPLIED but there was no mandatory
//         archived log destinations.
// *Action: One of the following:
//          1) Change archived log deletion policy using CONFIGURE command
//          2) Make one or more of standby destination as MANDATORY.

Items are not moved to the deleted items folder when they expire

Hey
I have Exchange 2010 Server (Version: 14.01.0438.000) and configured a retention policy with one retention tag for the
inbox that moves items after 365 days to the deleted items folder. I have assigned this policy to one Mailbox to see if it works. It doesn't. :)
All Items are "stamped" correctly with a expiry date. And the Messages show now "This item is expired" for example:
I made the Policy a week ago and waited to see if the items will be moved but nothing happen until today. The Application Log shows no errors or warnings. I already used "Start-ManagedFolderAssistant"
multiple times....
what is wrong here? And how do i track the problem down?
i also checked all the other threads regarding the same or alike issues. But couldn't find anything that would halp me.

Get-RetentionPolicyTag
Get-RetentionPolicyTag:
RunspaceId : bab19777-67ac-4a28-a895-19f89113122a
MessageClassDisplayName : All Mailbox Content
MessageClass : *
Description : Managed Content Settings
RetentionEnabled : True
RetentionAction : MoveToDeletedItems
AgeLimitForRetention : 365.00:00:00
MoveToDestinationFolder :
TriggerForRetention : WhenDelivered
MessageFormatForJournaling : UseTnef
JournalingEnabled : False
AddressForJournaling :
LabelForJournaling :
Type : Inbox
SystemTag : False
LocalizedRetentionPolicyTagName : {}
Comment :
RetentionId : 6c115c72-8186-4828-b801-d434d7fdbcc7
LocalizedComment : {}
MustDisplayCommentEnabled : False
LegacyManagedFolder :
AdminDisplayName :
ExchangeVersion : 1.0 (0.0.0.0)
Name : Delete after 1 year (Inbox)
DistinguishedName : CN=Delete after 1 year (Inbox),CN=Retention Policy Tag Container,CN=****
AG,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=****,DC=*****
Identity : Delete after 1 year (Inbox)
Guid : 6c115c72-8186-4828-b801-d434d7fdbcc7
ObjectCategory : *****/Configuration/Schema/ms-Exch-ELC-Folder
ObjectClass : {top, msExchELCFolder}
WhenChanged : 07.10.2014 10:16:04
WhenCreated : 07.10.2014 10:16:04
WhenChangedUTC : 07.10.2014 08:16:04
WhenCreatedUTC : 07.10.2014 08:16:04
OrganizationId :
OriginatingServer : srv-********
IsValid : True
Get-RetentionPolicy:
RunspaceId : bab19777-67ac-4a28-a895-19f89113122a
RetentionId : a83b8845-5f3b-422c-84a1-8eef8a8b2bd2
RetentionPolicyTagLinks : {Delete after 1 year (Inbox)}
AdminDisplayName :
ExchangeVersion : 1.0 (0.0.0.0)
Name : Funds@
DistinguishedName : CN=Funds@,CN=Retention Policies Container,CN=*****,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=***,DC=****
Identity : Funds@
Guid : a83b8845-5f3b-422c-84a1-8eef8a8b2bd2
ObjectCategory : hnw.dom/Configuration/Schema/ms-Exch-Mailbox-Recipient-Template
ObjectClass : {top, msExchRecipientTemplate, msExchMailboxRecipientTemplate}
WhenChanged : 07.10.2014 10:28:26
WhenCreated : 07.10.2014 10:28:26
WhenChangedUTC : 07.10.2014 08:28:26
WhenCreatedUTC : 07.10.2014 08:28:26
OrganizationId :
OriginatingServer : srv-******
IsValid : True
I just replaced some "critical information" with *****
Also the Policy is defently applied. I checked with:
Get-Mailbox -ResultSize unlimited | Format-Table Name,RetentionPolicy -Auto

Delete messages older than a date except personal folder

Hello everyone,
I have been spending a lot of time searching and testing how to delete all items older than 6 months in a user mailbox, but this rule it cannot be applied just one personal folder named "personal". I have been reading about retention policy and
retention policy tags, but I can't figure out how to use that to keep all items older than 6 month in personal folder.
could anyone tell me if I am right with retention policy or it's better other way?
thank you in advice

Hi,
In Outlook client, we can set AutoArchive for all folders to delete all items older than 6 months except for “Personal” folder one by one.
If you want to use retention policy in Exchange side, we can use retention tags and retention policies to have a try. there are three types of retention tags:
Default policy tag (DPT), Retention policy tag (RPT), Personal tag.
For your scenario, we can create a personal tag applied for this Personal folder. For example,
delete messages older than 3 years for this personal folder. Then apply this personal tag for Personal folder in Outlook. And the Personal folder items are all tagged. After that, we can
applying default policy tags (DPTs) to mailboxes to manage the retention of all untagged items.
Personal suggestion, since the delete action is only used for one specific mailbox, I suggest we can use AutoArchive in Outlook side to achieve it.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support
Hi Winnie Liang,
Thank you for answer. I would like to do all tasks from exchange side, so I know how to apply a retention policy to a mailbox for deleting all older than 6 months. But how can I apply the personal policy tag to a personal folder's users?
All involved users in this requirement are warned that they must let all personal messages in "personal" folder named "personal".
regards

How to put all RMAN-files in one backupset?? (so preventing RMAN-06023)

((Please see also this thread: Re: Restoring Database causes ORA-19612
How can I manage that ALL files, ALL pieces, Controlfile, SPfile etc. etc. is available in ONE backup-file.
When I do "Backup Database" and I copy the created files to another location: restoring the database keeps asking for older backuppieces.
(Rman-error: RMAN-06023: no backup or copy of datafile 1 found to restore"
When i type on the target:
RMAN> list backup of datafile 1;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
12 Full 70.03G DISK 00:44:49 02-APR-12
BP Key: 12 Status: EXPIRED Compressed: NO Tag: TAG20120402T213111
Piece Name: G:\RMANBACKUP\0KN7EQSV_1_1
List of Datafiles in backup set 12
File LV Type Ckp SCN Ckp Time Name
1 Full 2945781693 02-APR-12 D:\ORACLEDATA\CISORA1\SYSTEM01.DBF
RMAN>
I see that the Missing file is in a backupset of 1 day ago. That's NOT what i want. I want EVERY DAY a FULL backupset.
please advise how to achive.
thanks
Edited by: AvRossem on 3-apr-2012 5:36

AvRossem wrote:
((Please see also this thread: Re: Restoring Database causes ORA-19612
How can I manage that ALL files, ALL pieces, Controlfile, SPfile etc. etc. is available in ONE backup-file.
When I do "Backup Database" and I copy the created files to another location: restoring the database keeps asking for older backuppieces.
(Rman-error: RMAN-06023: no backup or copy of datafile 1 found to restore"
When i type on the target:
RMAN> list backup of datafile 1;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
12 Full 70.03G DISK 00:44:49 02-APR-12
BP Key: 12 Status: EXPIRED Compressed: NO Tag: TAG20120402T213111
Piece Name: G:\RMANBACKUP\0KN7EQSV_1_1
List of Datafiles in backup set 12
File LV Type Ckp SCN Ckp Time Name
1 Full 2945781693 02-APR-12 D:\ORACLEDATA\CISORA1\SYSTEM01.DBF
RMAN>
I see that the Missing file is in a backupset of 1 day ago. That's NOT what i want. I want EVERY DAY a FULL backupset.
please advise how to achive.
thanks
Hi,
How can I manage that ALL files, ALL pieces, Controlfile, SPfile etc. etc. is available in ONE backup-file.The short awnser is: You cannot do that.
RMAN divides some files types in different backupset.
This is a rule:
Datafiles use your own Backupset
Controlfile and SPFILE use your own Backupset
ARCHIVELOG use your own Backupset
For each BACKUPSET you can have many Backuppiece (i.e files on disk). As rule you always have relationship of one (Backupset) to one or more (Backuppiece).
So, respecting the rule above you can do following:
You can use the option FILESPERSET to keep all datafiles in same backuppiece. (In my case below 200 datafiles will be in same backuppiece)
{code}
RMAN> backup database tag='my_backup' filesperset 200 include current controlfile ;
Starting backup at 03-APR-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/dbrcv/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/dbrcv/sysaux01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/dbrcv/undotbs01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/dbrcv/users01.dbf
channel ORA_DISK_1: starting piece 1 at 03-APR-12
channel ORA_DISK_1: finished piece 1 at 03-APR-12
piece handle=/u01/app/oracle/fast_recovery_area/DBRCV/backupset/2012_04_03/o1_mf_nnndf_MY_BACKUP_7qppmnn7_.bkp tag=MY_BACKUP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 03-APR-12
channel ORA_DISK_1: finished piece 1 at 03-APR-12
piece handle=/u01/app/oracle/fast_recovery_area/DBRCV/backupset/2012_04_03/o1_mf_ncsnf_MY_BACKUP_7qppo4ls_.bkp tag=MY_BACKUP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 03-APR-12
RMAN> backup archivelog all filesperset 200 ;
Starting backup at 03-APR-12
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=16 RECID=1 STAMP=779332254
input archived log thread=1 sequence=17 RECID=2 STAMP=779374813
input archived log thread=1 sequence=18 RECID=3 STAMP=779393222
input archived log thread=1 sequence=19 RECID=4 STAMP=779436085
input archived log thread=1 sequence=20 RECID=5 STAMP=779472067
input archived log thread=1 sequence=21 RECID=6 STAMP=779511653
input archived log thread=1 sequence=22 RECID=7 STAMP=779580131
input archived log thread=1 sequence=23 RECID=8 STAMP=779648029
input archived log thread=1 sequence=24 RECID=9 STAMP=779649107
input archived log thread=1 sequence=25 RECID=10 STAMP=779649189
input archived log thread=1 sequence=26 RECID=11 STAMP=779649436
channel ORA_DISK_1: starting piece 1 at 03-APR-12
channel ORA_DISK_1: finished piece 1 at 03-APR-12
piece handle=/u01/app/oracle/fast_recovery_area/DBRCV/backupset/2012_04_03/o1_mf_annnn_TAG20120403T171718_7qppphtb_.bkp tag=TAG20120403T171718 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:35
Finished backup at 03-APR-12
{code}
Now I have 3 files:
{code}
RMAN > List BACKUSET;
BS Key Type LV Size Device Type Elapsed Time Completion Time
447 Full 314.02M DISK 00:00:37 03-APR-12
BP Key: 450 Status: AVAILABLE Compressed: NO Tag: MY_BACKUP
Piece Name: /u01/app/oracle/fast_recovery_area/DBRCV/backupset/2012_04_03/o1_mf_nnndf_MY_BACKUP_7qppmnn7_.bkp
List of Datafiles in backup set 447
File LV Type Ckp SCN Ckp Time Name
1 Full 444127 03-APR-12 /u01/app/oracle/oradata/dbrcv/system01.dbf
2 Full 444127 03-APR-12 /u01/app/oracle/oradata/dbrcv/sysaux01.dbf
3 Full 444127 03-APR-12 /u01/app/oracle/oradata/dbrcv/undotbs01.dbf
4 Full 444127 03-APR-12 /u01/app/oracle/oradata/dbrcv/users01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
448 Full 9.36M DISK 00:00:04 03-APR-12
BP Key: 451 Status: AVAILABLE Compressed: NO Tag: MY_BACKUP
Piece Name: /u01/app/oracle/fast_recovery_area/DBRCV/backupset/2012_04_03/o1_mf_ncsnf_MY_BACKUP_7qppo4ls_.bkp
SPFILE Included: Modification time: 03-APR-12
SPFILE db_unique_name: DBRCV
Control File Included: Ckp SCN: 444147 Ckp time: 03-APR-12
BS Key Size Device Type Elapsed Time Completion Time
492 300.38M DISK 00:00:26 03-APR-12
BP Key: 495 Status: AVAILABLE Compressed: NO Tag: TAG20120403T171718
Piece Name: /u01/app/oracle/fast_recovery_area/DBRCV/backupset/2012_04_03/o1_mf_annnn_TAG20120403T171718_7qppphtb_.bkp
List of Archived Logs in backup set 492
Thrd Seq Low SCN Low Time Next SCN Next Time
1 16 234488 30-MAR-12 261258 31-MAR-12
1 17 261258 31-MAR-12 286957 31-MAR-12
1 18 286957 31-MAR-12 303448 31-MAR-12
1 19 303448 31-MAR-12 329357 01-APR-12
1 20 329357 01-APR-12 351967 01-APR-12
1 21 351967 01-APR-12 375454 02-APR-12
1 22 375454 02-APR-12 409423 02-APR-12
1 23 409423 02-APR-12 443037 03-APR-12
1 24 443037 03-APR-12 443868 03-APR-12
1 25 443868 03-APR-12 443928 03-APR-12
1 26 443928 03-APR-12 444188 03-APR-12
{code}
See it:
BackupSet :
447 = Datafiles
448 = Controfile and SPFILE
492 = Archivelogs
Now I want create a copy of these backupset to offsite purpose:
{code}
RMAN> backup backupset 447,448,492 tag='my_backup_offsite' format '/u01/app/offsite/%U';
Starting backup at 03-APR-12
using channel ORA_DISK_1
channel ORA_DISK_1: input backup set: count=17, stamp=779649348, piece=1
channel ORA_DISK_1: starting piece 1 at 03-APR-12
channel ORA_DISK_1: backup piece /u01/app/offsite/0hn7h0a4_1_2
piece handle=/u01/app/offsite/0hn7h0a4_1_3 comment=NONE
channel ORA_DISK_1: finished piece 1 at 03-APR-12
channel ORA_DISK_1: backup piece complete, elapsed time: 00:00:25
channel ORA_DISK_1: input backup set: count=18, stamp=779649393, piece=1
channel ORA_DISK_1: starting piece 1 at 03-APR-12
channel ORA_DISK_1: backup piece /u01/app/offsite/0in7h0bh_1_2
piece handle=/u01/app/offsite/0in7h0bh_1_3 comment=NONE
channel ORA_DISK_1: finished piece 1 at 03-APR-12
channel ORA_DISK_1: backup piece complete, elapsed time: 00:00:03
channel ORA_DISK_1: input backup set: count=19, stamp=779649439, piece=1
channel ORA_DISK_1: starting piece 1 at 03-APR-12
channel ORA_DISK_1: backup piece /u01/app/offsite/0jn7h0cv_1_2
piece handle=/u01/app/offsite/0jn7h0cv_1_3 comment=NONE
channel ORA_DISK_1: finished piece 1 at 03-APR-12
channel ORA_DISK_1: backup piece complete, elapsed time: 00:00:45
Finished backup at 03-APR-12
RMAN> list backupset tag='my_backup_offsite';
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
447 Full 314.02M DISK 00:00:37 03-APR-12
BP Key: 624 Status: AVAILABLE Compressed: NO Tag: MY_BACKUP_OFFSITE
Piece Name: /u01/app/offsite/0hn7h0a4_1_3
List of Datafiles in backup set 447
File LV Type Ckp SCN Ckp Time Name
1 Full 444127 03-APR-12 /u01/app/oracle/oradata/dbrcv/system01.dbf
2 Full 444127 03-APR-12 /u01/app/oracle/oradata/dbrcv/sysaux01.dbf
3 Full 444127 03-APR-12 /u01/app/oracle/oradata/dbrcv/undotbs01.dbf
4 Full 444127 03-APR-12 /u01/app/oracle/oradata/dbrcv/users01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
448 Full 9.36M DISK 00:00:04 03-APR-12
BP Key: 625 Status: AVAILABLE Compressed: NO Tag: MY_BACKUP_OFFSITE
Piece Name: /u01/app/offsite/0in7h0bh_1_3
SPFILE Included: Modification time: 03-APR-12
SPFILE db_unique_name: DBRCV
Control File Included: Ckp SCN: 444147 Ckp time: 03-APR-12
BS Key Size Device Type Elapsed Time Completion Time
492 300.38M DISK 00:00:26 03-APR-12
BP Key: 626 Status: AVAILABLE Compressed: NO Tag: MY_BACKUP_OFFSITE
Piece Name: /u01/app/offsite/0jn7h0cv_1_3
List of Archived Logs in backup set 492
Thrd Seq Low SCN Low Time Next SCN Next Time
1 16 234488 30-MAR-12 261258 31-MAR-12
1 17 261258 31-MAR-12 286957 31-MAR-12
1 18 286957 31-MAR-12 303448 31-MAR-12
1 19 303448 31-MAR-12 329357 01-APR-12
1 20 329357 01-APR-12 351967 01-APR-12
1 21 351967 01-APR-12 375454 02-APR-12
1 22 375454 02-APR-12 409423 02-APR-12
1 23 409423 02-APR-12 443037 03-APR-12
1 24 443037 03-APR-12 443868 03-APR-12
1 25 443868 03-APR-12 443928 03-APR-12
1 26 443928 03-APR-12 444188 03-APR-12
RMAN>
{code}
When you perform restore you can use the tag='my_backup_offsite'.
This files belong a same policy of "configure retention policy ... " of RMAN. So, this files will be obsolete when it is out the policy.
Hope this helps,
Levi Pereira

I have set the Message History setting to delete messages after 30 days. Since doing this, Messages app is quite buggy.

I have no need to keep huge, old Messages conversations, so I recently set the Message History to delete messages after 30 days. Since doing this, however, I have noticed that the Messages app has become fairly buggy. Sometimes I'll open the app and it will look like there's no conversations, and the app prompts me to send a new message. Sometimes, I'll open the app to reply to an incoming message and my response will hang at 90% sent and then when I go back to the conversation list, it displays my outgoing, as-yet-unsent response as a new message, complete with little blue new message marker. The only way I have found to temporarily resolve these issues is to restart the phone. What's going on here?

Hi,
According to your description, I understand that you need to apply a rule to delete messages older than 30 days for all mailboxes in your environment. Is it right? If I misunderstand, please point it out.
As all above suggestions, we can use retention tags and retention policies in Exchange 2013 to achieve it. To apply it, we can try the following steps:
1. Login to Exchange Admin Center(EAC) in Exchange 2013 as an administrator.
2. Click compliance management > retention tags.
3. Click New Tag > applied automatically to entire mailbox(default).
4. Edit the Name, Retention action and Retention period(30 days), then
Save it.
5. Click Retention Policies tab > New.
6. Edit Name and add the Retention tags you created a moment ago. And
Save it.
7. Navigate to Recipients > Mailboxes.
8. In the list view, use the Shift or Ctrl keys to select multiple mailboxes.
9. In the details pane, click More options.
10. Under Retention Policy, click Update.
11. In Bulk Assign Retention Policy, select the retention policy you created to apply to the mailboxes, and then click
Save.
Hope it helps.
Thanks,
Winnie Liang
TechNet Community Support

Custom Folders in Exchange 2013

Hi-
Is there a way to push out additional standard folders to each Exchange 2013 mailbox? If I wanted each user to have a 5 year, 3 year, and 1 year folder, is this possible? Is there some type of script? Someone mentioned to me that there
is a .NET app that uses built-in Exchange functionality to deploy folders to user’s Exchange mailboxes--an "Exchange Folder Generator."
Thank you-
John

Hi John,
According to your description, my understanding is that you want to create the following custom folders for Exchange 2013 mailbox:
1 year folder: All items received 1 years ago;
3 years folder: All items received 3 years ago;
5 years folder: All items received 5 years ago;
Is it right?
If that is the case, I think there is no feature in Exchange to achieve it.
As a workaround, we can consider Ed’s suggestion to create retention policy. The retention tag
specifies how long a message remains in a mailbox and the action to be taken when the message reaches the specified retention age.
Please note that when a message reaches its retention age, it's moved to the user’s In-Place Archive or deleted instead of being moved to another custom folders.
Regards,
Winnie Liang
TechNet Community Support

RMAN LIST backup and maintain backup.

Hi Experts,
Currently we have some changes on the rman retention policy from 168days to 90days.
RMAN Retention policy is:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
And RMAN Scripts monthly backup is:
run
allocate channel t1 type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo_monthly.opt)';
backup as compressed backupset database tag ${SID}_MONTHLY keep until time 'sysdate+168';
release channel t1;
I believe I still have the old backup after I changed the 'sysdate+168' to 'sysdate+90'; on my scripts
How do I manage to delete this ?
Using, List backup and list backup summary will prompt me very long line and window,
How do I create the CONFIGURE settings I can remove the allocate channel... on my scripts ?
Cheers,
Raff

Hi mseberg,
I have executed as your advised below, but somehow it doesnt get the files.
Is there any way to check what is the oldest backup that available ?
RMAN> DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-90';
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=100 device type=DISK
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=138 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
specification does not match any backup in the repository
RMAN> DELETE EXPIRED BACKUP;
using channel ORA_DISK_1
using channel ORA_SBT_TAPE_1
specification does not match any backup in the repository
RMAN> DELETE FORCE NOPROMPT BACKUP COMPLETED BEFORE 'SYSDATE-90';
using channel ORA_DISK_1
using channel ORA_SBT_TAPE_1
specification does not match any backup in the repository

Effect on backupset

what is effect on old backupsets if one change the retention policy. is previous backupset also come under this policy or only new backupset e.g. taken after changing the retention policy.
thanks

By changing retention policy, you can use old backups as well.. See below example:
C:\Documents and Settings\Administrator>rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Sat Sep 5 15:32:10 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: TEST (DBID=1994923717)
RMAN> show retention policy;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
RMAN> backup datafile 4;
Starting backup at 05-SEP-09
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=141 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 05-SEP-09
channel ORA_DISK_1: finished piece 1 at 05-SEP-09
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TEST\BACKUPSET\2009_09
_05\O1_MF_NNNDF_TAG20090905T153240_5B4HL8L2_.BKP tag=TAG20090905T153240 comment=
NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 05-SEP-09
RMAN> backup datafile 4;
Starting backup at 05-SEP-09
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 05-SEP-09
channel ORA_DISK_1: finished piece 1 at 05-SEP-09
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TEST\BACKUPSET\2009_09
_05\O1_MF_NNNDF_TAG20090905T153244_5B4HLFB8_.BKP tag=TAG20090905T153244 comment=
NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 05-SEP-09
RMAN> report obsolete;
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           15     05-SEP-09
Backup Piece       15     05-SEP-09          C:\ORACLE\PRODUCT\10.2.0\FLASH_RE
COVERY_AREA\TEST\BACKUPSET\2009_09_05\O1_MF_NNNDF_TAG20090905T153240_5B4HL8L2_.B
KP
RMAN> configure retention policy to redundancy 2;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters are successfully stored
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN>In this example, firstly I had a retention policy to rendundancy 1 and I had two backups of datafile 4. So one of them is obsolete. By changing retention policy to redundancy 2 I'll NOT have any obsolete backup

Policy on Trash Retention.

Similar Messages

Maybe you are looking for