Very good explanation of point in time recovery. Have a quick question, for suppose we only take L0 backups once a week which is Friday night and L1 on weekdays. We are taking archivelog backups for every couple of hours.. User dropped a table on next Friday at around 3PM and want to recover database until 2:30PM. Is RMAN capable of understanding just with one command 'Recover database until time 2:30' to read L0 from Monday to Thursday and apply all archive and redo logs which are not backed up?
Thank you sir for the good explanation. I got a quick question: is it must to specify the backup tag, I mean if we set the SET UNTIL TIME clause, RMAN should be clever enough to pick the right backup. Thanks in advance
Thank you for the video Sir.. i am able to grasp it easier thru your efficient explaination. I have a question from different scenario, here in your explanation I see we recovered from 1st L1D after L0 backup. If the instance crash happens after 2nd L1D backup, how can we able to recover to PIT? Do we need to recover fully from 1st L1D backup and go for 2nd or we can add the 2nd L1D TAG for PIT recovery? Could you possible to answer this please?
Yes, you are right... Lets take there are three L1 between last L0 and PITR, then you must: Restore from L0 Recover from L1 (first L1) Recover from L1 (second L1) Recover from L1 (third L1) Recover till PITR Hope this clears your doubt.
Mr.Arun kumar is the best Among the DBA's markets, with his astonishing explanation, really remarkable. thanks to DBA Genesis
By far the best demo/refresher on restore/recovery.
Great job!
Great Video, thank you.
Thank you!
Very good explanation of point in time recovery. Have a quick question, for suppose we only take L0 backups once a week which is Friday night and L1 on weekdays. We are taking archivelog backups for every couple of hours.. User dropped a table on next Friday at around 3PM and want to recover database until 2:30PM. Is RMAN capable of understanding just with one command 'Recover database until time 2:30' to read L0 from Monday to Thursday and apply all archive and redo logs which are not backed up?
Thank you sir for the good explanation. I got a quick question: is it must to specify the backup tag, I mean if we set the SET UNTIL TIME clause, RMAN should be clever enough to pick the right backup. Thanks in advance
Thank you for the video Sir.. i am able to grasp it easier thru your efficient explaination. I have a question from different scenario, here in your explanation I see we recovered from 1st L1D after L0 backup.
If the instance crash happens after 2nd L1D backup, how can we able to recover to PIT?
Do we need to recover fully from 1st L1D backup and go for 2nd or we can add the 2nd L1D TAG for PIT recovery?
Could you possible to answer this please?
Yes, you are right... Lets take there are three L1 between last L0 and PITR, then you must:
Restore from L0
Recover from L1 (first L1)
Recover from L1 (second L1)
Recover from L1 (third L1)
Recover till PITR
Hope this clears your doubt.
@@dbagenesis Excited to see your quick response. It cleared my doubt.
Thanks a lot once again.
@@naveenkumark9104 what if we don't have any L1 suppose we have only L0 of Sunday and db crash at 10 am Monday we don't have any L1 so what we do ?
I In BACKUP AS COPY DATABASE .. image copies restore from Incremental backups should be possible - can you confirm?