An administrator initiates a Point-in-Time Recovery (PITR) for a specific Oracle Pluggable Database (PDB) through the NDB console. How does NDB Time Machine process the recovery when the transaction history spans multiple archived redo log switches?
A.
NDB relies on Oracle RMAN to isolate the container-level recovery scope and replays changes that apply to the selected PDB.
B.
NDB ignores the shared container redo logs and applies flat-text backup files directly to the target database directory structure.
C.
NDB uses the native Nutanix Prism Central Cassandra framework to reconstruct relational transaction histories across hosts.
D.
NDB prompts the administrator to execute automated shell scripts from the operating-system command line to append missing block structures.
NDB coordinates Oracle-native recovery mechanisms when restoring a selected PDB to a specified point in time. Time Machine supplies the required snapshot and transaction-log recovery points, while Oracle Recovery Manager restores the necessary PDB datafiles and applies archived redo through the requested timestamp. Oracle redo is maintained at the container database level, so the process does not literally use a completely independent redo stream for each PDB. Nevertheless, Oracle’s recovery operation limits the recovery scope to the selected PDB and processes all required archived-log switches automatically. NDB does not reconstruct Oracle transactions using Prism Central’s Cassandra data, apply flat-text backup files, or require the administrator to append database blocks manually. Nutanix documents the ability to restore selected PDBs by snapshot or timestamp in its official Oracle PDB and CDB management guidance.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit