John is a CDB administrator, and Mike and Tim are PDB administrators of their respective databases- John takes a complete CDB backup by using RMAN>Backup Database. Mike and Tim may need…

Question

Options

• ARecovery of individual PDBs is not possible, because John did not back up by using
• BMike and Tim need to individually take backups of their respective PDBs, because CDB-level
• CMike and Tim do not need to worry, because recovery of individual PDBs is possible.
• DRecovery of individual PDBs is not possible at all.

• A
  5% (2)
• B
  14% (6)
• C
  74% (32)
• D
  7% (3)

Explanation

https://docs.oracle.com/database/121/BRADV/rcmbckba.htm#BRADV735 About Backing Up CDBs and PDBs RMAN and Oracle Enterprise Manager Cloud Control provide full support for backup and recovery in a multitenant environment. The multitenant architecture enables an Oracle Database to function as a CDB. You can back up and recover a whole CDB, the root only, or one or more PDBs. You can also back up and recover individual tablespaces and data files in a PDB. You might want to perform nightly backups of the whole CDB by using an incremental backup strategy, or you might want to make frequent separate backups of individual PDBs and do less frequent backups of either the whole CDB or of the root. In terms of the ability to recover from data loss, separately backing up the root and all PDBs is equivalent to backing up the whole CDB. The main difference is in the number of RMAN commands that you must enter and the time to recover. Recovering a whole CDB requires less time than recovering the root plus all PDBs. Backing Up a Whole CDB Backing up a whole CDB is similar to backing up a non-CDB. When you back up a whole CDB, RMAN backs up the root, all the PDBs, and the archived redo logs. You can then recover either the whole CDB, the root only, or one or more PDBs from the CDB backup. Backing Up a Whole Database with RMAN You can perform a whole database backup with the database mounted or open. To perform a whole database backup, from the RMAN prompt, use the BACKUP DATABASE command. You may want to exclude specified tablespaces from a whole database backup. As explained in "Configuring Tablespaces for Exclusion from Whole Database Backups", you can persistently skip tablespaces across RMAN sessions by executing the CONFIGURE EXCLUDE command for each tablespace that you always want to skip. You can override the configured setting with BACKUP ... NOEXCLUDE. BACKUP DATABASE; BACKUP DATABASE PLUS ARCHIVELOG; Backing Up the Root with RMAN You can use RMAN to make a backup of only the root. Because the root contains critical metadata for the whole CDB, Oracle recommends that you back up the root or back up the whole CDB at regular intervals. BACKUP DATABASE ROOT; Backing Up PDBs with RMAN RMAN enables you to back up one or more PDBs in a CDB. There are two approaches to backing up a PDB with RMAN: - Connect to the root and then use the BACKUP PLUGGABLE DATABASE command. This approach enables you to back up multiple PDBs with a single command. When you connect to the root and back up a PDB, this backup is visible to the root and to that particular PDB but not to the other PDBs. - Connect to the PDB and use the BACKUP DATABASE command. This approach backs up only a single PDB and enables you to use the same commands used for backing up non-CDBs. Backups created when connected to any PDB are visible when connected to the root. When you back up individual PDBs, the archived redo logs are not backed up. Backing Up Tablespaces and Data Files in a PDB Because tablespaces in different PDBs can have the same name, to eliminate ambiguity you must connect directly to a PDB to back up one or more of its tablespaces. In contrast, because data file numbers and paths are unique across the CDB, you can connect to either the root or a PDB to back up PDB data files. If you connect to the root, you can back up data files from multiple PDBs with a single command. If you connect to a PDB, you can back up only data files in https://docs.oracle.com/database/121/BRADV/rcmflash.htm#BRADV640 Basic Concepts of Point-in-Time Recovery for PDBs RMAN provides support for point-in-time recovery for one or more pluggable databases (PDBs). The process of performing recovery is similar to that of DBPITR. You use the RECOVER command to perform point-in-time recovery of one or more PDBs. However, to recover PDBs, you must connect to the root as a user with SYSDBA or SYSBACKUP privilege. See "Performing Point-in-Time Recovery of CDBs and PDBs". Performing Point-in-Time Recovery of CDBs and PDBs RMAN enables you to perform point-in-time recovery (PITR) of CDBs and PDBs. PITR for PDBs can only be performed using RMAN. If you are not using a recovery catalog, it is recommended that you turn on control file auto backups. Otherwise, PITR for PDBs may not work effectively when RMAN needs to undo data file additions or deletions. Performing Point-in-Time Recovery of a Whole CDB The steps to perform PITR of a whole CDB are similar to the ones used for non-CDBs, with the differences described in this section. SHUTDOWN IMMEDIATE; SET UNTIL SCN 1000; RESTORE DATABASE; RECOVER DATABASE; ALTER DATABASE OPEN RESETLOGS; ALTER PLUGGABLE DATABASE ALL OPEN; Performing Point-in-Time Recovery of PDBs The steps to perform point-in-time recovery of PDBs are similar to the ones for performing DBPITR, with the differences described in this section. When you recover one or more PDBs to a specified point-in-time, the remaining PDBs in the CDB are not affected and they can be open and operational. After recovery, the old backups of the PDB remain valid and can be used if a media failure occurs. You do not need to create new backups. If you have performed point-in-time recovery for a PDB, then you cannot directly flashback the whole CDB to a point that is beyond the point in time to which the PDB was recovered. ALTER PLUGGABLE DATABASE pdb5 CLOSE; SET UNTIL SCN 1066; RESTORE PLUGGABLE DATABASE pdb5; RECOVER PLUGGABLE DATABASE pdb5; ALTER PLUGGABLE DATABASE pdb5 OPEN RESETLOGS;

No community discussion yet for this question.