Timeline for Oracle Hot Backup Theory
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 4, 2015 at 13:39 | comment | added | Gandolf989 | As far as I know you only need to create a standby control file when you are creating a standby database. You can just backup the control file and use that. The backup of the control file should either be from a database in mount mode, or the backup needs to include redo that was generated after the backup of the control file. That way if you are doing an inconsistent backup you will have enough redo to bring the database to a consistent state. | |
| Feb 4, 2015 at 10:04 | comment | added | ibre5041 | As far as I remember when doing this type of backup I had to create also a standby controlfile first. When restoring I used this standby controlfile for redolog aply and media recovery. | |
| Feb 4, 2015 at 7:54 | vote | accept | Stelios | ||
| Feb 3, 2015 at 20:38 | comment | added | Gandolf989 | When you restore a database you need to restore the control file first, then mount the database. When you do that the control file knows where all of the data files need to be as well as it has meta data for all of the backups. Ideally you want to up control_file_record_keep_time to keep track of at least 10 days worth of backups if not more. Then when you recover the database knows what RMAN backups files to use and where they should be. Ideally if you can't do a daily full backup you want to do incremental backups. Hopefully you have enterprise edition and can use a block change file. | |
| Feb 3, 2015 at 20:27 | comment | added | Stelios | Thanks for the link. I understand the reason behind the extensive redo log generation and its purpose during a hot backup. what does not click in my mind is how you can restore and recover the database afterwards. I remember reading that SMON checks the control file and the datafiles for the same SCN before opening the database. In the case of a hot backup, then restore and recover; since we will be putting the tablespaces in backup mode in different discrete time periods the datafiles within the tablespaces will not have consistent SCN s nor will the control file. | |
| Feb 3, 2015 at 20:09 | comment | added | Gandolf989 | RMAN can backup individual tablespaces without using the old start backup/end backup syntax. docs.oracle.com/cd/B19306_01/backup.102/b14192/… | |
| Feb 3, 2015 at 18:59 | comment | added | tvCa | There's a reason why OP is on level of tablespaces. If you want a database backup, yes, but if you want to backup specific tablespaces (and, that implies NOT backing up others), it may still be a good idea, no ? Not everybody needs a full backup. | |
| Feb 3, 2015 at 18:11 | history | answered | Gandolf989 | CC BY-SA 3.0 |