34.Examine the following RMAN command:
BACKUP DATABASE
TAG TESTDB
KEEP UNTIL 'SYSDATE+1'
RESTORE POINT TESTDB06;
Which two statements are true regarding the backup taken by using the above RMAN command?
(Choose two.)
A. Only data files and the control file are backed up.
B. Archived redo logs are backed up only if the database is open during the backup.
C. The backup is deleted after one day, regardless of the default retention policy settings.
D. The backup becomes obsolete after one day, regardless of the default retention policy settings.
Answer: BD
参考：http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta007.htm#RCMRF90048
keepOption
Overrides any configured retention policy for this backup so that the backup is not considered obsolete, as shown in Example 2-26.
You can use the KEEP syntax to generate archival database backups that satisfy business or legal requirements. The KEEP setting is an attribute of the backup set (not individual backup piece) or image copy.
Note: You cannot use KEEP with BACKUP BACKUPSET.
With the KEEP syntax, you can keep the backups so that they are considered obsolete after a specified time (KEEP UNTIL), or make them never obsolete (KEEP FOREVER). As shown in Example 2-27, you must be connected to a recovery catalog when you specify KEEP FOREVER.
Note: You can use CHANGE to alter the status of a backup generated with KEEP.
See Also: keepOption for more information about backups made with the KEEP option
Creating a Consistent Database Backup for Archival Purposes
This example uses a keepOption to create an archival backup set that cannot be considered obsolete for one year. The example backs up the database, archives the redo in the current online logs to ensure that this new backup is consistent, and backs up only those archived redo log files needed to restore the data file backup to a consistent state.
The BACKUP command also creates a restore point to match the SCN at which this backup is consistent. The FORMAT parameter must be capable of creating multiple backup pieces in multiple backup sets.
Example 2-26 Creating a Consistent Database Backup for Archival Purposes
This example uses a keepOption to create an archival backup set that cannot be considered obsolete for one year. The example backs up the database, archives the redo in the current online logs to ensure that this new backup is consistent, and backs up only those archived redo log files needed to restore the data file backup to a consistent state.
The BACKUP command also creates a restore point to match the SCN at which this backup is consistent. The FORMAT parameter must be capable of creating multiple backup pieces in multiple backup sets.
BACKUP DATABASE
FORMAT '/disk1/archival_backups/db_%U.bck'
TAG quarterly
KEEP UNTIL TIME 'SYSDATE + 365'
RESTORE POINT Q1FY06;