133.You performed the RMAN database backup with the KEEP option. Which two statements are true regarding this backup? (Choose two.)
A. The backup contains data files, the server parameter file, and the control file even if the control file autobackup is disabled.
B. The KEEP option overrides the configured retention policy.
C. The backup contains only data files and archived redo log files.
D. The KEEP option is an attribute of an individual backup piece.
Answer: AB
答案解析:
参考:http://docs.oracle.com/cd/E11882_01/server.112/e10803/config_backuprec.htm#HABPT5159
Usage Notes
RMAN does not consider backup pieces with the KEEP
option when computing the backup retention policy. If available, RMAN uses these backups for disaster recovery restore operations, but their purpose is to produce a snapshot of the database
that can be restored on another system for testing or historical usage.
When creating archival backups with KEEP
, RMAN only considers KEEP
backups with the same tag. Thus, when using keepOption
with notBackedUpSpec
, RMAN only skips a backup if it finds the specified maximum
number of KEEP
backups with the same tag. Other backups are not counted.
Syntax Element | Description |
---|---|
KEEP |
Specifies the backup as an archival backup, which is a self-contained backup that is exempt from the configured retention policy.
An archival backup is self-contained because is contains all files necessary to restore the backup and recover it to a consistent state. If the database is open during the backup, then RMAN automatically generates and backs up the archived redo log files needed to make the database backup consistent (see Example 2-26). RMAN does not consider backup pieces with the Note: You cannot use When See Also: CONFIGURE and Oracle Database Backup and Recovery User's Guide to learn more about autobackup of the control file. When Note: A recovery catalog is only required for |
FOREVER |
Specifies that the backup or copy never becomes obsolete (see Example 2-27).
A recovery catalog is required when FOREVER is specified because the backup records eventually age out of the control file. |
UNTIL TIME ' date_string ' |
Specifies the time until which the backup or copy must be kept. After this time the backup is obsolete, regardless of the backup retention policy settings.
You can either specify a specific time by using the current |
RESTORE POINT restore_point_name |
Creates a normal restore point matching the SCN to which RMAN must recover the backup to a consistent state (see Example
2-26). The restore point name must not exist.
The SCN is captured just after the data file backups complete. The restore point is a label for the SCN to which this archival backup can be restored and recovered, enabling the database to be opened. In contrast, the Note: The |
NOKEEP |
Specifies that any KEEP attributes no longer apply to the backup. Thus, the backup is a normal backup that is subject to the configured backup retention policy. This is the default behavior if no KEEP option
is specified. |
Example 4-23 Creating a Consistent Database Backup for Archival
This example makes a database backup with tag Q107
and specifies that it should never be considered obsolete (partial sample output included). The archived redo log files necessary to make the data files consistent are included in the backup
set.
Example 4-24 Removing the KEEP Attributes for a Backup
This example backs up all archived redo log files. The KEEP
clause specifies that one second after midnight on January 1, 2008 the backup is considered obsolete.
The following command removes the KEEP
attributes of all archived redo log backups (sample output included):