When FRA is enabled, the plug-in lets you define a media destination strategy that balances requirements while speeding up restores by specifying the Destination Backup Options on the Backup Options tab. These options let you select the destination for the backup. They include:
The plug-in provides you with the option during the restore process to define the Restore Source or location that RMAN should use as the source for the restore. This option lets you speed up restores by ensuring that RMAN restores from the FRA or from the NetVault media. With this option, you can:
Additionally, you can use these same Restore Source options when you have performed CLI-based backups to Disk by allocating a channel to Disk but you want to use the plug-in to perform the restore.
The following Restore Source options are available:
• |
NetVault Media Manager: When selected, RMAN opens an “SBT_TAPE” channel and reads the backup files from the backup media that is managed by NetVault and specified in the Device options section of the Target tab. Select this option if an FRA-backup-destination strategy has not been implemented or the Backup Destination of NetVault Media Manager was selected for all backups. |
• |
Disk (Restore from FRA or Disk): When selected, RMAN only opens a DISK device type and restores the backup files from the FRA or the OS-specific directory specified when configuring RMAN’s DISK device type. This option is the default. |
• |
Both NetVault Media Manager and Disk (Restore from both NetVault Media and (FRA or Disk)): When selected, RMAN opens an “SBT_TAPE” channel and a DISK channel, which allows RMAN the flexibility to choose the best source for the recovery files. Select this option if your backup destination strategy includes the Both NetVault Media Manager and Disk option or you have chosen to store backup recovery files in the FRA while performing Flash Recovery Area Backups on a different, independent schedule. |
• |
System Change Number (SCN) Based Point-in-Time Recovery: When an SCN is specified during PIT Recovery, RMAN recovers up to, but not including, the specified SCN. For example, if SCN 1000 is specified, recovery up to SCN 999 is performed. |
• |
Log Sequence Number (LSN) Based Point-in-Time Recovery: When the exact time of the data corruption or failure is not known, specifying a Log Sequence Number that contains the target SCN is a viable option. RMAN recovers through the specified log. V$LOG_HISTORY can be queried to view the logs that have been archived to identify the appropriate log sequence number and thread. |
• |
Time Based Point-in-Time Recovery: Time-based PIT Recovery is useful when the time that the data corruption occurred is known. For example, if a developer dropped a table at 6:00 a.m., PIT Recovery can be performed with a stop time of 5:55 a.m. The plug-in recovers up to, but not including, the specified time. |
For more information on PIT Recovery and database incarnations, see Performing Database Point-in-Time Recovery in the Oracle Database Backup and Recovery Basics guide.
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center